# BentCrypto Agent API

> Pay-per-call token intelligence for autonomous agents using x402 plus a gated Base MPP charge canary.

## Discovery
- OpenAPI: https://api.bentcrypto.com/openapi.json
- x402 canonical fan-out: https://api.bentcrypto.com/.well-known/x402
- x402 compatibility catalog: https://api.bentcrypto.com/x402.json
- MPP Base Token Risk canary: https://api.bentcrypto.com/mpp/v1/token/risk
- Agent capabilities: https://api.bentcrypto.com/agents.json
- Agent skill/integration guide: https://api.bentcrypto.com/skill.md
- Pricing hints: https://api.bentcrypto.com/pricing

## Paid endpoints
- GET https://api.bentcrypto.com/v1/token/risk?chain=<solana|base>&address=<token> — $0.01; x402; Solana and Base risk analysis.
- GET https://api.bentcrypto.com/v1/token/security?chain=solana&address=<mint> — $0.01; x402; Solana only.
- GET https://api.bentcrypto.com/mpp/v1/token/risk?chain=base&address=<contract> — $0.01; MPP evm charge; Base USDC Token Risk canary.

## x402 payment flow
1. Call the x402 paid endpoint without Payment-Signature.
2. Expect HTTP 402 and decode Payment-Required.
3. Choose a supported requirement within your spend policy.
4. Sign locally; never send private keys or seed phrases to BentCrypto.
5. Retry the exact request with Payment-Signature.
6. On HTTP 200, read the JSON result and Payment-Response settlement evidence.

The runtime x402 v2 Payment-Required challenge is authoritative for network, asset, amount, receiver, and timeout.

## MPP Base canary payment flow
1. Call the MPP canary without Authorization.
2. Expect HTTP 402 with WWW-Authenticate: Payment.
3. Verify Base, USDC, amount, recipient, and local spend policy.
4. Create the MPP Payment credential locally.
5. Retry the exact request with Authorization: Payment <credential>.
6. On HTTP 200, read the JSON result and Payment-Receipt evidence.

The runtime MPP Payment challenge is authoritative. BentCrypto never needs a buyer private key or seed phrase.