API
An API sells Verbs on your Nouns to developers and agents, with keys, metering, an SDK, a CLI, an MCP server and reference docs.
An API is an Interface that sells Verbs on your Nouns to developers and Agents. Declare the Nouns and Verbs once, and every part of the API compiles from them.
What you get
- 1API on your domain, one route per VerbInterface
- 1OpenAPI document, SDK, CLI and MCP server under your nameInterface
- 1reference docs, status page and changelog on your domainSite
- 1key screen, usage and request log in the customer PortalPortal
- 1Meter that counts calls per customerMeter
- 1Offer with a metered Price, billed each monthStripe's Product, Price and Billing Meter
- 1rate limits and errors that name the fixLimit
Guides
Build it in code
| Part | Code |
|---|---|
| Calling the platform's API | API guides and reference |
| The typed client | SDK |
| The terminal | CLI |
| Agents and tools | MCP |
| Keys and scopes | Keys |
| The Function behind each Verb | Functions |
How it works
- Your customers' API keys: issued in the Portal, scoped, rolled and revoked.
- API plans, limits and uptime: a free plan, bundles, caps, rate limits and credits.
- The API: the seven parts compiled from one definition.
- api.sb: the platform API every Startup API runs on.
- Rate limits.