Firecrawl
Firecrawl is the most complete LLM-ready web data API: six endpoints covering search, scrape, crawl, map, parse, and interactive browser sessions, with clean Markdown output and first-class MCP support. The advertised 1-credit-per-page rate is a base rate—JSON extraction, PDF parsing, ZDR, and prompt-injection checking multiply it by up to 9x, and Interact bills by the browser minute. Self-hosting is AGPL-3.0 but omits the anti-bot, Agent, and Interact features that define the cloud product. Plan credits do not roll over below $599/month.
What is Firecrawl?
Firecrawl is a web data API, not a visual scraper or a workflow builder. Its official tagline—a context API for searching, scraping, and interacting with the web at scale—is an accurate description of the scope. You send a URL or a domain; Firecrawl returns Markdown, HTML, a screenshot, or JSON matching a schema you supply. Around that core sit Search (web search with optional full-page content), Crawl (walk an entire site), Map (enumerate URLs), Parse (convert PDFs and documents), and Interact (a managed browser sandbox for clicking, typing, and reaching content behind forms). There is no point-and-click interface. You get an API key and write code.
The product’s design centre is the LLM pipeline. Most web pages require a real browser to render, block automated requests, and return HTML that no model can reason over directly. Firecrawl sits between the agent and the internet, handles JavaScript rendering and PDF extraction, and returns clean Markdown with the boilerplate stripped. Firecrawl claims its Markdown uses 93% fewer input tokens than raw HTML—a vendor figure, but the direction is obviously right: navigation and cookie banners are tokens you pay your LLM for. The structured-extraction layer—JSON mode, schema-matched output, and Pydantic schema support—is what moves Firecrawl from a scraper to a data API. That layer runs an LLM on Firecrawl’s side, which is why it costs 4 extra credits per page.
The open-source story is real but easy to overstate. The GitHub repository is AGPL-3.0, actively maintained, and has more than 180,000 stars. You can self-host it with Docker Compose. But Firecrawl’s own self-hosting guide lists what is not included: the Fire-engine anti-bot service, screenshots, page actions, Agent, Interact, enhanced proxy paths, managed dashboards, and enterprise controls. What remains is a Playwright-and-fetch crawler with a PostgreSQL queue—a different product from the cloud API. The AGPL license also carries copyleft obligations if you modify the code and serve it as a network service. “Open source” here means you can run a crawler; it does not mean you can replicate Firecrawl.
Pricing is where the product’s complexity becomes consequential. Firecrawl bills by credit, and the base rates are straightforward: 1 credit per page for scrape and crawl, 1 credit per call for map, 2 credits per 10 results for search. The complication is the add-on menu. JSON extraction adds 4 credits per page. PDF parsing adds 1 credit per PDF page. ZDR adds 1 credit per page. Prompt-injection checking adds 4 credits per page and charges 5 credits even on failure. The charges stack. A single JSON-mode scrape with ZDR is 6 credits per page; the same scrape with PII redaction is 9 credits per page. The 1,000-credit Free plan is 1,000 pages only in the most bare-bones configuration. In a realistic AI-extraction setup, it is closer to 111–166 pages. Interact is a separate meter entirely: 2 credits per browser minute for code-only sessions, 7 credits per minute for prompt-driven sessions, with a one-minute minimum.
How does Firecrawl work?
A developer makes a request to one of the six endpoints. /scrape takes a single URL and returns Markdown, HTML, links, screenshots, structured JSON, or a combination. /crawl takes a start URL and a limit, follows links within the site, and returns the set of scraped pages. /map enumerates URLs without scraping content, which is useful for sitemap discovery before a crawl. /search runs a web search and optionally scrapes the results, returning URL plus cleaned page content in the same call. /parse handles PDFs and documents. /interact opens a browser session bound to a scrape job, accepts either Playwright code (Node, Python, or bash) or a natural-language prompt, and returns stdout, result snapshots, and a CDP WebSocket URL for direct Playwright/Puppeteer connection if needed.
The scraping layer handles JavaScript rendering, anti-bot mitigation through the Fire-engine layer, and PDF parsing. Structured extraction uses an LLM to map page content to a supplied JSON schema or a natural-language prompt; the schema locks field names for downstream parsing, while prompt-only extraction is faster but less deterministic. Crawl and search internally call scrape on each page, so all scrape add-on costs apply to those endpoints as well. The output is designed to be consumed by an agent: clean Markdown for context, JSON for structured data, screenshots for visual verification, and CDP URLs for deeper browser control.
A keyless hosted MCP endpoint is available for search, scrape, and parse without an API key, limited per IP address per day. For agents that support MCP—Claude Code, Cursor, Codex, OpenCode—Firecrawl ships an MCP server that exposes the same endpoints as tools. The MCP path is the strongest argument for Firecrawl in 2026: adding Firecrawl to Claude Code or Cursor takes one line, and the keyless MCP server exposes search, scrape, and parse without an account. The caveat is that keyless access is IP-limited and can be blocked; one reviewer received a 403 stating their IP “looks suspicious,” requiring a free key.
Use Cases
- Feeding RAG pipelines and AI agents with clean Markdown from live web pages, PDFs, and JS-rendered sites
- Structured data extraction across a set of URLs or an entire domain using JSON schema or prompt-based extraction
- Site-wide discovery and content ingestion: map a domain’s URLs, then crawl the subset that matters
- Search-and-scrape in one call, where an agent needs both the source list and the full text of each result
- Interacting with pages behind forms, logins, or dynamic controls through the Interact browser sandbox, using Playwright code or a natural-language prompt
- Monitoring pages on a schedule for changes (on paid tiers, billed at 7 credits per page per check for deterministic extraction)
- Batch scraping thousands of URLs when the URL list is known in advance
Pricing
Pricing model: Freemium
| Plan | Price | Billing | Included usage | Notes |
|---|---|---|---|---|
| Free | $0 | per month | 1,000 credits per month. 2 concurrent browsers. Low rate limits: 10 requests/min for /scrape, /map, and /search; 2/min for /crawl, /agent, and /interact. 50,000 max queued jobs. No credit card required. No pay-as-you-go top-ups on Free. | — |
| Hobby | $16 | per month (annual) | $19/month on monthly billing. 5,000 credits per month. 5 concurrent browsers. 100 requests/min for /scrape, /map, /search; 20/min for /crawl and /agent. Pay-as-you-go top-ups from $5 per 1,000 extra credits. Credits do not roll over. | — |
| Standard (Recommended) | $83 | per month (annual) | $99/month on monthly billing. 100,000 credits per month. 25 concurrent browsers. 500 requests/min for /scrape, /map, /search; 100/min for /crawl and /agent. Pay-as-you-go top-ups from $5 per 2,000 extra credits. Credits do not roll over. | — |
| Growth | $333 | per month (annual) | $399/month on monthly billing. 500,000 credits per month. 50 concurrent browsers. 5,000 requests/min for /scrape, /map, /search; 1,000/min for /crawl and /agent. Pay-as-you-go from $5 per 2,500 extra credits. Credits do not roll over. | — |
| Scale | $599 | per month (annual) | $749/month on monthly billing. 1,000,000 credits per month. 100 concurrent browsers. 10,000 requests/min for /scrape, /map, /search; 2,000/min for /crawl and /agent. Pay-as-you-go from $5 per 5,000 extra credits. The first tier where plan credits roll over. | — |
| Enterprise | Custom | annual | Custom credits and concurrency. Dedicated support and SLA, bulk discounts, zero-data retention (ZDR), SSO, and advanced security. Contact sales. | — |
Common Limitations
- The advertised 1-credit-per-page rate is a base rate, not an effective rate · Firecrawl’s pricing page leads with “1 credit per page” for scrape and crawl, and that number is accurate for a bare Markdown scrape. But the features that make Firecrawl useful for AI agents are priced as add-ons that stack. JSON format (LLM extraction) adds 4 credits per page. PDF parsing adds 1 credit per PDF page. Zero-data retention adds 1 credit per page. Prompt-injection checking adds 4 credits per page and charges 5 credits even when the check causes the scrape to fail. A JSON-mode scrape with ZDR is 6 credits per page—a 6x multiplier over the headline; adding PII redaction makes it 9 credits. This is not hidden fine print; it is documented in the billing page. But the gap between the headline rate and the effective rate is large enough that teams budgeting from “1 credit per page” will systematically underestimate consumption. A 1,000-credit Free plan that looks like 1,000 pages is actually 111–166 pages in a realistic AI-extraction configuration.
- Interact browser sessions are billed by the minute and can dominate costs · Interact is Firecrawl’s managed browser sandbox for clicking, typing, scrolling, and reaching content behind forms or dynamic interactions. It is billed per browser minute, not per page: 2 credits per minute for code-only sessions (Playwright/Puppeteer via CDP) and 7 credits per minute for prompt-driven sessions where an AI agent performs the task. There is a one-minute minimum, and ZDR adds 2 credits per minute. A five-minute prompt-driven session consumes 35 credits—more than a month’s worth of Free-plan base scrapes for a single interaction. Interact is a distinct cost centre from scrape and crawl, and teams that add browser automation to their workflows should model it separately rather than assuming it falls under the per-page meter. The rate limit for /interact on Free is 2 requests per minute, so even testing it meaningfully on the free tier is constrained.
- Plan credits expire monthly on every tier below $599/month · Credits reset at the start of each billing cycle. On Free, Hobby, Standard, and Growth, unused plan credits do not roll over. Only Scale ($599/month annual, 1,000,000 credits) and Enterprise retain unused plan credits. This means a team that has a spike month followed by a quiet month on Hobby or Standard loses the unused balance and must buy pay-as-you-go credits during the spike. Firecrawl softened this slightly on September 9, 2026: paid plans can now top up automatically in $5 blocks up to a monthly cap, and credits purchased via top-up stay until used (unless the plan is cancelled). That helps in heavy months—you can pick a smaller plan and top up—but it does not fix the expiry of the plan’s own included credits. A Reddit user in r/n8n put the common gripe bluntly: “my unused credits just vanish at the end of the month.”
- Self-hosting is open source but does not replicate the cloud product · Firecrawl’s GitHub repository is real, actively maintained (188,000+ stars as of late 2026), and AGPL-3.0 licensed. Self-hosting it with Docker Compose is possible. However, Firecrawl’s own self-hosting guide states that the Fire-engine anti-bot service, screenshots, page actions, Agent, Interact, enhanced proxy paths, managed dashboards, and enterprise controls are not included in the self-hosted stack. What you get is a Playwright-and-fetch crawler with a PostgreSQL queue—useful, but materially less capable than the cloud API. The AGPL license also matters for commercial integration: if you modify the code and serve it as a network service, the copyleft obligations extend to your modifications. Community reports add that the self-hosted build struggles with Cloudflare-protected sites, requires a 4GB+ RAM Docker setup, and has broken MCP support in some configurations. For teams that need anti-bot handling, Interact, or a managed browser sandbox, self-hosting is not a substitute for the cloud plan.
- Concurrency, not credits, is often the binding constraint for agent workloads · Firecrawl enforces both per-minute rate limits and concurrent browser limits. The concurrent browser limit caps how many pages render at the same time; excess jobs queue, and queued time counts toward the request timeout. On Free, the limit is 2 concurrent browsers; Hobby 5; Standard 25; Growth 50; Scale 100. Bursts of activity can hit the concurrency ceiling even when average throughput is well within the credit allowance. An agent product that fans out 30 simultaneous scrapes is over the Standard concurrency budget (25) even if it is nowhere near 100,000 credits—so it gets throttled, queued, or pushed to upgrade for a reason that has nothing to do with total volume. Rate limits are applied per team, so adding API keys does not raise the ceiling. For crawl jobs that touch many pages in parallel, concurrency is often the first wall.
- Keyless MCP access is convenience with per-IP limits, not an unmetered free tier · Firecrawl offers a keyless hosted MCP endpoint (mcp.firecrawl.dev) that exposes search, scrape, and parse without an API key. This is useful for trying the product or for agent workflows that need occasional web access without credential management. However, keyless usage is limited per IP address per day by two limits—a maximum number of requests and a maximum number of credits—and the same operations cost different credits, so heavier usage (Interact, JSON extraction) reaches the credit cap sooner. One independent reviewer attempted a keyless scrape from their own machine and received a 403 stating the IP “looks suspicious,” requiring a sign-up for a free key. Keyless access does not include crawl, extract, map, batch scrape, or Interact. Treating keyless MCP as a production integration is a misreading of its purpose; it is a trial and low-stakes convenience layer, and it can be blocked at the IP level.
- No EU data residency, and SSO/ZDR are Enterprise-only · Firecrawl holds SOC 2 Type II on every plan and offers a DPA from Standard. However, it does not offer EU-only data residency on any plan. Zero Data Retention (ZDR) is available as a per-request add-on (+1 credit per page), not as a default posture, and enterprise-grade ZDR with contractual guarantees is an Enterprise feature. SSO is also Enterprise-only. A team on Standard cannot enforce SSO or centralised identity management. For organisations with data-sovereignty or compliance requirements, the self-serve tiers are not a stopgap—the governance features simply are not present until Enterprise. Firecrawl has disclosed SSRF vulnerabilities in the past, including one reported as unpatched at the time of disclosure, which raises the bar for teams that need to run it against internal or sensitive targets.
Key Features
- Six endpoints: Search, Scrape, Crawl, Map, Parse, and Interact
- Clean Markdown, HTML, screenshots, and schema-matched JSON output
- JavaScript rendering and anti-bot handling (Fire-engine) on cloud plans
- PDF parsing and document conversion
- Structured extraction with JSON schema or natural-language prompt
Firecrawl vs. Apify, Crawl4AI, and ScrapingBee
This comparison uses official pricing pages, documentation, and self-hosting guides available as of November 2026. It focuses on the structural differences that determine effective cost, self-hosting fidelity, and the shape of the tool—API versus platform versus library—rather than declaring a universal winner. Firecrawl is a six-endpoint web data API with a managed anti-bot layer and a deliberately AI-oriented output pipeline. Apify is a full scraping platform built around a marketplace of pre-built Actors. Crawl4AI is an Apache-2.0 Python library that is free to self-host and faster in benchmarks, but requires the operator to own the infrastructure. ScrapingBee is a proxy-and-rendering API with the simplest billing model and the weakest AI-specific feature set. These products overlap at the scrape endpoint, but they are not substitutes at the workflow level.
| Tool | Positioning | Key differences | Best fit | Pricing note |
|---|---|---|---|---|
| Firecrawl Official pricing page Billing and credit costs (official docs) Self-hosting feature gap (official guide) | A six-endpoint web data API for AI agents and RAG pipelines, turning live pages into clean Markdown or schema-matched JSON, with a managed browser sandbox (Interact) and first-class MCP support. | The most complete AI-oriented pipeline among the four: search, scrape, crawl, map, parse, and interact under one API family. The headline 1-credit-per-page rate multiplies to 6–9x when JSON extraction, PDF parsing, ZDR, and prompt-injection checking are enabled. Interact bills per browser minute (2–7 credits), not per page. Self-hosting is AGPL-3.0 but omits the anti-bot engine, Agent, Interact, and managed browser sandbox—the cloud-only features that define the product. Plan credits roll over only at Scale ($599/mo). Free tier: 1,000 credits/month with no top-ups. | Teams building AI agents or RAG pipelines that need a managed, LLM-ready web data API with anti-bot handling, structured extraction, and an interactive browser sandbox, and that can budget from the effective rate rather than the headline rate. | Free $0: 1,000 credits/mo, 2 concurrent, no top-ups. Hobby $16/mo annual ($19 monthly): 5,000 credits, 5 concurrent. Standard $83/mo annual ($99 monthly): 100,000 credits, 25 concurrent. Growth $333/mo annual ($399 monthly): 500,000 credits, 50 concurrent. Scale $599/mo annual ($749 monthly): 1,000,000 credits, 100 concurrent, rollover. Enterprise custom. Add-on credits: JSON +4/page, PDF +1/page, ZDR +1/page, prompt-injection +4/page. Interact: 2–7 credits/browser minute. |
| Apify Apify pricing (official) Independent platform comparison (documents Actor marketplace and CU billing) | A full-featured scraping platform built around a marketplace of pre-built scrapers called Actors, with scheduling, storage, and compute-unit billing, aimed at teams that want ready-made solutions for specific sites rather than a single API. | Apify’s core advantage is the Actor marketplace: if a pre-built scraper exists for the target site, the job is largely configuration rather than development. Firecrawl has no equivalent marketplace; it gives you endpoints and expects you to compose them. Apify’s free plan includes $5 of monthly usage credit (about 25 compute units at $0.20/CU), and paid plans start at $19/month (Starter) with $19 in prepaid usage. Compute is billed per CU (1 GB of memory for 1 hour), plus Actor-specific rental or pay-per-event costs. Firecrawl’s billing is per credit with a lower entry point and a simpler unit for AI workflows, but it has no marketplace and no pre-built site-specific scrapers. Apify is stronger when a ready-made Actor exists; Firecrawl is stronger when the workflow is bespoke and AI-output-oriented. | Teams that want pre-built scrapers for common sites (social media, e-commerce, maps), scheduling and storage in one platform, and are comfortable with compute-unit billing plus Actor costs. | Free: $0 with $5 monthly usage credit (~25 CUs at $0.20/CU). Starter $19/mo with $19 prepaid usage. Scale $199/mo. Business $999/mo. Compute $0.20 → $0.13/CU depending on tier. Store Actors bill separately per event or usage. |
| Crawl4AI Crawl4AI documentation (official, free self-hosting) Independent review (documents Apache-2.0 and self-hosting trade-off) | An open-source, Apache-2.0 Python library for turning websites into LLM-ready Markdown or JSON, free to self-host and faster than Firecrawl in benchmarks, but without a managed anti-bot layer or the six-endpoint API family. | Crawl4AI is the strongest zero-cost option if you are willing to operate the infrastructure. The library is Apache-2.0, self-hosting is free and unmetered, and benchmarks place it ahead of Firecrawl on raw crawling speed. It offers deep Python hooks, chunking strategies for LLMs, and an async architecture. What it lacks is the managed layer: no Fire-engine anti-bot handling, no hosted Interact browser sandbox with CDP URLs and live view, no built-in search endpoint with content, and no MCP server bundled in the core library (a hosted MCP option exists, but the self-hosted path is separate). Firecrawl’s cloud product is more expensive per page but removes the infrastructure burden and provides the anti-bot and browser automation features that Crawl4AI users must build or source separately. Crawl4AI’s hosted cloud offers 1,000 free credits/month and paid plans from $10/month, but the library remains the primary product. | Python teams with DevOps capacity that want the lowest marginal cost per page, full control over extraction logic, and are willing to own infrastructure, anti-bot handling, and scaling—rather than paying Firecrawl for a managed layer. | Self-hosted: free and unmetered under Apache-2.0. Hosted cloud: 1,000 free credits/month; paid from $10/month. No per-page metering on the self-hosted path; costs are infrastructure and engineering time. |
| ScrapingBee ScrapingBee pricing (official) Credit system explanation (official help center) | A proxy-and-headless-browser API for scraping, with the simplest credit model in the category and the weakest AI-specific feature set—no MCP, no structured extraction, no browser sandbox. | ScrapingBee’s pricing is the easiest to understand: 1,000 free credits, then Hobby at $19/month for 75,000 credits, Freelance at $49/month for 250,000, Startup at $99/month for 1M, and Business at $249/month for 3M. Credit costs are transparent and tiered by rendering and proxy type: classic proxies without JS = 1 credit, with JS = 5 credits, premium proxies = 10–25 credits, stealth proxies = 75 credits. There is no structured JSON extraction, no crawl-and-map workflow, no Interact browser sandbox, and no MCP server. ScrapingBee is stronger than Firecrawl on raw proxy and rendering infrastructure and simpler billing; Firecrawl is stronger on everything AI-oriented—Markdown output, schema extraction, search, crawl orchestration, and agent integration. A team that only needs HTML from pages behind proxies will find ScrapingBee cheaper and simpler; a team building an AI pipeline will find it insufficient. | Teams that need a straightforward proxy-and-rendering API for HTML extraction, with transparent credit costs and no AI-extraction or agent-integration requirements. | Free: 1,000 credits. Hobby $19/mo: 75,000 credits, 25 concurrent. Freelance $49/mo: 250,000 credits. Startup $99/mo: 1,000,000 credits. Business $249/mo: 3,000,000 credits. Credit cost varies by proxy and rendering: 1–75 credits per request. No structured extraction, MCP, or Interact. |
Comparison checked against official product information on 2026-11-04. Features and pricing may change.
Frequently Asked Questions
How much does Firecrawl actually cost per page?
The base scrape rate is 1 credit per page, but the effective rate depends entirely on the options enabled. JSON extraction adds 4 credits per page. PDF parsing adds 1 credit per PDF page. Zero-data retention adds 1 credit per page. Prompt-injection checking adds 4 credits per page and charges 5 credits even when the scrape fails. These charges stack: a JSON-mode scrape with ZDR is 6 credits per page; adding PII redaction makes it 9 credits per page. Interact is billed separately at 2 credits per browser minute (code-only) or 7 credits per minute (prompt-driven). Budget from the effective rate for your configuration, not the headline 1 credit per page.
Is the self-hosted Firecrawl the same as the cloud product?
No. The AGPL-3.0 repository is real, actively maintained, and self-hostable with Docker Compose, but Firecrawl’s own self-hosting guide states that the Fire-engine anti-bot service, screenshots, page actions, Agent, Interact, enhanced proxy paths, and enterprise controls are not included. What you get is a Playwright-and-fetch crawler with a PostgreSQL queue. Community reports add that the self-hosted build struggles with Cloudflare-protected sites and requires a 4GB+ RAM Docker setup. If your workflow depends on anti-bot handling, Interact, or a managed browser sandbox, the self-hosted build is a different, narrower product. The AGPL license also carries copyleft obligations if you modify the code and serve it as a network service.
Do Firecrawl credits roll over?
Plan credits do not roll over on Free, Hobby, Standard, or Growth. Only Scale ($599/month annual, 1,000,000 credits) and Enterprise retain unused plan credits. A spike month followed by a quiet month on Hobby or Standard means the unused balance expires. Since September 9, 2026, paid plans can top up automatically in $5 blocks up to a monthly cap, and credits purchased via top-up stay until used (unless the plan is cancelled). That lets you pick a smaller plan and top up in heavy months, but it does not fix the expiry of the plan’s own included credits.
What is the difference between Firecrawl’s Free plan and the keyless MCP access?
The Free plan gives you an API key with 1,000 credits per month and access to all endpoints, subject to low rate limits and no pay-as-you-go top-ups. Keyless MCP access requires no account and exposes search, scrape, and parse, but is limited per IP address per day by both a request cap and a credit cap, and shares the same operations-cost differences (Interact and JSON extraction cost more). Keyless access does not include crawl, extract, map, batch scrape, or Interact. The keyless path is a trial and convenience layer for agent workflows, not a production integration, and it can be blocked at the IP level.
Is Firecrawl suitable for large-scale crawling?
It can be, with the right plan and expectations. Concurrency, not credits, is often the binding constraint for crawl jobs: Free allows 2 concurrent browsers, Hobby 5, Standard 25, Growth 50, and Scale 100. Queued jobs count toward the request timeout, so bursts can cause latency even when average throughput is within the credit allowance. The maximum queued jobs is 50,000 on Free through Standard, 100,000 on Growth, and 200,000+ on Scale. Rate limits are applied per team, so adding API keys does not raise the ceiling. For large-scale crawling, budget for a plan with adequate concurrency and test with a representative workload rather than extrapolating from the credit allowance alone.
Alternative Tools
-
Context7 Context7 is an Upstash-built MCP server that injects up-to-date, version-specific library documentation and code snippets into AI coding agents, reducing deprecated-API hallucinations for indexed frameworks and packages. -
OpenRouter OpenRouter is the widest managed gateway to LLMs: 500+ models across 80+ providers behind one OpenAI-compatible endpoint, with automatic fallback, MCP support, and no per-token markup. Its pricing is honest about the token pass-through but less forthcoming about the $0.80 minimum fee that makes small top-ups cost 8–16% effectively, and about the fact that EU/US in-region routing requires the 8% Business tier. BYOK is free up to $25,000/month, which is a non-issue for almost everyone. It is a strong default for model breadth and zero-ops access—not for self-hosting, small-budget cost optimization, or contractual uptime guarantees. -
Composio Composio is a managed tool-integration and authentication layer that exposes 1,500+ apps as agent-callable tools via SDKs, a CLI, or hosted MCP endpoints, handling OAuth, tool search, and execution for AI agents. -
Google AI Studio Google AI Studio is the fastest zero-friction way to get a working Gemini API key and prototype multimodal prompts in a browser, with no credit card. The catch is structural: the free tier excludes Gemini 4 Argon and all image/video models, trains on your inputs with no self-serve opt-out, and hides rate limits inside a console; paid rates for Flash are promotional and double in 2027; thinking tokens are billed as output; and AI Studio has no IAM, VPC-SC, SLAs, or regional endpoints—those live in Vertex AI, which is a separate migration. -
Model Context Protocol MCP is the de facto open standard for connecting AI agents to tools and data, adopted by every major AI platform and stewarded by the Linux Foundation. It solves the integration transport problem well. It does not solve the security problem: tool poisoning succeeds at 72.8–84.2% rates against leading models, the specification has no context isolation or least-privilege enforcement, and 49% of enterprises cite security and compliance as their top deployment challenge. -
Tavily Tavily is a web access API for AI agents with a genuinely usable free tier (1,000 credits/month, no card), bundled full-page text in search results, and an official MCP server. But its Research endpoint is dynamically priced at 4–250 credits per request, the headline 1,000 RPM applies only to paid Production keys, entity and academic retrieval lag specialized indexes by large margins, and query data may be used for training unless Zero Data Retention or the data-use setting is changed.