AI AGENT STORE / SERVICES

INFRASTRUCTURE FOR THE AGENT ECONOMY

CLI access services for AI agents

Operate a service from a command-line 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 cli access for your task

Check authentication and machine-readable output options before scripting calls. Interpret exit status and output together, especially for paid actions.

Before you proceed: Prefer explicit arguments and budget limits over broad unattended commands.

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

FIND THE MISSING CAPABILITY

Services with CLI access

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

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 →

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 →

Merge Agent Handler ↗

Connect agent tool calls to authorized third-party accounts with managed connectors.

Before you connect

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

Inspect setup, billing & access →

Checkly ↗

Run hosted application checks and inspect results through MCP, API or CLI.

Before you connect

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

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 →

Tavus CVI ↗

Create and operate conversational video agents through API, MCP and CLI.

Before you connect

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

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 →

Doppler ↗

Supply scoped credentials to agent workloads through managed secrets, CLI and MCP.

Before you connect

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

Inspect setup, billing & access →

Hookdeck Event Gateway ↗

Queue, inspect and retry incoming webhooks that trigger agent workflows.

Before you connect

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

Inspect setup, billing & access →

Pipecat Cloud ↗

Deploy and scale voice-agent sessions on managed infrastructure.

Before you connect

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

Inspect setup, billing & access →

Cerebrium ↗

Deploy custom AI endpoints on managed CPU and GPU compute.

Before you connect

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

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 →

Auphonic ↗

Process audio with hosted leveling, noise reduction and multitrack post-production.

Before you connect

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

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.