Give your app a governed spending API.
Dino gives agents, apps, and automation workflows spending keys, budgets, approvals, webhooks, funding context, and a ledgered audit trail around every request.
Start with one test spend request. Then add approvals, webhooks, and production funding when the flow is proven.
10 min
first test request
REST
canonical API
Webhooks
async approvals
Quickstart
First request, first decision.
Create a spend request
curl -sS -X POST "https://api.dino.id/v1/spend-requests" \
-H "Authorization: Bearer $DINO_SPEND_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{
"amount_cents": 12000,
"currency": "usd",
"merchant_name": "OpenAI",
"reason": "model inference for support agent"
}'Policy response
Hit Play to see how Dino evaluates the request, returns a policy decision, and keeps a ledger trail — without leaving this page.
01
Create sandbox
Start with test keys, budgets, and policy decisions before touching live funds or KYB.
02
Send request
Call REST /v1 with idempotency. Dino evaluates budget, merchant, approval, and plan rules.
03
Review decision
Inspect approved, declined, or approval-required outcomes with a ledger trail for every request.
04
Go live
Add signed webhooks, funding controls, fallback reads, and key rotation before production spend.
Product surface
One API path before the advanced rails.
Start with spend requests. Once your app proves repeated governed spend, expand into checkout credentials, MCP workflows, cross-team transfers, or custom volume limits.
Test mode first
Use test keys, budgets, and policy decisions before real funds are involved.
Webhook-ready
Design against signed lifecycle events with idempotent handlers and status-read fallback.
Production handoff
Move to live keys only after funding, limits, approval fallback, and reconciliation are ready.
Platform primitives
Build with control built in.
Spending keys for server-side runtimes
Budgets and per-transaction caps
Human approval thresholds
Ledger entries for every decision
Webhook events for async state
Test-to-live production path
Production checklist
Ready for real money when you are.
Server-side key storage
Idempotency on economic creates
Signed webhook verification
Approval fallback and polling
Budget and plan-limit handling
Key rotation and audit export
Usage economics
Plans set the envelope. API volume drives the platform.
Keep subscription packaging separate from API usage. Developers can test for free, launch with capped usage, and expand into volume pricing as more spend routes through Dino.
Test mode
Free sandbox usage for integration and policy testing.
Starter
Capped early usage while the first governed spend flows are proven.
Pro
Higher limits, approval workflows, analytics, and operational controls.
Scale
Volume pricing when API spend becomes a core product workflow.