SerpAPI through Squiid

What SerpAPI is

SerpAPI turns search engine results pages into JSON. It handles the proxying, CAPTCHA solving and parsing required to read a live results page, and returns organic results, ads, featured snippets, knowledge panels, people-also-ask blocks and the rest as labelled fields. Coverage goes well beyond web search: Google Maps listings and reviews, Shopping results with prices, Scholar citations, Images, News, Trends, and other engines including Bing, DuckDuckGo, YouTube and Amazon. Location parameters let you see results as they appear in a specific city, which is what makes local rank tracking meaningful.

The reason AI-coded products use it is that some data only exists on a results page. Local business listings with ratings, product prices across sellers, rank tracking for SEO tools, and academic citations are not available through a clean API anywhere else. It is also the pragmatic choice when a feature needs to reflect exactly what a user would see when they search, rather than a differently ranked index. Response shapes are stable and documented per engine, which matters when generated code parses them without a human checking.

Why connect it through Squiid

SerpAPI is on the Squiid roadmap. When it is connected, requests will go to https://api.squiid.io/v1/serpapi/... with Authorization: Bearer $SQUIID_API_KEY, with clients working by base URL swap (gateway convention), and searches will meter against prepaid credits at SerpAPI's listed price on one invoice. Rate limits and plan tier are handled on the Squiid side, so an agent making parallel requests does not need to know which plan you are on. Caching identical queries is also supported, which is worth enabling when the same search runs on a schedule.

• One account, one key, one bill, one dashboard. SerpAPI sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the SerpAPI credentials. Your code carries SQUIID_API_KEY, so SERPAPI_API_KEY, SERPAPI_KEY 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 SerpAPI 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

• Structured JSON from live search results pages
• Google Maps, Shopping, Scholar, News and Images
• Other engines including Bing and YouTube
• Searches metered against prepaid credits
• SerpAPI list pricing, no markup

How to connect SerpAPI

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 SERPAPI_API_KEY, SERPAPI_KEY
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

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

Pricing through Squiid

SerpAPI charges a monthly plan fee by search volume with overage priced per search, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of SerpAPI usage, with no markup and no per-request margin.

SerpAPI 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 SerpAPI 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: SerpAPI is usage-metered, so leaving means creating your own SerpAPI key and pointing the client at it. Squiid never owns your code, your schema or your domain, and the gateway speaks SerpAPI'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

SerpAPI 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 SerpAPI 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.