AI AGENT STORE / SERVICES

INFRASTRUCTURE FOR THE AGENT ECONOMY

SDK access services for AI agents

Use a provider library from your 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 sdk access for your task

Check the supported language and version against the official quickstart. Confirm configuration and response handling with a small controlled task.

Before you proceed: A convenience method still consumes the underlying service’s permissions and usage.

AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.

FIND THE MISSING CAPABILITY

Services with SDK access

97 services · Catalog updated 2026-11-10 · See each listing’s review date

Svix ↗

Deliver webhook events and investigate failed deliveries with agent tools.

Before you connect

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

Inspect setup, billing & access →

WorkOS ↗

Manage identity resources and authorize access to your MCP services.

Before you connect

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

Inspect setup, billing & access →

Ably AI Transport ↗

Stream agent responses across reconnecting clients and multiple devices.

Before you connect

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

Inspect setup, billing & access →

Twilio Programmable Messaging ↗

Send authorized messages and track delivery through telecom infrastructure.

Before you connect

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

Inspect setup, billing & access →

LiveKit Cloud ↗

Run realtime voice agents on managed media and deployment infrastructure.

Before you connect

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

Inspect setup, billing & access →

Cartesia ↗

Generate and transcribe speech through hosted voice models and agent tools.

Before you connect

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

Inspect setup, billing & access →

Novu Cloud ↗

Operate notification workflows and subscriber preferences through agent tools.

Before you connect

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

Inspect setup, billing & access →

Stytch Connected Apps ↗

Give agents scoped, consented access to your application through OAuth.

Before you connect

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

Inspect setup, billing & access →

Courier ↗

Manage notification templates, journeys and delivery through operational agent tools.

Before you connect

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

Inspect setup, billing & access →

Airtop Cloud Browsers ↗

Run browser sessions with saved profiles and natural-language page operations.

Before you connect

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

Inspect setup, billing & access →

Lob Print and Mail ↗

Turn approved documents into physical letters and postcards through an API.

Before you connect

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

Inspect setup, billing & access →

Scrapfly ↗

Fetch live web content through managed scraping, browser and extraction tools.

Before you connect

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

Inspect setup, billing & access →

Notte ↗

Give agents hosted browser sessions with reusable authenticated state.

Before you connect

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

Inspect setup, billing & access →

People Data Labs Company Enrichment ↗

Match company identifiers against a maintained business dataset.

Before you connect

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

Inspect setup, billing & access →

AssemblyAI ↗

Turn recorded or live audio into transcripts through hosted speech models.

Before you connect

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

Inspect setup, billing & access →

EasyPost ↗

Retrieve carrier rates, purchase authorized labels and follow shipment tracking.

Before you connect

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

Inspect setup, billing & access →

Speechmatics Agent STT ↗

Stream audio and receive speaker-labelled transcripts and turn events for voice agents.

Before you connect

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

Inspect setup, billing & access →

Airweave ↗

Search synchronized context from authorized apps and databases through API, CLI or MCP.

Before you connect

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

Inspect setup, billing & access →

Tinybird ↗

Query managed analytics data and published endpoints through MCP or APIs.

Before you connect

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

Inspect setup, billing & access →

Alchemy ↗

Query blockchain nodes and indexed data through MCP, API or CLI.

Before you connect

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

Inspect setup, billing & access →

Reducto ↗

Turn complex documents into structured fields and layout-aware content.

Before you connect

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

Inspect setup, billing & access →

Supadata ↗

Retrieve public video transcripts and metadata through API, SDK or MCP.

Before you connect

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

Inspect setup, billing & access →

Dappier ↗

Query publisher content and current information with documented agent payment options.

Before you connect

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

Inspect setup, billing & access →

Tensorlake ↗

Run agent code in hosted sandboxes with controlled resources and resumable state.

Before you connect

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

Inspect setup, billing & access →

Mindee ↗

Extract structured fields from documents with hosted models and asynchronous API jobs.

Before you connect

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

Inspect setup, billing & access →

Supermemory ↗

Retain project context, retrieve source documents and share memory across authorized agent sessions.

Before you connect

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

Inspect setup, billing & access →

Descope Agentic Identity Hub ↗

Give agents policy-controlled access to third-party credentials and delegated integrations.

Before you connect

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

Inspect setup, billing & access →

Databento ↗

Retrieve maintained historical and live market datasets through APIs and client libraries.

Before you connect

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

Inspect setup, billing & access →

Weaviate Cloud ↗

Store searchable data in a managed vector database and query it through SDKs or MCP.

Before you connect

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

Inspect setup, billing & access →

You.com APIs ↗

Search current web sources through API or MCP, with free and documented machine-payment routes.

Before you connect

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

Inspect setup, billing & access →

Privy Agent Wallets ↗

Create programmable wallets with scoped authorization for agent transactions.

Before you connect

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

Inspect setup, billing & access →

Sensible ↗

Extract structured document data with configurable fields and validation rules.

Before you connect

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

Inspect setup, billing & access →

PostGrid Print & Mail ↗

Send physical letters and postcards from approved content through an API.

Before you connect

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

Inspect setup, billing & access →

Roboflow Serverless Cloud API ↗

Run image inference and vision workflows on managed GPU infrastructure.

Before you connect

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

Inspect setup, billing & access →

Shodan ↗

Retrieve observed internet service banners and host context through API, SDK or CLI.

Before you connect

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

Inspect setup, billing & access →

Soniox Speech API ↗

Transcribe recorded or streaming audio using hosted speech models and structured results.

Before you connect

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

Inspect setup, billing & access →

Geocodio ↗

Geocode address batches and append geographic reference data through API, SDK or CLI.

Before you connect

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

Inspect setup, billing & access →

Explore related capabilities

Browse all service tags →

NO BROWSER REQUIRED

Discover. Inspect.
Connect.

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

Choose your next service with the facts in hand.

Find the tools you need

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.