SERPpost V1

Google and Bing SERP data. Source capture in one V1 API.

Query Google and Bing result types, then capture public pages and files in structured responses. Create an account to test the request, parameters, and response fields your workflow needs.

100 credits · no credit card required · test V1 before you buy.

Request receipt

Google Search

POST /api/v1/search
{
  "s": "web to markdown api",
  "t": "google",
  "country": "us",
  "language": "en",
  "maxCache": 0
}

Expected result fields

organic relatedSearches aiOverview

maxCache: 0 asks for a fresh request. Response fields vary with the selected result type and the available search result.

One V1 surface

Choose the response shape before you write the workflow.

The endpoint stays consistent while the result type changes. Use search for result sets, or use the reader endpoint when your workflow needs a page, file, or screenshot.

Google Search

google

Get an organic result set for a query, with the surrounding search context when it is available.

Fields: organic, relatedSearches, aiOverview

Google Shopping

google_shopping

Inspect product listings when a query has commercial intent.

Fields: shopping_results

Google Images

google_images

Retrieve image results and related visual search suggestions.

Fields: images_results, suggestedSearches

Google News

google_news

Collect current news results for a topic without changing your search workflow.

Fields: news_results

Google Videos

google_videos

Find video results when the useful answer is better shown than read.

Fields: video_results

Google Short Videos

google_short_videos

Inspect short-form video results for a topic or emerging query pattern.

Fields: short_video_results

Bing Search

bing

Run a Bing query when you need a second search surface in the same integration.

Fields: organic

Reader endpoint

Bring the source into the workflow.

Send a public URL to the V1 reader endpoint when a result page is only the beginning of the task.

See reader parameters
web

Web Reader

Turn a public web page into usable Markdown, metadata, and HTML.

Fields: title, description, markdown, html

file

File Extraction

Extract readable content from a publicly accessible document URL.

Fields: title, description, fileUrl, fileMarkdown

screenshot

Web Screenshot

Capture a rendered page alongside machine-readable content.

Fields: title, description, markdown, imageUrl

A clear integration path

Inspect first. Integrate with fewer surprises.

  1. 1

    Select a result type

    Start with the surface your product needs: web, shopping, images, news, video, short video, Bing, or reader capture.

  2. 2

    Review the request and fields

    The playground displays the endpoint, parameters, and response shape so the work can be tested before it reaches production.

  3. 3

    Keep the key server-side

    Use the dashboard to manage access and Request Slots; call the API from your server, not from a public browser bundle.

Plans and capacity

Choose the credits and Request Slots that fit the workload.

All plans use the V1 search and reader surface. Review the pricing details before you buy, then test the request that matters to your workflow.

Credit pack

Standard

For low-volume live usage

$18.00
$0.90/1k credits
Credits
20,000
Included usage volume
Request Slots
2
Live requests at once
What you get
  • Shared credit pool across core endpoints
  • 2 Request Slots included
  • Does not stack
  • Credits valid for 6 months
Credit pack
Recommended

Starter

For early scaling teams

$99.00
$0.75/1k credits
Credits
132,000
Included usage volume
Request Slots
5
Live requests at once
What you get
  • Shared credit pool across core endpoints
  • 5 Request Slots included
  • Stacks with more paid packs
  • Credits valid for 6 months
Credit pack

Pro

For growing automation

$597.00
$0.60/1k credits
Credits
995,000
Included usage volume
Request Slots
37
Live requests at once
What you get
  • Shared credit pool across core endpoints
  • 37 Request Slots included
  • Stacks with more paid packs
  • Credits valid for 6 months
Credit pack

Ultimate

For heavy live usage

$1680.00
$0.56/1k credits
Credits
3,000,000
Included usage volume
Request Slots
113
Live requests at once
What you get
  • Shared credit pool across core endpoints
  • 113 Request Slots included
  • Stacks with more paid packs
  • Credits valid for 6 months
Pricing built for real usage

Pick the credit pack that fits your current usage

Every paid order unlocks the same core platform. What changes is how many credits and live requests at once you get.

Need more live requests at once? Starter, Pro, and Ultimate can add their slots together.

Request Slot example
2x Starter = 10 Request Slots

1x Starter + 1x Pro = 42 Request Slots. Standard stays fixed at 2 slots.

Request Slot rules
Request Slots = how many live requests you can run at once.
Starter, Pro, and Ultimate stack when you buy more paid packs.
Standard stays fixed at 2 slots.
100 free credits
100 credits • 1 Request Slot

Useful for auth checks, first-call validation, and lightweight search-result or source-capture testing. If your team already knows it will exceed that window, move directly to a paid pack.

Need more than 100 credits for testing?

Contact the SERPpost Team if your validation scenario needs a larger controlled window before purchase, or if you want a recommendation based on expected credits and live request needs.

Recommended buying logic: verify the integration with free credits, then choose the paid pack that matches your real credit usage and live request needs.
Before you buy

Understand the request, capacity, and next step.

Use the playground and V1 docs to validate the endpoint you need. Pricing and Request Slots remain visible before checkout.

Get started without a credit card

New users get 100 free credits to validate real requests before buying a paid pack.

Predictable pay-as-you-go buying

Buy credits only when you need them. There are no forced subscriptions, and every paid pack keeps the same core platform access.

More live requests when you need them

Starter, Pro, and Ultimate can add more Request Slots across paid packs, so your live request capacity can grow with usage.

Samples, docs, and support are ready

Use sample outputs, docs, and the SERPpost Team when you need help with credits, Request Slots, V1 request setup, or source-capture validation.

From the blog

Practical notes for search and source capture workflows.

View all articles