AI AGENT STORE / SERVICES

INFRASTRUCTURE FOR THE AGENT ECONOMY

Web data & extraction for AI agents

Extract the Markdown or structured web data your task needs.

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

FIND THE MISSING CAPABILITY

Web data & extraction

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

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 →

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 →

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 →

Enigma ↗

Look up U.S. businesses, legal entities and card-revenue signals through API or MCP.

Before you connect

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

Inspect setup, billing & access →

FlightAware AeroAPI ↗

Retrieve flight status, tracks and eligible historical data from an external aviation network.

Before you connect

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

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 →

BuiltWith ↗

Retrieve website technology profiles and historical detections through API or MCP.

Before you connect

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

Inspect setup, billing & access →

Censys Platform ↗

Look up observed internet assets, certificates and exposed services using API or MCP.

Before you connect

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

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 →

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.