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
Call a service directly over its documented API.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
Read authentication, request and response contracts before integration. Use timeouts and bounded retries and distinguish reads from billable or state-changing operations.
Before you proceed: Keep credentials out of URLs and check provider errors before retrying.
AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.
FIND THE MISSING CAPABILITY
150 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
Launch a cloud browser to interact with websites.
Provision a provider account and API key; target sites may require login.
Our integration playbook
Choose session control before building a browser workflow
Delegate a web task or control a managed browser.
Provision a cloud API key and any target-site credentials.
Our integration playbook
Decide whether to delegate a task or control the browser
Search the web and retrieve page contents for your research.
Provision an API key and usage budget.
Our integration playbook
Build a research record you can audit later
Find web information through search designed for AI agents.
Sign up for an API key; approve paid usage beyond the included allowance.
Our integration playbook
Set a research budget before expanding the search
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
Run your code in an isolated execution environment.
Provision an API key and approve the compute budget.
Our integration playbook
Treat the sandbox lifecycle as part of the task
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
Save useful context and recall it across your sessions.
Provision an API key and decide which user or agent owns each memory.
Our integration playbook
Design memory boundaries before saving context
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
Provision an isolated cloud computer for your code and tools.
Create a Daytona organization, provision an API key and approve resource usage and billing.
Our integration playbook
Make sandbox cleanup part of your result
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
Request cited web research and structured enrichment for your task.
Provision a Parallel API key and usage budget, or configure an authorized payment method for the separate payment gateway.
Our integration playbook
Keep the research evidence attached to each output field
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
Build persistent context from conversations and business activity.
Create a Zep account and API key; map application users and authorize which records may be ingested.
Our integration playbook
Check that memory changes when the underlying facts change
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
Prepare connected document collections for retrieval workflows.
Create an account and API key; authorize source and destination connectors and approve processing costs.
Our integration playbook
Reconcile source files with the destination records
Retrieve cited context from your authorized document collection.
Create a Pinecone account and API key, create an assistant, and upload documents you are authorized to process.
Our integration playbook
Test retrieval separately from answer generation
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
Find current web sources and return evidence in a useful structure.
Provision an API key and account credits, or configure an approved funded wallet and spending policy for the documented x402 route.
Our integration playbook
Validate a citation before spending on deeper research
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
Execute coding tasks in managed development sandboxes.
Create a Runloop account and scoped API key; approve repository access, environment inputs and resource spending.
Our integration playbook
Keep environment identity with each coding result
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
Connect agent workflows to live voice conversations.
Create a Vapi account and API key, configure an assistant and authorized number or web calling, and approve recipients and spending.
Our integration playbook
Verify the business action separately from the conversation
Extract structured web data and maintain scheduled collections.
Provision an API key and credit budget, or use the documented MPP route with an approved funded InFlow wallet and spending policy.
Our integration playbook
Validate a sample before scheduling a collection
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
Retrieve evidence from your authorized documents through a managed RAG API.
Create an organization and namespace, generate an API key and approve the documents to ingest.
Our integration playbook
Prove retrieval with known answers before adding a corpus
Run generated code through an isolated code-interpreter API.
Create a Riza account and API key; choose the runtime, input data, permitted network access and spending limit.
Our integration playbook
Use a bounded transformation before executing generated tools
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
Obtain delegated access to APIs on a user’s behalf.
Configure an Auth0 tenant, application and external provider connection. Each user must authenticate and grant the required provider permissions.
Our integration playbook
Bind every external action to the correct user and grant
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
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
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
Embed content and rerank retrieved candidates through hosted models.
Obtain a Jina API key, choose a model and configure token funding for sustained usage. Decide which content may be sent to the hosted API.
Our integration playbook
Keep retrieval coverage separate from ranking quality
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
Preserve workflow progress across worker failures and long waits.
Create a Temporal Cloud account and namespace, choose API-key or mTLS authentication, and deploy workers containing the workflow and activity code.
Our integration playbook
Design recovery around the external action, not just the workflow
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
Maintain vector and text retrieval over a hosted search index.
Create an account and API key, select a region and namespace, and define document identifiers, searchable fields and the embedding approach for your corpus.
Our integration playbook
Test access filters and cold retrieval before scaling the corpus
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
Send authorized messages and track delivery through telecom infrastructure.
Create and verify a Twilio account, configure an eligible sender or Messaging Service, and complete destination-specific registration where needed. Establish recipient permission and billing before live sends.
Our integration playbook
Reconcile message identity before retrying an uncertain send
Run realtime voice agents on managed media and deployment infrastructure.
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
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
Give agents scoped, consented access to your application through OAuth.
Create a Stytch project, configure the connected client, redirect URLs and scopes, and implement the consent and token-validation flow. For an existing identity provider, configure a Trusted Auth Token profile and claim mapping.
Our integration playbook
Test the denied path as carefully as the successful authorization
Run model inference for agent workflows on managed serving capacity.
Create a Fireworks account and API key, configure billing and choose a supported model and serving mode. Set an application budget and decide which tools the model may propose.
Our integration playbook
Separate model inference from permission to execute a tool
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
Call hosted models on managed inference capacity for agent workloads.
Create an account and project, generate an API key, configure billing and choose the exact model and serving mode. Define the request budget and validate the model on the intended task.
Our integration playbook
Choose the serving mode before committing to a latency-sensitive workflow
Run browser sessions with saved profiles and natural-language page operations.
Create an Airtop account, obtain a developer API key and select a usage plan. For authenticated sites, have the authorized user establish a profile through the supported login flow.
Our integration playbook
Verify profile identity and session cleanup before repeating browser work
Turn approved documents into physical letters and postcards through an API.
Create a Lob account and prepare sender, recipient and print-ready content. Use a Test key for layout and integration checks; an administrator must configure payment before live Print and Mail requests.
Our integration playbook
Separate proof approval from the irreversible physical-mail handoff
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
Match company identifiers against a maintained business dataset.
Create a People Data Labs account, obtain an API key and select Company API credits and field access. Confirm that the intended storage and downstream use fit the account’s agreement.
Our integration playbook
Resolve company identity before writing enrichment into your system
Turn recorded or live audio into transcripts through hosted speech models.
Create an account, obtain an API key and configure funds and alerts for the intended usage. Choose the audio workflow, model and optional features, and ensure the audio is authorized for processing.
Our integration playbook
Keep the audio job identity through transcription and downstream analysis
Run supported language models on managed Cerebras inference infrastructure.
Create a Cloud Console organization and project, issue an API key and configure billing. Select an available model and check its capabilities, project limits and serving option.
Our integration playbook
Budget output tokens against both inference spend and available quota
Resolve addresses and place names into geographic coordinates and context.
Create a Mapbox account and access token, configure billing and decide whether results will be stored. Confirm the workflow uses results with a Mapbox map; permanent storage requires the appropriate account setup.
Our integration playbook
Set the result-storage policy before building an address lookup workflow
Run supported models through managed inference APIs and SDKs.
Create a Groq account and API key. Choose an available model and configure the organization’s tier, payment method and spend limits before production use.
Our integration playbook
Coordinate model calls across agents sharing one organization
Resolve addresses and coordinates using maintained open geographic data.
Create an account and API key. Choose a production plan for ongoing use, confirm request allowances and apply the provider’s attribution guidance.
Our integration playbook
Separate geographic precision from address identity
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
Convert files through hosted import, processing and export jobs.
Create an account, choose credits and issue an API key with only the required task scopes. Select formats, engine options and the export destination.
Our integration playbook
Verify the exported artifact before declaring conversion complete
Upload, transform and deliver files through managed APIs and a CDN.
Create a project and obtain its public and secret keys. Choose a plan, configure storage behavior and select the transformations and delivery access the workflow needs.
Our integration playbook
Track upload, storage and delivery as separate states
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
Generate paginated PDF documents through a hosted rendering API.
Create an account, retrieve the API key and choose a document plan. Prepare HTML and accessible assets, then test the intended rendering pipeline before production generation.
Our integration playbook
Validate page content as well as successful PDF generation
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 carrier rates, purchase authorized labels and follow shipment tracking.
Create an account, set up the EasyPost Wallet and ship-from address, and obtain separate test and production keys. Enable wallet carriers or connect authorized carrier accounts, with an approved postage budget.
Our integration playbook
Separate the shipping quote from the paid label and carrier handoff
Stream audio and receive speaker-labelled transcripts and turn events for voice agents.
Create a Speechmatics account and API key, choose an approved processing region and fund the required usage. Configure the audio source and downstream agent separately.
Our integration playbook
Validate who spoke and when the agent should respond
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
Run browser-based collection in managed cloud browsers.
Create a Browser API zone, obtain its connection credentials and set a bandwidth budget.
Our integration playbook
Choose hosted rendering for interactive pages
Collect structured search-engine results for agent research.
Create a SERP API zone, configure an API token and choose query locales and usage limits.
Our integration playbook
Build a repeatable search-results collection
Collect structured records with maintained website scrapers.
Create an account and API token, select a scraper or dataset, and define fields, targets and a collection budget.
Our integration playbook
Choose fresh collection or an existing dataset
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
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
Run agent code in hosted sandboxes with controlled resources and resumable state.
Create an account and select a project and plan. Issue a project API key for SDK use, or authenticate the CLI separately. Set resource limits, timeouts and a budget before scheduling work.
Our integration playbook
Choose the sandbox lifecycle before starting code
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
Extract structured fields from documents with hosted models and asynchronous API jobs.
Create a Mindee account, configure a model and test representative documents. Issue an organization API key, choose the appropriate plan and processing zone, and lock the production schema before automating imports.
Our integration playbook
Check field meaning before importing extracted data
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
Retrieve flight status, tracks and eligible historical data from an external aviation network.
Create a FlightAware account, enroll in an AeroAPI tier appropriate to the use case and obtain an API key. Confirm storage and redistribution rights, usage limits and the budget before scheduling repeated lookups.
Our integration playbook
Match the flight instance before reacting to a status
Give agents policy-controlled access to third-party credentials and delegated integrations.
Create a project and Connection, configure provider credentials and consent, then define agent identity, tenant membership and access policies. Users must connect accounts that require their consent.
Our integration playbook
Keep the caller identity attached to each credential request
Retrieve maintained historical and live market datasets through APIs and client libraries.
Create an account, select a dataset and confirm its licensing and permitted use. Obtain an API key, set a spending limit and complete any required agreements before accessing live or restricted data.
Our integration playbook
Fix the dataset, symbol mapping and time window before downloading
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
Generate speech from text using hosted voice models and streaming audio APIs.
Create an account, choose a voice and usage plan, and issue a Standard API key. Obtain the necessary permission before using a custom voice.
Our integration playbook
Validate the audio stream before connecting it to a conversation
Create programmable wallets with scoped authorization for agent transactions.
Create a Privy application, choose wallet ownership and authorized signers, define policies and fund only the intended network and assets. Keep administrative control separate from the agent runtime where appropriate.
Our integration playbook
Keep wallet authority and payment intent attached to each transaction
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
Find and resolve real-world places using maintained location data.
Create a developer account and service key, review the data-use terms and select fields and billing appropriate to the application. Confirm the current API version before adapting an older example.
Our integration playbook
Resolve the exact venue before using its details in a plan
Retrieve licensed company, funding and relationship data for research workflows.
Arrange REST API access through sales and obtain a provisioned key. Confirm the licensed fields, intended use and sharing rights before integrating. A separate MCP connection does not supply REST credentials.
Our integration playbook
Keep entity identity and missing-data reasons visible in enrichment
Extract structured document data with configurable fields and validation rules.
Create an account, issue an API key and configure the document type and extraction fields. Add representative samples and validation rules, and confirm the allowed data retention and processing arrangement.
Our integration playbook
Validate extracted values before turning them into actions
Send physical letters and postcards from approved content through an API.
Create a Print & Mail account, configure billing and approved sender details, and prepare authorized recipients and content. Start with the isolated test key before using a live key that creates real mail orders.
Our integration playbook
Approve the exact mail piece before crossing into live fulfilment
Generate talking-avatar videos from authorized images, footage and scripts.
Create an account and API key, choose an avatar workflow and confirm the plan’s usage licence. Custom Instant Avatars require a subject consent-verification recording and suitable training footage.
Our integration playbook
Separate content approval, rendering and publication
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
Calculate routes and travel-time estimates using road and traffic data.
Create a TomTom developer account, issue an API key and select the appropriate map product and billing plan. Supply verified coordinates and the vehicle and time assumptions required by the task.
Our integration playbook
Make departure time and vehicle assumptions part of the result
Extract receipt and invoice fields with managed document-processing APIs.
Create a Data Extraction API account, obtain credentials and confirm supported document types, retention and billing. The separate expense-management app does not provide the same API access.
Our integration playbook
Reconcile the arithmetic before posting extracted financial data
Deploy and scale voice-agent sessions on managed infrastructure.
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
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
Run image inference and vision workflows on managed GPU infrastructure.
Create a workspace, choose or deploy the intended model or Workflow and obtain an API key. Confirm data permissions, model licensing, supported inputs and available credits.
Our integration playbook
Validate the model on your scene before automating downstream decisions
Deploy custom AI endpoints on managed CPU and GPU compute.
Create a project, configure billing, application dependencies and model secrets, and choose compute and scaling settings. Prepare a tested application and the service-account credentials required for automated deployments.
Our integration playbook
Test access control and resource limits alongside inference output
Search a maintained news corpus and group coverage into events.
Create an Event Registry / NewsAPI.ai account and API key. Choose a plan covering the required history and usage, and decide how retrieved content will be attributed and used.
Our integration playbook
Count independent sources before treating repeated coverage as corroboration
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
Retrieve observed internet service banners and host context through API, SDK or CLI.
Create a Shodan account and obtain its API key. Select an entitlement covering the intended search, history or monitoring workload; free key creation does not unlock every method.
Our integration playbook
Separate stored observations from a request to scan an asset
Transcribe recorded or streaming audio using hosted speech models and structured results.
Create a Soniox account and project, configure billing and generate a project API key. Choose the appropriate regional endpoint and recorded-file or live-streaming workflow.
Our integration playbook
Preserve audio evidence and job identity until the transcript is checked
Process audio with hosted leveling, noise reduction and multitrack post-production.
Create an account, select an output preset and authorize an API key or OAuth connection. Choose available processing credits and any intended publishing destinations before running a production.
Our integration playbook
Validate the processed audio before enabling automatic publishing
Geocode address batches and append geographic reference data through API, SDK or CLI.
Create an account and API key, confirm country and field coverage, and choose a plan and usage limit. Self-serve and Enterprise use different accounts and endpoints.
Our integration playbook
Budget by requested fields and review approximate matches before joining datasets
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.