AgentMail ↗
Create and operate your own email inboxes.
Agent signup can receive mail; a human must connect the account before sending is unlocked.
Our integration playbook
Build an inbox workflow that separates receiving from sending
INFRASTRUCTURE FOR THE AGENT ECONOMY
Connect a service through a documented MCP interface.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
Inspect the tools exposed by the server and the account they operate on. Verify whether the integration performs actions or merely searches documentation.
Before you proceed: Review individual tool inputs and scope before allowing consequential actions.
AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.
FIND THE MISSING CAPABILITY
97 services · Catalog updated 2026-11-10 · See each listing’s review date
Create and operate your own email inboxes.
Agent signup can receive mail; a human must connect the account before sending is unlocked.
Our integration playbook
Build an inbox workflow that separates receiving from sending
Turn websites into Markdown and structured data you can use.
A limited introductory scrape is documented without a key; higher limits require an account.
Our integration playbook
Validate extraction before scaling to a whole website
Discover app tools and use the access your owner has authorized.
Connect a provider account and authorize each application and scope needed.
Our integration playbook
Bind each tool call to the right connected account
Pay for compatible API services from your authorized wallet.
Authenticate with email OTP; the owner funds the wallet and sets spending limits.
Our integration playbook
Put a budget boundary around each paid API call
Discover and run maintained data-collection tools in the cloud.
Authorize an Apify account with OAuth or an API token; optional agent payment routes require approved funds.
Our integration playbook
Verify an Actor before trusting a data pipeline
Call authorized application tools through a scoped agent session.
Configure Nango, have account owners authorize their integrations, and create a session restricted to the intended tenant and tools.
Our integration playbook
Prove tenant isolation before enabling application writes
Run durable background tasks beyond your current agent session.
Create an organization and project, authorize CLI access, deploy task code and configure the required secrets.
Our integration playbook
Separate a durable run from a repeatable external action
Turn complex documents into text and structured data your agent can inspect.
Create an account, provision an API key and approve uploading the documents and using processing credits.
Our integration playbook
Validate the difficult page before processing the whole collection
Call app tools using the accounts your users authorize.
Create a Connect project and OAuth client; have each user connect the intended accounts and approve production billing.
Our integration playbook
Prove which user owns the connected account
Retrieve current public web data through a hosted MCP connection.
Create a Bright Data account, configure its API token and approve the public-data scope and usage budget.
Our integration playbook
Check coverage before expanding a public-data collection
Run browser tasks on managed browser capacity.
Create a Browserless account, authorize OAuth or configure a token, and choose a plan with suitable session limits.
Our integration playbook
Choose a session lifetime that matches the task
Provision Postgres and inspect scoped development databases.
Authorize a Neon account and project, choose database permissions and billing, and review MCP-requested actions before execution.
Our integration playbook
Use an isolated branch to validate a database change
Give your agent a managed browser with live session controls.
Create a Kernel account and API key; authorize the target websites, account access and resource budget.
Our integration playbook
Recover the existing browser before opening another
Connect authorized messaging, email and calendar accounts.
Create a Unipile account, obtain a DSN and token, and have each account owner authorize the intended connection and actions.
Our integration playbook
Separate account access from permission to send
Use authorized app tools through a managed actions runtime.
Create an Arcade account, choose the tools for your workflow and obtain the account owner’s OAuth authorization.
Our integration playbook
Bind each tool call to the correct account owner
Give your agent a phone connection and inspect call outcomes.
Connect an existing Bland account or use agent onboarding with owner phone verification. Approve the calling scope and any payment or subscription.
Our integration playbook
Keep phone provisioning separate from payment completion
Retrieve maintained company and jobs data through MCP or API.
Create a Coresignal account with credits; authorize the team through the MCP browser sign-in or configure an API credential.
Our integration playbook
Check entity identity before buying a larger data pull
Start cloud browser tasks with a documented agent-access flow.
Agent Access documents a challenge-based trial key without a dashboard account. Target-account access and any paid expansion still need owner authorization.
Our integration playbook
Treat trial onboarding and browser permissions separately
Keep agent-generated files in managed object storage.
Create a Tigris account, authorize the intended organization and buckets, and choose access and retention settings.
Our integration playbook
Verify the stored object before handing off its link
Trigger structured notification workflows from your agent.
Create a Knock account, configure delivery providers and recipient data, and authorize the workflows your agent may trigger.
Our integration playbook
Expose one notification workflow with a defined payload
Query operational evidence through an agent-accessible observability service.
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
Maintain shared task state in a managed Redis database.
Create and authorize a database, or use the documented agent scratch-database route. Scratch databases expire after 72 hours unless claimed through an Upstash account.
Our integration playbook
Define key ownership and expiry before sharing agent state
Investigate application errors with production context.
Create a Sentry organization and project, instrument the application, and authorize access to the relevant project.
Our integration playbook
Connect an error to a release before proposing a fix
Send transactional email from an authorized domain.
Create an account, verify the sending domain through its DNS, and authorize credentials and intended recipients.
Our integration playbook
Track the message outcome before retrying delivery
Upload, transform and deliver managed media assets.
Choose a Cloudinary product environment and authorize access. An agent can provision a temporary Claimable Cloud, but a person must claim it with email verification to retain it.
Our integration playbook
Verify the delivered variant before publishing its URL
Inspect and operate a hosted application backend.
Create a project and deployment, define application functions and provision credentials scoped to the intended deployment.
Our integration playbook
Separate deployment selection from permission scope
Inspect billing records and operate payment workflows.
Set up the Stripe account and sandbox, authorize the agent’s permissions, and complete any required business activation before live payment operations.
Our integration playbook
Reconcile a billing record before changing it
Inspect and manage a hosted Postgres application backend.
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
Retrieve web content and structured search results.
Create a ScrapingBee account, supply its API key and choose the allowed research targets and credit budget.
Our integration playbook
Validate one extraction before expanding the crawl
Generate speech and manage hosted voice agents.
Create or select an ElevenLabs workspace, authorize the connection and choose permitted voices, content and a usage budget.
Our integration playbook
Verify the audio artifact and the agent target independently
Run hosted image, video and audio generation jobs.
Select a fal account or workspace, authorize the connection, fund the required credits and set a permitted model and spending scope.
Our integration playbook
Treat generation as a tracked job with an output contract
Control remote Chromium sessions with managed proxy access.
Create an Oxylabs account, enable Agent Browser credentials and set permitted targets, session concurrency and a traffic budget.
Our integration playbook
Prove the interaction before scaling browser sessions
Query product events and investigate user journeys.
Create or select a PostHog project, instrument the events needed for your question, and authorize the agent connection to the appropriate account.
Our integration playbook
Make the metric definition part of the answer
Deploy applications and inspect their build and runtime state.
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
Retrieve support context and maintain Help Center articles.
Select a supported US or EU workspace and authorize the required read and write scopes. Set the permitted conversation and article workflows before enabling unattended tasks.
Our integration playbook
Read the complete conversation before writing support context
Transcribe audio through hosted speech models.
Create a Deepgram project, issue a scoped API key or sign in through the CLI, and choose an audio-processing budget and permitted input files.
Our integration playbook
Keep the transcript traceable to the original audio
Search web and specialist research sources through one API.
Create a Valyu account, obtain an API key or authorize MCP sign-in, and select a plan with access to the datasets your task needs.
Our integration playbook
Keep source coverage visible throughout the research task
Connect agents to email, calendars and meeting records.
Create a Nylas application and connect an authorized account or provision an Agent Account. Grant only the account resources and actions needed for the workflow.
Our integration playbook
Resolve account identity and time zones before booking
Maintain a hosted vector index for retrieval and agent memory.
Create a managed cluster, choose its region and capacity, define the collection and embedding model, and supply a database API key scoped to the intended collections.
Our integration playbook
Validate retrieval boundaries before loading the full corpus
Resume agent workflows after failures and long waits.
Create an Inngest account, integrate the SDK and deploy or connect the application code that executes your functions. Scope agent access to the intended environment.
Our integration playbook
Make each external side effect recoverable before enabling retries
Discover and run hosted machine-learning models.
Create a Replicate account and API token, configure billing when required, and choose a model with suitable input requirements, usage rights and a task budget.
Our integration playbook
Track the prediction before deciding whether to retry
Coordinate availability and scheduling across authorized calendars.
For MCP, create a Scheduler account and developer application in the correct data center. Connect the calendars and select an internal or multi-tenant authorization model.
Our integration playbook
Resolve participants and authorization before proposing a time
Give agents API access to telephone and messaging infrastructure.
Create and fund a Telnyx account, issue a V2 API key and configure the numbers, messaging or voice resources required for your workflow. Complete applicable provider onboarding before production use.
Our integration playbook
Separate resource inspection from outbound communication
Search public developer documentation without an account or API key.
Configure an MCP-compatible client with the HTTPS endpoint https://mcp.algolia.com/1/docsearch/mcp. No Algolia account, application ID or API key is required.
Our integration playbook
Resolve the documentation set before trusting a code example
Deploy and inspect application infrastructure through agent tools.
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
Operate hosted applications and databases from an MCP client.
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
Capture meeting media and investigate recording workflows through APIs.
Create a regional Recall.ai account and REST API key. Set the meeting’s recording permissions, participant notice and retention policy; create a separate scoped MCP key if an unattended agent needs diagnostic access.
Our integration playbook
Track admission, capture and artifact readiness as separate states
Deliver webhook events and investigate failed deliveries with agent tools.
Create a Svix account, select an environment and configure an application and receiver endpoint. Enable App Portal MCP in each intended environment before issuing an application-scoped agent token.
Our integration playbook
Make the receiver safe to replay before recovering missed events
Operate hosted compute and account resources through the Cloudflare API MCP server.
Create a Cloudflare account, choose the services and billing plans required by the workload, and authorize only the accounts and resources the agent should operate.
Our integration playbook
Resolve account and resource identity before executing a discovered operation
Manage identity resources and authorize access to your MCP services.
Create a WorkOS workspace, select staging or production, configure the application and identity connections, and approve the agent’s dashboard account access. Production requires billing information.
Our integration playbook
Keep management authorization separate from end-user access
Retrieve structured search-engine results through an API or MCP client.
Create a SerpApi account, obtain an API key and select a search plan. Choose the engine, language and geographic settings that match the task.
Our integration playbook
Keep the search context with every result you use
Generate and transcribe speech through hosted voice models and agent tools.
Create a Cartesia account, select a usage plan and obtain server credentials or sign in through the MCP connection. Choose the voice, model and audio format required by the destination.
Our integration playbook
Match the audio contract before connecting speech to a live workflow
Operate notification workflows and subscriber preferences through agent tools.
Create a Novu Cloud account in the intended region, configure a development environment and connect the required delivery providers. Define subscriber identifiers, preferences and the workflow before enabling real recipients.
Our integration playbook
Resolve the subscriber, environment and delivery provider before triggering
Manage notification templates, journeys and delivery through operational agent tools.
Create a Courier workspace, connect delivery providers and prepare a test recipient. Select the Test environment and issue a separate API key for the agent before allowing production sends.
Our integration playbook
Resolve environment and provider capacity before releasing a notification
Fetch live web content through managed scraping, browser and extraction tools.
Create a Scrapfly account and project, obtain credentials or authorize the MCP connection, and choose the credit plan and project access settings for the workload.
Our integration playbook
Validate page identity and extraction completeness before scaling retrieval
Give agents hosted browser sessions with reusable authenticated state.
Create a Notte account and workspace, select a plan and authorize the MCP connection or issue an API key. Establish any required website login with the authorized account owner.
Our integration playbook
Check authentication, task completion and browser shutdown separately
Check email addresses against external validation and risk signals.
Create an account, obtain an API key and configure credits. Connect the official MCP server if needed, and choose the appropriate processing region.
Our integration playbook
Keep uncertain email results out of automatic send decisions
Look up public IP addresses using maintained network and location data.
Create an IPinfo account, choose the data tier and configure overage billing. Authorize the MCP client or issue a server-side API token.
Our integration playbook
Keep network evidence separate from decisions about people
Fetch weather observations and forecasts through an agent-oriented API or MCP server.
Have the account owner authorize signup and the current terms, then store the returned account secret and data key separately. A person completes paid credit top-ups on the provider’s payment page.
Our integration playbook
Check the weather timestamp and the correct credit balance
Operate video ingest, streaming and playback through APIs or MCP.
Create an account and select the intended environment, token permissions and billing plan. Decide whether playback must be public or signed before creating assets.
Our integration playbook
Keep video creation, readiness and playback permission distinct
Retrieve market prices, filings and structured company financial data through API or MCP.
Create and fund an account for API access, or authorize a funded USDC wallet on Base for supported x402 requests. Check the intended use against the data licence before selecting a route.
Our integration playbook
Keep each financial value attached to its period and source
Connect agent tool calls to authorized third-party accounts with managed connectors.
Set up an organization, Registered User and scoped Tool Pack, then authorize required third-party connectors. A documented agent signup route can create initial credentials, but it does not grant private account access.
Our integration playbook
Bind each tool call to the intended user and permission scope
Run hosted application checks and inspect results through MCP, API or CLI.
Create an account, select monitoring locations and a plan, and configure checks and alerts. Authorize an approved OAuth client or issue a key with the required account role.
Our integration playbook
Distinguish a monitor’s last result from current application health
Capture rendered pages and retrieve clean page text through a hosted API or MCP.
Create an account and approve the hosted MCP connection or obtain an API access key. Choose capture options, a plan and any permitted extra-usage limit.
Our integration playbook
Make screenshot evidence reproducible and inspect its contents
Search synchronized context from authorized apps and databases through API, CLI or MCP.
Create an account and collection, authorize the required source connections and wait for an initial sync. Choose a plan and decide which data the agent may retrieve.
Our integration playbook
Check source freshness before treating retrieved context as current
Query managed analytics data and published endpoints through MCP or APIs.
Create a Workspace in the intended region, ingest an authorized dataset and prepare query endpoints. Issue a resource-scoped token or appropriately restricted JWT and set a usage budget.
Our integration playbook
Give the agent a scoped analytical question and a known data window
Retrieve web content and supported structured datasets using hosted collection infrastructure.
Create an account, obtain its API key and select a credit allowance and concurrency level. Define the permitted sources, retrieval volume and required output format.
Our integration playbook
Budget the actual retrieval options and validate the extracted fields
Simulate transactions and inspect contract execution in managed blockchain environments.
Create a Tenderly account and project, arrange a paid plan and have MCP access enabled through sales. Select the intended project, network and Virtual Environment before running a workflow.
Our integration playbook
Keep simulated state separate from permission to move real assets
Query blockchain nodes and indexed data through MCP, API or CLI.
Create an account and app for API or MCP access, or authorize an EVM wallet and USDC budget for the separate x402 gateway. Select the intended network and scope any wallet permissions separately.
Our integration playbook
Bind blockchain observations to a chain, block and payment route
Query linked web entities and extract structured records through API or MCP.
Create a Diffbot account, authorize MCP or supply an API token, and choose a plan and query budget. Crawl access depends on the plan.
Our integration playbook
Resolve the entity before expanding a research query
Turn complex documents into structured fields and layout-aware content.
Create a Reducto account and authorize a key or local login. Select the processing region, retention terms and spending limits before uploading sensitive documents.
Our integration playbook
Validate document evidence before accepting structured fields
Retrieve public video transcripts and metadata through API, SDK or MCP.
Create an account, connect hosted MCP with OAuth or configure an API key, and set a credit budget. Decide whether generated transcription and automatic credit recharge are allowed.
Our integration playbook
Set a transcription mode and cost ceiling before fetching video
Retrieve library documentation and examples for an agent’s coding task.
Connect an MCP client with OAuth or create a Context7 API key. Select allowed sources and decide whether private-repository indexing or paid overages are permitted.
Our integration playbook
Match documentation to the installed dependency before coding
Query publisher content and current information with documented agent payment options.
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
Compare carrier rates, purchase shipping labels and track parcels through API or MCP.
Create a Shippo account, configure billing and carrier connections, and authorize the MCP connection. Set explicit limits for label purchases and other billed operations.
Our integration playbook
Separate shipping decisions from label purchases
Retrieve cryptocurrency market data through a public keyless MCP endpoint.
Configure an authorized MCP client with https://mcp.api.coingecko.com/mcp. The public endpoint needs no account key; separately approve any move to a keyed plan.
Our integration playbook
Resolve asset identity before comparing market snapshots
Query labeled blockchain activity, token flows and wallet analytics through API or MCP.
Create a Nansen account, obtain an API key and choose an API credit budget. Check which endpoints require a paid plan before starting a batch.
Our integration playbook
Constrain chain scope and label costs before wallet research
Fetch, render and extract web data with managed infrastructure through MCP or API.
Create a Zyte account, authorize MCP and select the billing organization. Set API spending limits and separately review any Scrapy Cloud job budget.
Our integration playbook
Choose the least expensive retrieval mode that preserves the evidence
Create and operate conversational video agents through API, MCP and CLI.
Create a Tavus developer account, configure credentials and billing, and choose a face, voice and permitted application tools. Set session duration, concurrency and spending limits.
Our integration playbook
Bound the session lifecycle before connecting application actions
Search an independent web index and retrieve source-linked context for agents.
Create an API account, complete the provider’s billing verification and issue a key. Choose a usage budget and confirm the plan’s storage rights before retaining results.
Our integration playbook
Budget the search context and verify the original claim
Find scholarly works, resolve citations and inspect research connections through API or MCP.
Connect MCP and approve OpenAlex sign-in, or obtain a free API key. An agent can request a key for its owner, but the owner must click the emailed activation link before that key works.
Our integration playbook
Keep a reproducible search trail before summarizing research
Look up U.S. businesses, legal entities and card-revenue signals through API or MCP.
Create an Enigma account, choose a plan covering the required interface and obtain an API key. Current pricing places API access in Pro and MCP access in Max; confirm account entitlements and credit limits.
Our integration playbook
Resolve the business entity before buying enrichment
Prepare, send and track agreement workflows through authenticated API and MCP tools.
Choose a Docusign account and eligible plan, enable MCP access with the administrator, and configure OAuth. Custom agents need an approved production Integration Key and their own approval step for agreement actions.
Our integration playbook
Validate recipients and document versions before sending an agreement
Supply scoped credentials to agent workloads through managed secrets, CLI and MCP.
Create a project and a config containing only the required credentials. Have an authorized administrator issue a suitably scoped token, choose its expiry and configure the agent runtime. The MCP server requires Node.js 20 or later.
Our integration playbook
Match credential scope to the workload before launching it
Find places, geocode addresses and calculate routes through location APIs and MCP.
Create a Geoapify account and project, generate an API key and configure restrictions suitable for the client. Choose a plan and implement the required Geoapify and source-data attribution.
Our integration playbook
Resolve the location before trusting a route estimate
Retain project context, retrieve source documents and share memory across authorized agent sessions.
Create an account, decide which data may be retained and choose a space or namespace. Approve MCP access to the intended spaces, or create an API key in the developer console for application integration.
Our integration playbook
Keep memory attributable and test corrections across sessions
Find relevant public and private technical documentation through a hosted MCP service.
Create a Ref account and connect the MCP client. Choose personal or team scope, and authorize any private documentation sources before making them available to the agent.
Our integration playbook
Check the installed version before applying a retrieved example
Store searchable data in a managed vector database and query it through SDKs or MCP.
Create a cloud account and cluster, import an authorized collection and configure its vectorizer. Enable Agents for the organization if using Query Agent, and issue a key with access to the intended collections.
Our integration playbook
Validate retrieval and access boundaries before asking for summaries
Search current web sources through API or MCP, with free and documented machine-payment routes.
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
Queue, inspect and retry incoming webhooks that trigger agent workflows.
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
Run agent-directed tests on hosted real mobile devices and desktop browsers.
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
Route MCP tool calls through managed identity, authorization and audit controls.
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
Inspect tests and operate dedicated mobile devices through hosted MCP tools.
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
Validate addresses against maintained reference data through MCP or REST.
Create a Smarty account, obtain secret API credentials and activate licences for the APIs you need. The MCP bulk-address tool requires explicit user confirmation of its lookup count.
Our integration playbook
Preserve uncertain address details instead of silently completing them
Retrieve website technology profiles and historical detections through API or MCP.
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
Look up observed internet assets, certificates and exposed services using API or MCP.
Create a Platform account and select the appropriate plan. Organization access requires the API Access role. Choose the organization whose entitlements and credits should be used.
Our integration playbook
Attach observation time and identity confidence to each inventory finding
Retrieve website technology and company signals through a maintained index, API or hosted MCP.
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
NO BROWSER REQUIRED
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
Full catalog: /data/agent-services.json
Manifest: /.well-known/agent-services.json
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.
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.
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.