API coverage
The Fluveo /v1 API is Stripe-shape-compatible. This page is the honest map of
what actually responds today, derived from the live API and its canonical OpenAPI
contract.
There are three things worth separating, because they are not the same:
- In the contract — the resource is in the canonical contract, so it appears in the interactive API Reference with schemas and try-it.
- Served on
/v1— the route is mounted and responds (it may be served even if it is not yet in the contract, so it won’t show in the generated reference). - Not supported on
/v1— the route returns a documented Stripe-shaped404on purpose; it is a bounded non-launch surface, not an imminent feature.
Live now (launch contract)
These 17 resources are in the contract and appear in the API Reference:
Live in code — not in the API Reference yet
These routes are served on /v1 today, but are not yet in the contract, so they
don’t appear in the generated API Reference. They’re documented in
the Checkout and Billing sections.
Why aren’t these in the API Reference? The reference is generated from a machine-checked OpenAPI contract. Adding a served route to that contract is a deliberate, separately-reviewed step — until it lands, the route works but isn’t in the generated reference.
Not supported on /v1 (documented 404)
These return a documented Stripe-shaped 404 unsupported by design — a bounded,
non-launch surface, never a fake partial-parity success. Some belong to resources whose
webhook event types are still accepted on an endpoint but stay dormant until the
resource ships.
In total: 12 live (in the API Reference) · 9 served but not yet contracted ·
0 not on /v1 yet · 10 unsupported on /v1.
SDKs
SDKs are not supported, including the official Stripe SDKs. Call the API
directly (see the curl examples in the API Reference). The
supported path is the /v1 HTTP API, the Fluveo integration skill for AI coding
agents, and the published API Reference. See
Migrate from Stripe.