Updated 28 Aug 2026: Adds YepAPI's separate August 22 list-price increase on selected flat-rate and volume-priced endpoints, so the dossier distinguishes the billing-defect correction from the simultaneous change in the documented prices customers now actually pay.

Key details

  1. The billing defect was fixed on August 22, 2026.
  2. Every flat-rate endpoint had been charged at $0.01 per call regardless of its listed price, according to YepAPI.
  3. Historical usage will not be rebilled.
  4. YepAPI separately raised selected list prices on August 22, including Phone Finder $0.05→$0.10, Email Finder $0.02→$0.04 and Domain Overview $0.04→$0.08.
  5. Several keyword, competitor, backlink and content endpoints also moved to new base-plus-volume pricing schedules.
  6. Volume-priced endpoints were unaffected by the flat-rate billing defect itself.
  7. Current API Logs show the cost of individual requests, and volume-priced endpoint pages now include worked pricing tables.

What builders should take away

  1. Recalculate unit economics using YepAPI's current August 22 pricing table rather than pre-August invoices or older docs; for some endpoints both the billing behavior and list price changed at once.
  2. Add budget alerts or cost-per-call checks where an endpoint’s corrected/current price materially changes the margin of a product feature.
  3. Use API Logs to sample actual request charges against the pricing reference, especially after product or pricing updates.
  4. Preserve historical billing data separately when comparing cost trends because August 22 creates an accounting discontinuity rather than a traffic change.
  5. If downstream customers are charged on a pass-through or margin basis, review whether the corrected supplier price and the separate list-price increases require packaging or pricing changes.

What changed

YepAPI disclosed and fixed a billing-layer defect on August 22, 2026. Every endpoint using flat-rate pricing had been falling through to a $0.01-per-call default instead of charging the price listed in its documentation. The company says current requests now bill at the documented rate and that it will not rebill historical usage. Separately, YepAPI published a pricing update the same day that raised list prices on nine flat-rate endpoints and on several keyword, competitor, backlink and content volume tiers. For example, Phone Finder moved from $0.05 to $0.10, Email Finder from $0.02 to $0.04 and Domain Overview from $0.04 to $0.08. The correction and the price increase are distinct changes: the first makes billing match the docs, while the second changes what the docs say selected calls should cost.

Why it matters

For affected customers this is more than a cosmetic documentation correction. A workload that had actually been billed $0.01 per call can now jump to a corrected listed rate, and on selected endpoints that listed rate itself also increased on August 22. Builders who inferred production unit economics from historical invoices can therefore see a sharper cost change than the original billing-defect disclosure alone implied. The no-retroactive-charge decision removes historical liability, while request-level cost visibility and explicit pricing tables make future reconciliation easier.

The bug affected the whole flat-rate pricing path

YepAPI says the billing layer ignored each flat-rate endpoint’s configured price and applied the $0.01 default instead. The company describes the defect as affecting every flat-rate endpoint, not a handful of products or customer accounts. Endpoints priced according to rows returned were billed correctly throughout.

A separate pricing update changed selected list prices

YepAPI also changed documented prices on August 22. Phone Finder doubled from $0.05 to $0.10; Email Finder, Author Finder and LinkedIn Finder moved from $0.02 to $0.04; Domain Overview moved from $0.04 to $0.08; Backlinks Summary from $0.03 to $0.05; Content Summary from $0.02 to $0.05; and Maps Photo from $0.01 to $0.02. Keyword, competitor and domain-keyword endpoints also moved to a higher base-plus-per-100-results schedule, while backlink and content endpoints adopted a new volume schedule.

The correction can create a larger step-change in live costs than it first appeared

From August 22, the documented amount is the charged amount. Because some documented amounts also increased on that date, customers whose traffic centered on affected endpoints may be moving from the historical $0.01 defect rate to a newly higher list price in one step. YepAPI is not applying either change retroactively to earlier usage.

Volume pricing is becoming more inspectable too

YepAPI added explicit tables to volume-priced endpoint pages showing a base request price plus row-based charges with examples at several result sizes. It also exposes request-level cost in API Logs. Those changes give customers stronger tools to reconcile documentation, usage and billing after both the defect correction and the pricing update.

What to watch next

  • Whether YepAPI makes further pricing changes after customers reconcile the August 22 correction.
  • Whether YepAPI identifies how long the flat-rate defect had been present.
  • Whether request-level cost data becomes available through an API for automated cost monitoring.

Still unclear

  • YepAPI has not stated when the flat-rate billing defect began.
  • The impact varies by endpoint and usage mix because only some documented prices changed on August 22 and only flat-rate endpoints were affected by the underbilling defect.
  • The disclosures are first-party; no independent billing audit was available in the research window.

Sources

Direct reading behind this dossier.

2 sources

Discussion

Discussion is reader-contributed. Comments are not part of the BTN dossier or its editorial evidence.

0 visible comments

Join the discussion

Keep comments useful and relevant. Reader contributions may be moderated and are not BTN editorial evidence.

Sign in to comment