# Changelog

> SerpCrypto changelog: dated changes to the SERP API, its fields, prices and policies, and how breaking changes are announced. Credits never expire. No KYC.

- URL: https://serpcrypto.com/changelog/
- Last updated: 2026-10-22
- Publisher: SerpCrypto (https://serpcrypto.com)

Every change that a customer or a parser could notice is written here with a date: new fields, engines, prices, policy updates and incidents.

**Quick answer — What has changed at SerpCrypto, and when?**

On 2026-10-22 **SerpCrypto** published its website, its API documentation for `https://serpcrypto.com/api/v1/search`, its price grid (from $7.50 for 10,000 searches down to $0.30/1K searches) and its policies. The API and the client area open on the date announced in this log. Every later change to fields, engines, prices or policies is recorded here.

## Change log

| Date | Area | Change |
| --- | --- | --- |
| 2026-10-22 | Website | Website and API documentation published: quick start, search reference, response format, locations, errors, and code for Python, Node.js and curl. The API and the client area open on the date announced in this log. |
| 2026-10-22 | Prices | First price grid published: seven credit packs from 10,000 searches ($7.50) to 5,000,000 searches ($1,500). Credits never expire. |
| 2026-10-22 | Policies | Terms of service, privacy policy, refund policy and Acceptable Use Policy published. |

## What kinds of changes are logged?

- **API fields:** a new block or field in the JSON, or a change in how an existing field is filled.
- **Engines and parameters:** an engine or a parameter value added, renamed or retired.
- **Prices:** any change to a pack price or size, with the date it applies. Packs already bought keep their credits.
- **Policies:** terms, privacy, refunds and acceptable use, with a one-line summary of what changed.
- **Incidents:** a period when an engine or the client area failed for many customers, and what was done.

## How are breaking changes to the API handled?

The version is part of the path: `https://serpcrypto.com/api/v1`. Within this version, new fields can appear at any time, so a parser should ignore fields it does not know. A field that a parser may rely on is not renamed or removed within the version without a dated entry in this log first.

Some changes come from the engines themselves. When Google stopped honouring `num=100` in September 2025, collecting 100 results started to take 10 requests instead of one. When an engine changes its page in a way that affects a block, the entry says which block and from which date.

## How do prices change?

A new price applies to packs bought after the date in the log. It never reduces the credits already on an account, because credits are counted in searches, not in dollars. Prepaid search credits never expire: unused searches stay on your account until you use them. The current grid is always on the [pricing page](https://serpcrypto.com/pricing/) and in the machine-readable [pricing.json](https://serpcrypto.com/pricing.json) file.

## How can I follow this log?

Check this page, or read its Markdown version, which carries the same table and is easy to diff. The [status page](https://serpcrypto.com/status/) explains how to test the API yourself when you suspect an incident. Questions about an entry go to support@serpcrypto.com; Email replies within 12 hours, 7 days a week, including help with API integration.

---

SerpCrypto: SerpCrypto is a SERP API for developers and AI agents that returns Google and Bing results as JSON, paid in crypto with no ID upload. Prepaid search credits from $0.30/1K searches never expire. No KYC — no ID, no selfie, no documents. Pay in crypto.