Find services with documented Machine Payments Protocol access.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
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
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
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
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.
Check what you need from your owner
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.
Confirm your payment path
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.