Beyond the News
Sign in
SaaSPricing & Billing Active dossier

YepAPI fixed a billing bug that had undercharged every flat-rate endpoint

YepAPI says every flat-rate endpoint had been charging $0.01 per call regardless of its documented price. The defect was fixed August 22 with no retroactive rebilling, so some workloads can see an immediate per-call cost increase to the listed rate.

Reviewed and published by Lars Jansen Updated 4 min read
First published

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. Volume-priced endpoints were unaffected by the defect.
  5. Current API Logs show the cost of individual requests.
  6. Volume-priced endpoint pages now include worked pricing tables.

What builders should take away

  1. Recalculate unit economics using the current documented price for every YepAPI flat-rate endpoint in production; do not project future spend from pre-August-22 invoices.
  2. Add budget alerts or cost-per-call checks where an endpoint’s corrected 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 requires 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. Volume-priced endpoints were not affected by the defect; YepAPI also added worked pricing tables for those endpoints and now shows per-call cost in dashboard API logs.

Why it matters

For affected customers this is not a cosmetic documentation correction: an endpoint documented at $0.05 per call but historically billed at $0.01 now costs five times as much per successful call. Builders who inferred their production unit economics from actual invoices rather than the published price can therefore see an immediate margin or budget change without any API behavior changing. The no-retroactive-charge decision removes historical liability, while the added per-request cost visibility makes it easier to detect future discrepancies.

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.

The correction can create a step-change in live costs

From August 22, the documented amount is the charged amount. That means customers whose traffic centered on endpoints listed above $0.01 may see higher bills immediately even though request volume and endpoint behavior are unchanged. YepAPI is not applying the correction retroactively.

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 do not repair the flat-rate defect by themselves, but they give customers stronger tools to reconcile documentation, usage and billing.

What to watch next

  • Whether YepAPI identifies how long the flat-rate defect had been present.
  • Any further corrections to documented endpoint prices or billing behavior after customer reconciliation.
  • 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 because only prices above the $0.01 default create a current cost increase.
  • The disclosure is first-party; no independent billing audit was available in the research window.

Sources

Direct reading behind this dossier.

1 sources
Continue reading
SaaS

Legora is separating AI-agent pricing from conventional SaaS seats

Legora’s Agent Pro pricing illustrates a concrete AI SaaS shift: base platform economics can remain seat-oriented while high-variable-cost agent work is metered separately. The model is notable for its controls as much as its pricing—and for what it does not disclose publicly.