Run tests on hosted physical devices and maintained browser environments beyond your local runtime.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
163 available services15 capability categoriesOpen discovery · no login
Choosing real-device testing for your task
Choose by the exact device, operating system, browser, concurrency and product licence required. Distinguish remote device control from launching a manual session.
Before you proceed: Pin the application build, inspect test evidence and end sessions when finished. Separate infrastructure failures from reproducible application defects.
AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.
FIND THE MISSING CAPABILITY
Services with Real-device testing
2 services · Catalog updated 2026-11-10 · See each listing’s review date
Create a BrowserStack account and obtain the product licence for the workflow: App Automate for mobile device control or Automate for desktop browser control. Provide an authorized app build or test URL and connect the MCP client.
Our integration playbook Pin the build and device before judging a test result
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
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.