Own-fleet

also known as: own-fleet acquisition

The acquisition method where captures run on the provider’s own stealth-browser fleet — real browser sessions loading the real consumer surface — rather than through a third-party scraping vendor (managed-vendor) or the model vendor’s API (official-api). Owning the fleet is what makes durable artifacts possible, since the screenshot, proof-of-page HTML and raw capture are yours to keep, and what makes login walls a schedule rather than an architectural dead end.

In AI Search API

own-fleet is the auto default for seven surfaces today — chatgpt, perplexity, copilot, google_ai_overview, google_ai_mode, google_search, google_news — running guest (logged-out) sessions at consumer_ui fidelity. The authenticated account pool for login-walled surfaces is phase-2. provenance.acquisition: "own-fleet" marks every such capture.

Envelope — an own-fleet capture, on the record

"provenance": {
  "acquisition": "own-fleet",
  "official": false,
  "fidelity": "consumer_ui",
  "loginState": "logged_out"
}

Related terms

See it in the product

Every definition here is enforced in the Envelope contract — run a capture and read the fields yourself.

Try 500 credits free All terms