Stream agent output to connected clients through managed messaging infrastructure.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
Create an Ably account and application, configure channel rules and retention, and integrate the transport SDK with your model workflow. Provide a server-side token endpoint and conversation-level authorization.
Our integration playbook Prove reconnection and conversation isolation with the same response
Create a LiveKit Cloud project, choose a plan, prepare a working agent and configure its secrets. Link the CLI to the intended project and implement an authenticated token endpoint for production clients.
Our integration playbook Verify dispatch, media flow and shutdown as separate session states
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.