Firecrawl through Squiid

What Firecrawl is

Firecrawl converts websites into text a model can use. The scrape endpoint renders a single page, including JavaScript-heavy ones, and returns markdown, HTML or a screenshot. The crawl endpoint walks an entire site and returns every page, with include and exclude patterns and a depth limit. The extract endpoint takes a JSON schema and pulls structured fields out of a page, and a map endpoint lists a site's URLs quickly. Proxies, retries and rate limiting are handled for you. Actions let you click, scroll or wait before the content is captured, which handles pages that hide their content behind an interaction.

For agentic coding this is how documentation becomes context. Pointing Firecrawl at a library's docs site produces markdown you can chunk, embed and query, which is the standard way to give an agent accurate knowledge of an API it was not trained on. Other uses are competitor page monitoring, pulling pricing tables into a comparison, and turning a customer's website into a knowledge base during onboarding. Change tracking on repeated scrapes is the other common use, because it answers what moved on a page since yesterday.

Why connect it through Squiid

Crawls are the expensive shape, because a site with ten thousand pages costs ten thousand pages. Squiid meters Firecrawl against prepaid credits at the provider's list price and shows pages consumed per day, so a crawl that escaped its include pattern is visible immediately. Requests go to https://api.squiid.io/v1/firecrawl/... with Authorization: Bearer $SQUIID_API_KEY, the SDKs work by pointing their base URL at the gateway (gateway convention), and the spend appears on one invoice.

• One account, one key, one bill, one dashboard. Firecrawl sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Firecrawl credentials. Your code carries SQUIID_API_KEY, so FIRECRAWL_API_KEY, FIRECRAWL_BASE_URL never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Firecrawl costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• Clean markdown from JavaScript-rendered pages
• Whole-site crawling with include and exclude rules
• Schema-based structured extraction
• Pages metered against prepaid credits
• Firecrawl list pricing, no markup

How to connect Firecrawl

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces FIRECRAWL_API_KEY, FIRECRAWL_BASE_URL
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/firecrawl/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Firecrawl charges credits per page scraped or crawled on plan tiers, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Firecrawl usage, with no markup and no per-request margin.

Firecrawl has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Firecrawl usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Nothing to move: Firecrawl is usage-metered, so leaving means creating your own Firecrawl key and pointing the client at it. Squiid never owns your code, your schema or your domain, and the gateway speaks Firecrawl's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Firecrawl through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Firecrawl usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.