Agent Portfolio (x402)
Wallet and protocol holdings of a given address.
Paid per call via the x402 payment protocol instead of an API key. An unpaid request returns 402 with a base64 payment-required header carrying the payment challenge (0.025 USDC on Base, eip155:8453); an x402-capable client settles it and retries.
The API-key REST API is the default way to use Octav. Use these only when the caller explicitly wants pay-per-call, or is an autonomous agent holding a wallet but no API key. There is no /agent/transactions — transaction history requires an API key.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Query Parameters
EVM or SOL wallet address
Aggregate holdings across addresses
Include image URLs for chains, assets, and protocols
Include blockchain explorer URLs
Wait for fresh data if cache is stale
Response
Successful response — same shape as the API-key equivalent
The response is of type object.