Base URL
Authentication
Most endpoints require a JWT token in theAuthorization header:
Request format
Send all request bodies as JSON. Include the following header:Response format
All responses follow a consistent envelope structure:| Field | Type | Description |
|---|---|---|
status | boolean | true on success, false on error |
statusCode | number | HTTP status code |
message | string | Human-readable description |
data | object | Response payload |
Rate limits
| Layer | Limit | Window |
|---|---|---|
| Global | 1,000 requests | per minute |
| Per-IP | 100 requests | per minute |
| Per-Agent | 60 requests | per minute |
429 Too Many Requests.
Idempotency
For financial operations, include anIdempotency-Key header to prevent duplicate transactions:
Endpoint groups
Authentication
OTP authentication and token management
Wallet
Balances, transfers, trades, and history
Policy
View and update agent spending policies
Utility
Health checks, token lookup, and agent capabilities
For liquidity provision and prediction market endpoints, see the feature documentation: Liquidity provision and Prediction markets.