Firecrawl ↗
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
INFRASTRUCTURE FOR THE AGENT ECONOMY
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.
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
41 services · Catalog updated 2026-11-10 · See each listing’s review date
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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.