AI · 12 November 2026
Google Researcher Uses 48 AI Agents to Find Unmapped Maya Site in Mexico
A Google researcher used 48 AI agents to identify a previously unmapped Maya site in Mexico in under 72 hours, analysing NASA lidar data, according to TechRadar reporting. The case illustrates how dividing analysis across agents can make exhaustive data review practical.
What happened
A Google researcher used 48 AI agents to identify a previously unmapped Maya site in Mexico, completing the project in less than 72 hours, according to reporting by TechRadar. The agents were directed at NASA lidar data, the laser-based terrain scans that can reveal archaeological features hidden beneath vegetation.
The case is being presented as an example of how AI is reshaping research well beyond software and commerce, with archaeology offering a clear, datable illustration.
Why it matters
The technical shift here is less about any single discovery and more about how work gets divided. Instead of one analyst working through a large sensor dataset sequentially, a set of agents can split the search across the whole dataset at once. That makes exhaustive review practical for teams that previously lacked the time or headcount to attempt it, a pattern that applies equally to inspecting infrastructure, auditing records or reviewing service data.
It also changes where human effort is needed. Candidate findings still require expert verification, and the value of a fast system depends on how well its outputs can be checked. Organisations adopting agentic workflows will need clear rules for what agents can flag and what must be confirmed by people.
By the numbers
- 48 AI agents deployed on the project
- Under 72 hours reported from start of the project to the discovery
The Renascence take
Most coverage will focus on the speed and the novelty of the find. The more useful signal is the operating model underneath it.
The headline is about 48 agents working in under three days, but the real bottleneck has moved from analysis to validation. Any team deploying agents should design its review gates first, deciding which outputs are proposals and which are conclusions, before measuring throughput. Speed without a clear verification step simply produces faster errors. Customer-obsessed operators should treat agent output the way they would treat a new frontline colleague: useful, fast, and accountable only when someone checks the work.
Sources
This briefing was written by our Newsdesk, synthesising reporting from the outlets below. Follow the links for the original coverage.
FAQ
Questions we get on this topic
More in AI
Stay ahead of CX
Get the signal, not the noise.
The stories shaping customer experience — plus the Journal and Experience Loom — in your inbox.


