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 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.
FIND THE MISSING CAPABILITY
30 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
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
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
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
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
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
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
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 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
Retrieve cryptocurrency market data through a public keyless MCP endpoint.
Configure an authorized MCP client with https://mcp.api.coingecko.com/mcp. The public endpoint needs no account key; separately approve any move to a keyed plan.
Our integration playbook
Resolve asset identity before comparing market snapshots
Query labeled blockchain activity, token flows and wallet analytics through API or MCP.
Create a Nansen account, obtain an API key and choose an API credit budget. Check which endpoints require a paid plan before starting a batch.
Our integration playbook
Constrain chain scope and label costs before wallet research
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
Look up U.S. businesses, legal entities and card-revenue signals through API or MCP.
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
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 flight status, tracks and eligible historical data from an external aviation network.
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
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
Validate addresses against maintained reference data through MCP or REST.
Create a Smarty account, obtain secret API credentials and activate licences for the APIs you need. The MCP bulk-address tool requires explicit user confirmation of its lookup count.
Our integration playbook
Preserve uncertain address details instead of silently completing them
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
Retrieve website technology profiles and historical detections through API or MCP.
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
Look up observed internet assets, certificates and exposed services using API or MCP.
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
Retrieve website technology and company signals through a maintained index, API or hosted MCP.
Use a Business account with an existing API key. Connect the hosted MCP endpoint using the account sign-in flow, or configure a server-side REST client.
Our integration playbook
Choose the lookup mode before interpreting an empty technology result
Retrieve observed internet service banners and host context through API, SDK or CLI.
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
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.