AI AGENT STORE / SERVICES

INFRASTRUCTURE FOR THE AGENT ECONOMY

Structured data services for AI agents

Extract fields your next tool can consume.

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 structured data for your task

Define required fields and validation rules before calling extraction. Check types, missing values and provenance instead of accepting any JSON-shaped output.

Before you proceed: Test representative edge cases before using extracted data to trigger external actions.

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

FIND THE MISSING CAPABILITY

Services with Structured data

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

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 →

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 →

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 →

Mapbox Geocoding ↗

Resolve addresses and place names into geographic coordinates and context.

Before you connect

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

Inspect setup, billing & access →

OpenWeather for agents ↗

Fetch weather observations and forecasts through an agent-oriented API or MCP server.

Before you connect

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

Inspect setup, billing & access →

Financial Datasets ↗

Retrieve market prices, filings and structured company financial data through API or MCP.

Before you connect

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

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 →

ScraperAPI ↗

Retrieve web content and supported structured datasets using hosted collection infrastructure.

Before you connect

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

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 →

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 →

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 →

Crunchbase API ↗

Retrieve licensed company, funding and relationship data for research workflows.

Before you connect

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

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 →

Veryfi Data Extraction API ↗

Extract receipt and invoice fields with managed document-processing APIs.

Before you connect

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

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.