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
Collect content across multiple pages of a site.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
Set allowed scope, page limits and a usage budget before crawling. Validate a small sample before treating a larger collection as complete.
Before you proceed: Record visited URLs so repeated runs can avoid unnecessary duplicate work.
AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.
FIND THE MISSING CAPABILITY
5 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
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
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
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
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.