Retrieve recorded events to investigate agent and application behavior.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
Authorize an existing organization, or use the agent-created organization flow for a temporary environment. An owner must claim temporary organizations within 24 hours to retain them.
Our integration playbook Bound the investigation before expanding its time window
Create a project and authorize the intended organization. Scope MCP to that project and select read-only access and feature groups for unattended monitoring.
Our integration playbook Keep monitoring separate from database migration work
Select a Vercel account, team and project, connect a supported MCP client and authorize the intended team access. Define which production changes need review.
Our integration playbook Verify a fixed preview revision before production
Create a Railway account, choose a workspace and billing plan, and authorize the projects the agent may access. Connect application source and configure required secrets before deployment.
Our integration playbook Bind the deployment to a project, environment and source revision
Create a Render account and workspace, connect the intended source repository, choose resource plans and authorize your agent. Select the workspace explicitly before operating resources.
Our integration playbook Check the supported operation before committing to an MCP workflow
Create an account and project, connect a source to a destination, and configure incoming webhook signature checks and destination authentication. Select throughput and retention appropriate to the workflow.
Our integration playbook Make event retries safe before connecting them to agent actions
Create a gateway organization and host, connect the intended MCP servers, configure user and agent identities and assign tool access. Point clients at the host-specific gateway URL and complete the required sign-in.
Our integration playbook Check the actual tool behavior behind each access tier
Create a Sauce Labs account and choose the required product entitlements. Mobile control requires private dedicated devices and Real Device Access API concurrency; ordinary account access is sufficient only for tools without those dependencies.
Our integration playbook Confirm the device entitlement before scheduling a reproduction
Create an account and the intended organization, activate billing and configure the application’s model-provider secrets. Prepare an agent image or Dockerfile and choose deployment capacity and transport.
Our integration playbook Test the full session lifecycle before scaling voice traffic
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.