Managed browser workflows
Read, search, screenshot, click, type, scroll, and popups — inside a policy lane.
GridFleet API — v1
One API surface for fleet-backed services.
One bearer token, one governed access layer. GridFleet v1 exposes browser automation, forecasting, monitoring, court-feed, and audit workflows through bearer-token endpoints — every result returns with receipts.
Auth bearer token · Results receipt-backed · Clients HTTP + MCP
Scroll
01 — Endpoints
Services, not sockets.
Each endpoint fronts a fleet capability. You send the job in JSON; the fleet plans, acts, verifies — and the response carries the evidence.
Research forecasting
Multi-agent prediction with reasoning receipts attached to every answer.
Watch what matters
Court-feed, regulatory, and workflow state checks with routed verification.
Tools where you work
Use GridFleet tools from Claude Code, Cursor, Codex CLI, or other MCP-compatible clients.
02 — The shape of a call
Send the job.Get the receipt.
Every v1 request is a job description; every response is a result plus the proof it happened. No polling dashboards, no trust-me logs.
- Bearer-token auth on every request
- Jobs run inside policy lanes with scoped authority
- Responses carry request IDs, evidence references, and verification notes
- Access is provisioned per operator — request yours
$ POST /v1/services/browse
auth authorization: Bearer <your-token>
body { "action": "read", "target": "approved source" }
▸ fleet plans · acts · verifiespolicy lane
200 result + receipt (request id · evidence refs · verification)
representative shape — live calls return real receiptsv1
03 — Access
Tokens are provisioned,not self-served.
Tell us the workflow and we scope it to the right lanes and limits. You get a bearer token, the endpoints above, and receipts on everything.