Every week, another thread on X or Hacker News debates which frontier model is cheapest per million tokens — GPT-4o vs Claude Sonnet vs Gemini Flash, racing toward fractions of a cent per request. Founders still pitch "AI-powered content" as if the expensive part of publishing is getting a language model to emit paragraphs.

Over the last six weeks, we built tabiji.ai — 386 local restaurant and activity guides, 324 travel itineraries, 706 destination pages, and 200+ short-form videos. After auditing our actual cloud and API bills, the conclusion is unmistakable: LLM token costs are a rounding error. Data enrichment is the real expense.

TL;DR

Across 1,400+ AI-produced travel pages and 200+ short-form videos, LLM text tokens account for just ~20% of our monthly bill (~$80/mo) — the other 80% goes to ground-truth data enrichment and media rendering.

  • Per-page unit economics — A curated local guide costs ~$0.50 in Google Places API calls and ~$0.30 in SerpAPI photo sourcing, vs. ~$0.02 in LLM writing tokens (4% AI text, 96% data layer).
  • Real cloud receipts — Our March 1–18, 2026 Google Cloud bill hit $333.92 ($209.60 Gemini API including vision/image scoring, $126.04 Places API at $32 per 1,000 requests).
  • The real moat — Anyone can prompt an LLM for a listicle; defensibility comes from enriching 3,755 venues with live ratings, verified hours, and real Reddit quotes.

The Numbers Nobody Talks About

Here is our actual monthly spend to run the content pipeline at scale:

Category What It Does Monthly Cost
LLM tokens (Gemini, Claude, GPT) Writing, structuring, reasoning ~$80
Image generation (Gemini Flash) Hero images, social graphics ~$15
Google Places API Ratings, hours, contact info, reviews ~$115
SerpAPI (Google Search + Images) Photo sourcing, research validation ~$50
Video generation (MiniMax / Veo) Instagram Reels, YouTube Shorts ~$120
Cloudflare Pro + R2 storage CDN, image hosting, deployment ~$25
Music generation (Suno) Background audio for video ~$10

LLM text generation — the line item everyone benchmarks — is roughly 20% of our monthly stack (~$80 of ~$415). Data enrichment and media rendering account for the other 80%.

Google Cloud billing report showing $333.92 in API costs for March 1-18, 2026 — Gemini API $209.60, Places API $126.04
Our actual Google Cloud bill — March 1-18, 2026. Gemini API: $209.60. Places API: $126.04. The data enrichment layer is real.

Why a 4.8-Star Rating Costs More Than a 1,000-Word Article

Any model can write plausible prose about "the best ramen in Tokyo" in three seconds. What makes a local guide trustworthy is the verification and enrichment pipeline underneath:

  • Google Places API — For each of the ~15 venues on a guide, we query the Places API for live ratings, review counts, opening hours, phone numbers, price tiers, and direct Google Maps links. At $0.032 per call, 15 venues cost roughly $0.50 per page.
  • Reddit sourcing — Every recommendation is anchored in real threads from subreddits like r/JapanTravel or r/FoodNYC, complete with upvotes, timestamps, and verbatim quotes that no model can pull from weights alone.
  • Photo sourcing and vision scoring — Each venue needs an authentic photo. We query Google Images via SerpAPI, download candidates, score them with a vision model for relevance and lighting, then compress and push to Cloudflare R2 — five API calls plus a vision pass per venue.
  • Schema markup — Every page ships with JSON-LD structured data containing live aggregateRating fields so search and answer engines can parse verified star ratings directly.

Add it up: a single popular-picks page costs ~$0.50 in Places API calls, ~$0.30 in search and photo sourcing, and ~$0.02 in LLM tokens for the copy. Text generation is 4% of the unit cost. The data layer is 96%.

The Data Moat Nobody Sees

That inverted cost structure is a feature, not a bug: expensive data enrichment creates an actual moat.

Anyone can ask Claude for "10 Best Restaurants in Barcelona" and publish another generic AI listicle. What they can't replicate with a single prompt is our enriched dataset: 3,755 venues cross-referenced with live Google ratings, timestamped Reddit quotes, verified opening hours, and vision-scored photos.

Our earliest tabiji.ai itineraries were pure LLM output — clean prose, zero hallucinations of syntax, and completely generic recommendations recycled from pre-training data. Once we wired in live enrichment from Google Places, Reddit, and Foursquare, the pages crossed from commodity prose into ground truth. Showing that Klimataria in Athens holds a 4.5 rating across 3,200 reviews and stays open until 11 PM on Thursdays isn't "AI creativity." It's a paid API lookup — and it's the exact detail that makes a traveler trust the page.

Video Makes It Even More Obvious

Our Instagram Reels pipeline ships 20+ videos a day across 10 formats, and the per-video unit economics tell the same story:

  • MiniMax video generation: ~$0.27 per 8-second clip
  • Image generation for I2V input: ~$0.01 per image
  • Text overlay + FFmpeg compositing: $0 (local compute)
  • Music generation: ~$0.01 per track
  • LLM for script/hook writing: ~$0.005 per video

Right now, the video model accounts for 93% of the per-clip cost only because video inference hasn't commoditized as fast as text. Give it six months. Long after video generation drops to a penny per clip, the research layer — finding the exact local scam to warn tourists about and verifying the cultural context — will remain the real work.

What This Means for Anyone Building with AI

If you're building an AI publishing pipeline, plan around one rule: your text model costs will fall to zero, while your ground-truth data costs won't.

Gemini Flash already writes clean copy for fractions of a cent, and image models are right behind it. Meanwhile, Google Places still charges $32 per 1,000 requests, SerpAPI still bills per search, and curating trustworthy Reddit threads or venue photos still takes multi-step verification pipelines that dwarf the cost of drafting the prose.

The model is the pen. The data is the ink. Everyone's arguing about the pen.

We expose our enriched catalog as a free static API — 1,428 JSON files covering 706 destinations and 3,755 curated places. Assembling and verifying that data cost orders of magnitude more than the LLM tokens used to write the pages. Stop optimizing for token pennies, start investing in your data layer — and make sure your pipeline doesn't suffer from structural drift at scale.