The Problem
Web search tools that scrape and return full cleaned pages blow up your token bill. A Hermes user in r/hermesagent put it plainly this week: a Firecrawl-style API "burns credits fast." The hidden cost isn't only the search API's price; it's the thousands of tokens of page text you then feed the model on every call. Pull five full articles into context per query and your LLM bill, not your search bill, becomes the line item that hurts. The token bloat is the tax nobody quotes you up front.
The Scavio Solution
Return structured SERP fields instead of full pages, cache the queries that repeat, and pay per-credit so light calls cost less than heavy ones. A SERP API gives the model titles, snippets, domains, and the knowledge graph, which is usually enough to answer or to decide which one page is worth fetching in full. You fetch the full page only when the snippet isn't enough, instead of dumping five every time. Scavio's /api/v1/google returns those fields as typed JSON; verified live on 2026-06-26, one full-SERP call came back with 7 organic results plus 8 related searches and knowledge-graph/news/shopping blocks at 2 credits. Snippets first, full fetch on demand, cache the hot queries.
Before
Agent calls a scrape-and-clean API on every query, pulls 5 full pages (~8,000+ tokens) into context each turn, and pays for that token bloat on every single LLM call. Search bill looks fine; the model bill quietly doubles.
After
Agent calls a SERP API, gets structured snippets (~hundreds of tokens), answers from them or fetches one full page only when needed. Hot queries hit a short-TTL cache and cost nothing. Token usage per grounded answer drops by most of the page-text overhead.
Who It Is For
Anyone running an agent that calls a scrape-and-clean search API on every turn and watching their LLM token bill climb faster than their search bill. If you genuinely need full-page JavaScript-rendered content (behind-auth dashboards, heavy SPAs), keep a crawler for those targets; this is about not paying the page-text tax on the 80% of queries a snippet answers.
Key Benefits
- Structured snippets cost a fraction of full-page text in context tokens
- Per-credit billing: a light Google call is 1 credit, full SERP is 2, you don't overpay for cheap queries
- Caching repeat queries removes the call entirely; pricing/news need short TTLs, definitions can cache for a day
- One key across Google, Reddit, YouTube, Amazon, Walmart, and TikTok so you don't multiply vendor bills
- Fetch full page content only on demand, not by default, which is where the token savings actually come from
Python Example
import os, requests
KEY = os.environ['SCAVIO_API_KEY']
r = requests.post(
'https://api.scavio.dev/api/v1/google',
headers={'Authorization': f'Bearer {KEY}'},
json={'query': 'kubernetes 1.31 release date', 'light_request': True},
).json()
# 1-credit light call; snippets only, no page bloat
for x in r['results'][:3]:
print(x['title'], '-', x['domain'])JavaScript Example
const KEY = process.env.SCAVIO_API_KEY;
const r = await fetch('https://api.scavio.dev/api/v1/google', {
method: 'POST',
headers: { Authorization: `Bearer ${KEY}`, 'Content-Type': 'application/json' },
body: JSON.stringify({ query: 'kubernetes 1.31 release date', light_request: true }),
}).then((x) => x.json());
for (const x of r.results.slice(0, 3)) console.log(x.title, '-', x.domain);