Recovea documentation
Recovea is AI spend control: it meters, caps and receipts a company's AI spend from beside their app; the number is one they can re-derive. These pages document it on the wire: cost tracking, spend caps, budgets and receipts, as Meter, Cap, Breaker and Prove.
Base URLs
OpenAI
https://api.recovea.ai/v1Anthropic
https://api.recovea.aiYour own endpoint
https://api.recovea.ai/upstream/v1For coding agents: The five questions a coding agent asks, answered for Recovea: cost tracking, budgets, receipts, caching and fallback.
Quickstart
- Quickstart Change one base URL and send one request: the headers that come back, the first receipt, and what an armed cap answers.
Products
- Products Meter, Cap, Breaker and Prove: four product lines on one gateway, each described as its wire behavior.
- Meter Every request routed through the gateway is priced from a frozen price list and recorded with no prompt or completion in the record.
- Cap An armed cap answers 402 before your provider is called. On Free the caps protect up to one monthly total per organization; the kill switch stops outright.
- Breaker A budget one run carries, declared in request headers. The run is refused at its own line and stays stopped; other runs keep going.
- Prove Every priced request is a receipt in your organization's hash chain under recovea-chain-v1. Export a period and re-derive every hash yourself.
- Where a cap is set Every place a cap is set in the platform, who may change which cap, the four-field form, the five windows, and the scope on the wire.
Concepts
- Concepts The ideas behind the product pages: windows, thresholds, the receipt chain, fail-open and fail-closed, roles and keys.
- Caps and windows The five windows a cap runs on, their UTC boundaries, what the week means in the code, and how several caps on one scope combine.
- Alert thresholds The percentages a cap warns at: whole numbers from 1 to 100, up to ten per cap, each fired once per window and re-armed at the reset.
- The hash-chained ledger The recipe recovea-chain-v1: fourteen fields in order, joined by U+001F, hashed with SHA-256 from a genesis of 64 zeros, and how to re-derive one receipt.
- Fail-open and fail-closed What the gateway does when part of it fails: it passes your traffic through, except under an armed cap or the kill switch, which refuse rather than guess.
- Content-free by schema The metering record has no field that can hold a prompt, a completion or a tool argument. That is a property of the schema, not a retention policy.
- Roles The five roles, Owner, Admin, Member, Billing and Viewer, and what each may do, from the capability table the server enforces on every platform route.
- Organization and keys Your organization, one per email address, the gateway keys it mints, and the project a key can carry: what each one is and who may change it.
- Tags The x-recovea-tags request header: its shape, its limits, the four namespaces, and the rule that it never reaches your provider.
- Glossary One-line definitions of the words these docs use, each pointing at the page that explains it.
- Customer spending caps A dollar line per one of your customers, refused before your provider is called, on Team and above.
- Attribution cuts How a month of your spend is cut by key, project, route, tag and customer: one row per value, and every request in one row of each cut.
- Rate limits Requests and tokens per minute for each plan, as the platform serves them, where throttling sits before the caps, and the 429 it answers.
Guides
- Guides One job per page, top to bottom, ending with a step that shows the thing working.
- Cap your AI spend Set a cap on your organization or on one key, arm it, read the refusal it answers with, hear its alerts, and raise it.
- Set up spending caps for your customers Give every one of your customers a dollar line of their own, on Team and above.
API reference
- API reference The exact shapes: endpoints, headers, status codes and bodies, for the reader who already has it working.
- The Baseline package (the passive tap) The wire the Baseline package runs on: one endpoint, a bearer tap key, the fifteen-field event, and what the server answers.
- Customer spending caps: the wire The customer tag, the budget headers, the refusals and the budgets API shapes for customer spending caps.
- OpenAI-compatible The OpenAI wire.
- Anthropic Anthropic's wire on the same host.
- Declared upstreams The OpenAI wire, forwarded to a destination your organization declared.
Troubleshooting
- Troubleshooting When it does not do what you expected: one entry per real question, each with the cause and the fix.
- Customer spending caps: troubleshooting One entry per question about customer spending caps, with its cause and its fix.
Changelog
- Changelog What shipped, dated, one line each. The changelog is kept on recovea.ai.