Consent and credentials
Account-bound access requires an OAuth 2.1 bearer token and active Stakao consent for the token client_id.
Public discovery, catalog, search, MCP, and x402 allocation analysis do not require OAuth. OAuth is used only when an agent requests account-bound data or submits a human-reviewed activation request.
Account request
bash
curl -i https://api.stakao.com/agent/account/me \
-H 'Authorization: Bearer <oauth-access-token>'Route scopes
The API enforces both the token scopes and the scopes stored in the active Stakao consent.
- GET https://api.stakao.com/agent/account/me — openid.
- GET https://api.stakao.com/agent/account/wallets — openid profile.
- GET https://api.stakao.com/agent/account/strategies — openid profile.
- POST https://api.stakao.com/agent/account/activation-requests — openid profile email.
- GET/POST https://api.stakao.com/agent/mcp/account — openid profile transport access; tool-specific calls enforce their account scope.
Token handling and cache policy
Authorization is accepted only on the account routes, and account responses are never cached.
- Public x402 and public MCP routes ignore any Authorization header.
- Account responses use Cache-Control: private, no-store.
- 401 responses preserve or synthesize WWW-Authenticate: Bearer.
- Cookies, bearer tokens, OAuth bodies, and account payloads are not logged.
No agent execution
OAuth account access does not grant on-chain execution authority.
Account reads are tenant-scoped to the authenticated user. request_activation creates a PENDING record for human review. It does not sign, create a proxy, create a delegate transaction, activate a strategy, or call the chain.