A drop-in endpoint
SerpKite serves GET /customsearch/v1 with the same query parameters (key, cx, q, start, num, gl, hl, lr, safe, dateRestrict, siteSearch, searchType) and the same response shape: kind, searchInformation and items[]. In most code the change is the host and the key.
Each call costs 1 credit, from $0.60 to $1.00 per 1,000 depending on the pack, and credits never expire.
What happens to cx
cx identifies a Programmable Search Engine configured in Google's console. We accept it so existing code doesn't break, but we ignore it: SerpKite searches all of Google, the way a logged-out user would. If your engine was limited to certain sites, add siteSearch or site: operators to the query.
Every other CSE parameter, such as exactTerms, fileType, sort or the image filters, is accepted as it is, so the tool keeps them in the URL. The table marks the few that are accepted and ignored.
When to switch to /v1/search
The native POST /v1/search endpoint returns more than CSE ever did: People Also Ask, knowledge graph, related searches, top stories, and LLM-ready Markdown. The helper prints the equivalent request so you can move over when you're ready. The full walkthrough is in the Custom Search migration guide.