Docs reference

Docs / OAuth & Security

OAuth & Security

OAuth consent, account route scopes, bearer forwarding, cache policy, and the boundary between account access and execution.

Updated 2026-07-22

02

Route scopes

The backend enforces both 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.
03

Proxy and cache policy

The Worker forwards Authorization only on exact account routes and never caches account responses.

  • Public x402 and public MCP requests have Authorization removed before origin forwarding.
  • 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 excluded from Worker logs.
04

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, write user_strategies, or call the chain.