Coinbase Agentic Wallet ↗
Pay for compatible API services from your authorized wallet.
Authenticate with email OTP; the owner funds the wallet and sets spending limits.
Our integration playbook
Put a budget boundary around each paid API call
INFRASTRUCTURE FOR THE AGENT ECONOMY
Access compatible paid APIs through a payment client.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
Confirm that the destination implements the required payment flow. Inspect the price and response contract and enforce a maximum payment.
Before you proceed: Verify both the payment outcome and the returned service result.
AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.
FIND THE MISSING CAPABILITY
7 services · Catalog updated 2026-11-10 · See each listing’s review date
Pay for compatible API services from your authorized wallet.
Authenticate with email OTP; the owner funds the wallet and sets spending limits.
Our integration playbook
Put a budget boundary around each paid API call
Find current web sources and return evidence in a useful structure.
Provision an API key and account credits, or configure an approved funded wallet and spending policy for the documented x402 route.
Our integration playbook
Validate a citation before spending on deeper research
Retrieve market prices, filings and structured company financial data through API or MCP.
Create and fund an account for API access, or authorize a funded USDC wallet on Base for supported x402 requests. Check the intended use against the data licence before selecting a route.
Our integration playbook
Keep each financial value attached to its period and source
Query blockchain nodes and indexed data through MCP, API or CLI.
Create an account and app for API or MCP access, or authorize an EVM wallet and USDC budget for the separate x402 gateway. Select the intended network and scope any wallet permissions separately.
Our integration playbook
Bind blockchain observations to a chain, block and payment route
Query publisher content and current information with documented agent payment options.
Choose the required publisher model and access channel. Configure an API key for the regular API, or authorize the storefront’s identity and payment route with a bounded budget.
Our integration playbook
Select the content contract before authorizing paid retrieval
Search current web sources through API or MCP, with free and documented machine-payment routes.
For limited search, configure the free MCP profile without an account. For broader access, create an account and API key or authorize OAuth. For machine payments, use a compatible funded wallet and an approved spending budget.
Our integration playbook
Choose an access route and bound the retrieval cost before researching
Retrieve website technology profiles and historical detections through API or MCP.
Choose account credits with an API key or authorize a funded Base USDC wallet for x402. Saved-card top-ups require separate manual enablement, spending limits and an Agent Billing Key.
Our integration playbook
Check observation dates before treating a technology as currently installed
NO BROWSER REQUIRED
Search for a capability, then follow the listing’s siteGuide link for our original integration playbook: selection advice, workflow, acceptance checks and recovery steps. The complete playbook is in the page HTML, so you can fetch it without JavaScript or a login.
GET /api/agent-services?capability=email GET /api/agent-services?interface=mcp GET /api/agent-services?payment=x402-wallet GET /api/agent-services?payment=mpp-wallet GET /api/agent-services?payment=no-payment GET /api/agent-services?id=e2b
Full catalog: /data/agent-services.json
Manifest: /.well-known/agent-services.json
You are here to get something done. Find a mailbox for your messages, a browser for your web tasks, a sandbox for your code, or a wallet for approved payments.
Inspect the setup requirements before connecting. You may need your owner to create an account, grant OAuth consent, fund a wallet, or provide a website login.
Check whether usage is free, billed to a provider account or uses a documented x402 or MPP wallet. “Not verified” means agent payment support has not been established. Confirm current terms and stay within your owner’s approved budget.