Pricing
Apply for one of 10 complimentary Beta seats. Every paid plan includes Google, Bing, Yahoo, DuckDuckGo, Yandex, Baidu, Brave, and Naver. General page scraping is on the roadmap. New here? Read what Serpent API is, follow the quickstart, or watch engine status.
Want token costs and billing details? Pricing & Tokens
You need to be signed in to subscribe
You need to be signed in to subscribe
You need to be signed in to subscribe
Create an account after you're approved, or subscribe to a paid plan. Or read the docs and quickstart first.
FAQ
Engines, tokens, rollover, refunds, and how teams go from API key to production.
Serpent API (SerpentAPI) is a real-time SERP API at serpentapi.com. Developers use it to pull structured organic search results from Google, Bing, Yahoo, DuckDuckGo, Yandex, Baidu, Brave, and Naver through one REST API. General page scraping and MCP for AI agents are on the roadmap. See What is Serpent API? or the docs.
SerpentAPI returns structured organic results from Google, Bing, Yahoo, DuckDuckGo, Yandex, Baidu, Brave, and Naver through one API. Switch engines with a single parameter — same request shape and result schema.
Not yet. General page scraping (arbitrary URLs after SERP discovery) is on the roadmap— planned as a secondary endpoint on the same API key and bill. Today, SerpentAPI ships real-time SERP search across eight engines.
Maintaining proxies, captchas, layout changes, and eight engine quirks is expensive. SerpentAPI gives you structured JSON, one integration, predictable pricing, and a status page backed by production traffic — so your team ships product instead of fighting HTML.
We publish live uptime on our public status page. Platform target is 99.9%. Engine availability can vary with upstream search sites; the status page breaks this down per engine.
Yes — a free Beta plan with 10 seats by application. Beta includes all eight SERP engines, 2,500 tokens/month, and 10 requests/minute. Apply at /beta. Paid plans start at Professional ($79/mo).
Each successful API call consumes tokens based on the request. Plans include a monthly allotment — Beta 2,500, Professional 15,000, Business 50,000, and Enterprise 150,000 tokens. Paid plans are billed monthly. A portion of unused tokens can roll over (see below). You can monitor usage in the dashboard and upgrade anytime if you need more throughput.
Yes. At the end of each billing period, 30% of your unused tokens roll into the next month. Rollover tokens must be used in that following month — they do not roll again. We always consume rollover tokens before your new monthly allotment. Your total available balance is capped at 130% of your plan’s monthly tokens (for example, Professional caps at 19,500). If you barely use a month, that 30% rollover is how you land at the 130% cap — unused rollover simply expires when the next period ends.
Rate limits match live search capacity: Beta 10 requests/minute, Professional 30/minute, Business 60/minute, and Enterprise 120/minute. Higher plans also get priority async queues. Need more? Contact us for custom throughput.
Yes. If you cancel and request a refund during an active billing period, we calculate usage at your plan’s standard rate (monthly price ÷ monthly token allotment), deduct the value of tokens already used, and refund the remaining unused balance to your original payment method. Refunds are typically processed within 5–10 business days. Abuse, chargebacks after a refund, or accounts terminated for Terms violations may be ineligible.
Example: on Professional ($79 ÷ 15,000 tokens), unused tokens are refunded at that plan rate after deducting tokens already consumed.
Yes. Cancel from the billing portal whenever you want. Access continues through the end of the paid period unless you request a prorated refund (see our refund policy above). No long-term contracts on standard plans.
Most developers are live in minutes: sign up, pick a plan, copy an API key, and POST to the search endpoint. Full examples for curl, Node, Python, and more are in the docs.
Create an account, subscribe to a plan, generate an API key in the dashboard, and send it on every request with the x-api-key header. Keys are shown once at creation — store them securely and rotate if compromised.
Still unsure? support@serpentapi.com · Docs · Pricing · Blog · Status