Frequently Asked Questions

SERPpost V1 provides Google and Bing result types plus public page, file, and screenshot capture in one API surface. It is for teams that need search results and source content in the same workflow.

Create your account, claim 100 free credits, get your API key from the dashboard, and validate a real request in the playground or docs examples. Once the setup is proven, move to a paid pack when you need more credits or more live requests.

No. You can create an account and receive 100 free credits without entering a card. Payment details are only needed when you decide to buy a paid credit pack.

SERPpost uses a shared credit pool across its V1 search and Reader endpoints. Validate a real request first, then use pricing to choose the paid pack that matches your expected credits and Request Slots.

Yes. Paid credits are valid for 6 months from the date of purchase. That gives teams room to use a pack across real work instead of forcing a monthly subscription model.

Yes. Starter, Pro, and Ultimate can add their Request Slots across eligible paid orders, so you can run more live requests as your usage grows. Standard keeps a fixed 2-slot allocation and does not work the same way.

SERPpost offers a full refund within 7 calendar days of payment if no more than 20% of the plan usage has been consumed. Beyond that window or usage threshold, purchased credit packages are non-refundable.

Request Slots tell you how many live requests you can run at once. 100 free credits include 1 Request Slot, Standard includes a fixed 2-slot allocation, and larger paid packs give you more room for production use.

Use Bearer authentication. Generate your API key in the dashboard and send it in the Authorization header of each request. The docs examples follow the same auth pattern you should reuse in production.

Use the Playground to inspect a V1 request shape and response format before you wire SERPpost into your own application. It lets you validate the output your workflow needs before you buy a larger pack.

Yes. You can cache results in your own app when that fits your use case. Most teams keep SERPpost as the live request layer, then add their own storage, retry, and queueing rules around repeatable jobs.

Usually only for lightweight validation. New users get 100 free credits and 1 Request Slot, which is enough to verify auth, sample output, and first-call behavior. If your team already knows the usage will be larger, move to a paid pack or contact the team for guidance.

Use the contact page or email support@serppost.com when you need help choosing a paid pack, planning your Request Slots, or validating a larger testing scenario. Support is centered on product usage, buying guidance, docs, and troubleshooting.

Use pricing for pack comparison, docs for implementation detail, the playground for live samples, and terms for payment and refund policy. Those pages are the right places to verify the current buying and usage rules before you commit.