Skip to the page

25,280 files on GitHub still call Google’s Custom Search API

Google closes the Custom Search JSON API on January 1, 2027 (its documentation). On November 20, 2026 we counted the public code that still calls it.

The count

Totals from GitHub’s code search for each exact phrase, on November 20, 2026.

25,280
files contain the API’s address, googleapis.com/customsearch/v1
18,464
files read a GOOGLE_CSE_ID setting
8,368
files use LangChain’s GoogleSearchAPIWrapper
42
days from this count to the shutdown

By language

Files that contain the API’s address, by the language GitHub assigns to the file.

Language
Files
Python
10,208
JavaScript
5,008
TypeScript
3,028
PHP
659
Java
550
C#
352
Go
342
Ruby
155

Active projects that hold the call

Eight of the projects with more than 1,000 stars whose code contains the API’s address and that were pushed to in the last year. Some offer it as one search provider among several.

Project
What it is
Stars
apache/camel
Integration framework with 350+ connectors
6,418
ANative-Lab/EvoAgentX
Framework for self-evolving AI agents
3,447
aandrew-me/tgpt
AI chat in the terminal
3,299
swirlai/swirl-search
AI search across company apps
3,048
AnotiaWang/deep-research-web-ui
Deep research agent with cited reports
2,228
limecloud/lime
AI agent for coding and research
1,496
moyangzhan/langchain4j-aideepin
AI application platform in Java
1,405
ALwrity/ALwrity
AI marketing and content platform
1,227

What the numbers say

  • Python carries the most10,208 of the 25,280 files are Python, followed by JavaScript with 5,008 and TypeScript with 3,028.
  • One LangChain class accounts for 8,368 filesGoogleSearchAPIWrapper, LangChain’s wrapper around the API, appears in 8,368 files. Every agent built on it stops searching on the same day.
  • 7,072 files build the call with the key in the addressThey contain customsearch/v1?key=, the simplest form of the call. These are the easiest to move: the request stays the same and only the address and the key change.
  • Google’s own replacement covers 50 domainsGoogle points existing customers to Vertex AI Search for up to 50 domains and asks those who need the whole web to contact it. There is no drop-in for whole-web search from Google.

Move in one line

SpecStream answers the Custom Search request as it is. Change the base address to api.specstream.ai and the key, and the code keeps its JSON. The steps are in the migration guide, with guides for open-source apps that use Google’s search. Related data: public repositories.

Questions

Something we didn't answer? Talk to a human

When does the Google Custom Search JSON API shut down?
Google’s documentation says existing customers have until January 1, 2027 to move to another solution. The API is already closed to new customers.
How much public code still uses the Google Custom Search JSON API?
On November 20, 2026 GitHub’s code search counted 25,280 files that contain the API’s address, googleapis.com/customsearch/v1, and 18,464 files that read a GOOGLE_CSE_ID setting.
What replaces the Google Custom Search JSON API?
Google suggests Vertex AI Search for up to 50 domains. For search of the whole web, SpecStream answers the same request at its own address: change the base address and the key and keep the rest of the code.
What does the replacement cost?
Google charged $5 per 1,000 queries after 100 free queries a day. SpecStream’s drop-in route costs $1 per 1,000 searches of up to 10 results.
How were the files counted?
Each number is the total GitHub’s code search reported for one exact phrase on November 20, 2026. GitHub’s totals are its own estimates and include forks and copies.

Keep your search working after January 1

One address and one key change. $1 per 1,000 searches on the drop-in route.