Authentication
Two ways to authenticate inference requests. Use whichever fits your integration.
API Keys (Bearer)
Request Header
Authorization: Bearer sk-your-api-key- Keys start with
sk-. Shown only once on creation. - Requires a platform account with a card on file.
- Usage is billed post-pay via Stripe. See Billing.
Payment Credential (MPP)
Request Header
Authorization: Payment eyJjaGFsbGVuZ2UiOns...- No account, no API key, no card required.
- Send a request with no auth → receive a
402payment challenge → fulfill it → retry with credential. - Payment is inline and per-token via a Tempo session.
- See the MPP guide for the full flow.
How the Server Decides
The Authorization header scheme determines the rail:
| Header | Result |
|---|---|
| Bearer sk-... | Stripe card billing path |
| Payment eyJ... | MPP Tempo session path |
| (none) | 402 with MPP payment challenge |
Endpoint Reference
GET
/v1/keysSessionList API keys.
POST
/v1/keysSessionCreate API key.
Parameters
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | Yes | Key name. |
DELETE
/v1/keys/:idSessionRevoke an API key.