API Reference

The Dino API supports several product areas, but the flagship public developer flow today is governed spend for agents over REST /v1 with Dino spending keys.

Interactive API reference (Scalar) — every route, parameter, and schema, with optional “try it” flows: api.dino.id.

If you are building agentic or robotic spend first, start here:

Agent integration starter → (copy-paste shell + minimal harness)

Agent Spend Quickstart →

For the recommended LLM integration architecture, read:

Connecting AI Agents to Dino →

Supporting references:

• Agent Spend Webhooks →
• Agent Spend Errors →
• Agent Spend Changelog →
• Purchase Intents API →
• Crypto Payouts API — Solana USDC →
• Cross-Team Transfers (REST) → — send and receive between workspaces via /v1/transfers
• How Agents Use Dino →

#Full API documentation

The same reference lives at api.dino.id (Scalar UI) and api.dino.id/openapi (raw OpenAPI JSON).

#Agent spend first

Dino's public agent-spend contract gives you:

• spend requests with policy evaluation
• budget and threshold enforcement
• human approval routing
• ledger-backed audit history
• idempotent request handling

Primary endpoints:

• POST /v1/spend-requests
• GET /v1/spend-requests/:id
• GET /v1/balance
• GET /v1/accounts
• GET /v1/accounts/:id

Workspace-to-workspace book transfers (USD, recipient must accept) live on the same /v1 router and include:

• receive-address lookup + resolve
• payment-code create + resolve
• transfer create/list/detail
• accept/decline/cancel transitions

See Cross-Team Transfers for the full endpoint list.

Authentication for this flow uses a Dino spending key:

Authorization: Bearer din_...

#Broader platform API

Beyond agent spend, Dino also provides APIs for:

• Transactions
• Invoices
• Customers
• Time tracking projects and entries
• Financial reports
• Documents
• Bank accounts

#Authentication

The Dino API supports two authentication methods:

#API keys and spending keys

Dino currently exposes two bearer-token patterns:

1. Generic Dino API keys for broader platform automation
2. Dino spending keys for the public agent-spend /v1 flow

For broader Dino data automation:

1. Go to Settings → Developer
2. Click Create API key
3. Give it a descriptive name
4. Copy the key immediately (you won't see it again)

Include your API key in the Authorization header:

Authorization: Bearer your-api-key-here

For agent spend, issue a spending key from the spend-account flow and use:

Authorization: Bearer din_...

#OAuth 2.0 (for user-facing apps)

For building apps that access other users' Dino data with their permission.

1. Create an OAuth application in Settings → Developer
2. Implement the OAuth authorization flow
3. Exchange authorization codes for access tokens
4. Use access tokens in API requests

Build an OAuth app →

#Base URLs

Agent spend uses:

https://api.dino.id/v1

Other Dino APIs are available under route-specific prefixes exposed from the main API service and documented in the full OpenAPI reference.

#Rate limits

• Agent-spend /v1 requests are rate limited and return machine-readable 429 errors.
• Retry with backoff and preserve your idempotency key when retrying POST /v1/spend-requests.
• Check the live API reference for route-specific limits as they evolve.

#Current surface status

• REST /v1 for agent spend: shipped
• dashboard approvals and ledger: shipped
• outbound approval webhooks: shipped
• CLI spend flow: rolling out
• MCP spend tools: rolling out
• TypeScript SDK for agent spend: planned

#SDKs

The public agent-spend contract is designed to back future SDK and MCP tooling. Until those ship for spend parity, use the REST quickstart as the canonical source of truth.

MCP documentation →

#Support

• Email: support@dino.id