Google Search
google Get an organic result set for a query, with the surrounding search context when it is available.
Fields: organic, relatedSearches, aiOverview
SERPpost V1
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
{
"s": "web to markdown api",
"t": "google",
"country": "us",
"language": "en",
"maxCache": 0
} Expected result fields
maxCache: 0 asks for a fresh request. Response fields vary with the selected result type and the available search result.
One V1 surface
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 Get an organic result set for a query, with the surrounding search context when it is available.
Fields: organic, relatedSearches, aiOverview
google_shopping Inspect product listings when a query has commercial intent.
Fields: shopping_results
google_images Retrieve image results and related visual search suggestions.
Fields: images_results, suggestedSearches
google_news Collect current news results for a topic without changing your search workflow.
Fields: news_results
google_videos Find video results when the useful answer is better shown than read.
Fields: video_results
google_short_videos Inspect short-form video results for a topic or emerging query pattern.
Fields: short_video_results
bing Run a Bing query when you need a second search surface in the same integration.
Fields: organic
Reader endpoint
Send a public URL to the V1 reader endpoint when a result page is only the beginning of the task.
See reader parametersweb Turn a public web page into usable Markdown, metadata, and HTML.
Fields: title, description, markdown, html
file Extract readable content from a publicly accessible document URL.
Fields: title, description, fileUrl, fileMarkdown
screenshot Capture a rendered page alongside machine-readable content.
Fields: title, description, markdown, imageUrl
A clear integration path
Start with the surface your product needs: web, shopping, images, news, video, short video, Bing, or reader capture.
The playground displays the endpoint, parameters, and response shape so the work can be tested before it reaches production.
Use the dashboard to manage access and Request Slots; call the API from your server, not from a public browser bundle.
Plans and capacity
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.
For low-volume live usage
For early scaling teams
For growing automation
For heavy live 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.
1x Starter + 1x Pro = 42 Request Slots. Standard stays fixed at 2 slots.
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.
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.
Use the playground and V1 docs to validate the endpoint you need. Pricing and Request Slots remain visible before checkout.
New users get 100 free credits to validate real requests before buying a paid pack.
Buy credits only when you need them. There are no forced subscriptions, and every paid pack keeps the same core platform access.
Starter, Pro, and Ultimate can add more Request Slots across paid packs, so your live request capacity can grow with usage.
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