1. Authorize your agent
Authorize with your agent’s key to get a short-lived token for the connection. The key stays on your server and never reaches the model. See Connect your agent.2. Point your MCP client at the hosted endpoint
Attach the short-lived token as anAuthorization: Bearer header and connect. This works for any framework or custom runtime that speaks MCP over HTTP.
3. Try it
With the agent connected at the read level, ask:What's the ETH price right now?Check balances for 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045Show me recent transactions for 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 on ethereumResolve USDC on ethereum so I can prepare a transfer
4. Grant more capability
Move from read to prepare, execute, or governed autonomous by binding a broader tool profile to the agent and requesting the matching scopes at token exchange. See Execution Levels.Key concepts
Agents & Authority
The five bound things that make an agent, and why the model never authorizes.
Policy Gates
Deny-by-default allowlist rules, evaluated before any share is released.
Structured Errors
Category, code, and required action on every error. Agents recover programmatically.
Where to go next
- Connect your agent — the full credential-exchange flow
- Choose your surface — admin, embedded, customer-owned, background, or deterministic
- Execution Levels — from read-only to governed execution
- Tool Reference — the complete tool surface