Retrieve observed website technologies and their detection history.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
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
Use a Business account with an existing API key. Connect the hosted MCP endpoint using the account sign-in flow, or configure a server-side REST client.
Our integration playbook Choose the lookup mode before interpreting an empty technology result
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.