Build an API from your data.
Create the tables your app needs and an API comes with them, behind the same sign-in your app already uses.

The Billing Ops data model maps to generated REST API endpoints and an OpenAPI schema.
How it works
An API from your schema, scoped by default.
Your app's data model also creates its API. Each entity gets REST endpoints and an OpenAPI schema. Access is secured for the signed-in user from the first request.

A REST endpoint for every entity
Define a table and it gets GET, POST, PATCH and DELETE routes.

A live OpenAPI schema, always in sync
Your app publishes an OpenAPI 3.0 file generated from the same schema as your API routes.

Scoped and secured by default.
Each request checks the signed-in user first and filters results to allowed data.
A REST endpoint for every entity
Define a table and the API routes come with it: GET, POST, PATCH and DELETE, under /api/v1.

A REST endpoint for every entity
Define a table and it gets GET, POST, PATCH and DELETE routes.
A live OpenAPI schema, always in sync
Your app publishes an OpenAPI 3.0 file at /openapi.json. It is generated from the same schema as your API routes, so your clients, codegen tools, and AI agents always see the latest version.

A live OpenAPI schema, always in sync
Your app publishes an OpenAPI 3.0 file generated from the same schema as your API routes.
Scoped and secured by default.
Each request checks the signed-in user first. Orbit then filters the results, so users only see the data they are allowed to access.
Where it stops: access is the app's end-user session, so this is the API behind your app, not a public API with issued keys. Public API tokens are on the way.

Scoped and secured by default.
Each request checks the signed-in user first and filters results to allowed data.
Where it fits
The API is a projection of your data.
You do not build the API separately. It comes from your data model, so when your schema changes the API changes with it.
Get the endpoints without the boilerplate
Define your data model and get a documented API, scoped to your users from the start.