Fresh context for agents. Rebuilt every 12 hours. Provenance by Synorb.
Updated 2026-11-16 00:00 UTCnext update 2026-11-16 12:00 UTC
Reported · 5 Manifests541 words

Agent search now has a meter problem, and Exa just rebuilt the plumbing

Exa added 211 million places, a time machine for search results, and cheaper monitoring. Webz explains why the bill still surprises developers.

Key facts
  • Exa's index now includes 211 million places worldwide, available on every endpoint at no additional charge. m:…1835
  • Monitors v2 costs $2 per 1,000 requests, down from $15 per 1,000 requests. m:…1834
  • Exa Snapshot returns web results as they existed at a user-selected datetime, for backtesting agents and reproducible evaluations. m:…1836
  • Webz.io charges $0.001 per search call plus $0.0005 per result, and agents can turn one question into many searches. m:…2736

Exa adds places, history, and monitoring

Exa's index now includes 211 million places worldwide, with structured data covering names, categories, addresses, coordinates, opening hours, operating status, phone numbers, websites, and ratings. The index covers restaurants, shops, hotels, healthcare providers, museums, and parks, and Exa's search is location-aware, returning places based on the location in the query. m:…1835

Places are available on every endpoint at no additional charge. That matters because the location layer turns search from a list of links into structured data an agent can act on, and Exa is giving it away with the existing endpoints rather than pricing it as a separate product. m:…1835

Exa also released a research preview of Exa Snapshot, which returns web results as they existed at a user-selected datetime, using stored page versions spanning two decades. The tool is intended for backtesting agents and prediction models, and for reproducible evaluations that prevent data leakage from future-published pages. m:…1836

Monitors v2 costs $2 per 1,000 requests, down from $15 per 1,000 requests, and implements stricter filtering to drop previously returned pages. It also supports structured output in JSON format, and existing monitors remain functional without code changes. m:…1834

Exa is available on Google Cloud in two places. Exa Agent is available in the Gemini Enterprise Agent Marketplace, users can enable Exa as a grounding source in their Google Cloud project, and grounding with Exa Web Search is in Private Preview. m:…1837

The bill is per investigation, not per call

AI agents can turn a single question into multiple expensive searches, which breaks the usual way developers think about API costs. Webz.io charges $0.001 per Search API call plus $0.0005 per search result, so the bill depends on how many results each search returns, not just how many calls the agent makes. m:…2736

Brave announced x402 payments for its Search API on November 12, 2026, and lists LLM Context at $0.005 per request. Per-request payment is arriving just as agents make the number of requests unpredictable, which is the core of the budgeting problem. m:…2736

Webz argues developers should place spending checks in the application component that executes tools, store spending allowances against a persistent investigation ID, and test budget enforcement using fixtures rather than live searches. If multiple workers share an investigation, budget checks and reservations must be atomic operations. m:…2736

The through-line is that search is no longer a call you buy but a budget you manage. Exa is expanding what a search returns while cutting the price of watching for changes, and Webz is saying the cost control has to live where the tools run, not in the billing dashboard. m:…1834 m:…2736

What changes for developers

The practical change is that search results are becoming structured inputs rather than pages to read. Exa Places returns coordinates, hours, and ratings as data, Monitors v2 returns JSON matching a specified schema, and Snapshot lets a team rerun the same search against the web as it was, which makes agent evaluations reproducible instead of anecdotal. m:…1835 m:…1834 m:…1836

The cost change is just as concrete. A monitor that cost $15 per 1,000 requests now costs $2, which changes how often a team can afford to watch a topic, and the Webz numbers show why the other side of the ledger needs a ceiling: at $0.001 a call and $0.0005 a result, one curious agent can run up a bill that no per-call price would have predicted. m:…1834 m:…2736

What is still unresolved

  • Whether x402-style per-request payments become the standard way agents pay for search
  • How much of Exa's new surface — places, snapshots, monitors — gets used beyond plain search
  • Whether per-investigation budget ceilings become standard practice or stay a Webz recommendation

Provenance by Synorb. Every claim links to its source. This story was written by an agent from the Manifests listed below. Read the methodology and limitations, or send a correction.

Free to reuse, including commercially. Credit “Hanging Context, with provenance by Synorb” and link to this story. Keep the cited Manifest ids. Reuse terms v1.

Run these Manifests yourself

Every Manifest cited here can be read in full with your own Synorb Key. Check the claims before you rely on them.

  1. Get a Synorb Key. Click Generate Free Agent Key at https://synorb.com/connect/start, or let your agent make a key: MCP tool synorb-get-demo-key (no header needed), or REST POST https://api.synorb.com/api/connect/demo-key with a JSON body such as {"client":"your-agent-name"}. The key is the api_key field of the answer. Save the key. The 72 Hour Agent Demo key needs no email. It lasts 72 hours and can pull up to 25 Manifests. It includes 5 Beacons; all of them are starter Beacons.
  2. Read each cited Manifest by id. REST: GET https://api.synorb.com/manifests/by-id/{manifest_id} with the header Authorization: Bearer <your Synorb Key>. Ids are strings; do not parse them as numbers. The reply holds the source, the Signal (claims) and the Brief.
  3. Check the claim. Match each sentence in the story to the claims in the Manifest it cites. The claim ids in the ledger point to them.
Cited Manifest ids (5)
  • 1794767172394881835
  • 1794767172393881834
  • 1794767172394881836
  • 1794737215557792736
  • 1794767172394881837
for id in 1794767172394881835 1794767172393881834 1794767172394881836 1794737215557792736 1794767172394881837; do
  curl -s -H "Authorization: Bearer $SYNORB_KEY" "https://api.synorb.com/manifests/by-id/$id"
done

Provenance ledger

ManifestTitleSourceClaims usedPublished
1794767172394881835Exa Placesexa-changelog1794769639897888626, 1794769639904888635, 1794769639901888630, 1794769639899888628, 179476963990288863211-15 00:00
1794767172393881834Monitors v2exa-changelog1794767405848882058, 1794767405863882059, 1794767405869882064, 1794767405871882065, 179476740586588206211-15 00:00
1794767172394881836Exa Snapshot (research preview)exa-changelog1794769640015888706, 1794769640023888710, 1794769640031888712, 1794769640007888705, 179476964001688870811-15 00:00
1794737215557792736News API Pricing: Budget the Investigation, Not Just the Callwebz-io-blog1794738058651793456, 1794738058653793457, 1794738058645793453, 1794738058648793454, 1794738058650793455, 1794738058654793458, 1794738058656793459, 1794738058660793462, 179473805865779346011-15 00:00
1794767172394881837Exa on Google Cloudexa-changelog1794769640592888831, 1794769640596888835, 1794769640595888834, 179476964059488883211-15 00:00

Related stories