Skip to main content

Pricing

ReserveBeat's coverage board is free and never paywalled. The API is priced in compute units, with no tiers and no seats: every account gets 20,000 a month free, a history request costs 10, 20 or 50 by its shape, and past the allowance it is pay as you go at $0.05 per 1,000 compute units, prepaid. Enterprise is custom.

01Plans

Three plans, one meter

The coverage board is never paywalled. Every tracked token renders its current published figures for everyone at their stated scope, with source tier and freshness beside them. Compute units price depth, volume, and reuse terms — never visibility of a current figure.

  1. People and machines

    Free

    $0

    For anyone checking what a stablecoin issuer has published — analysts, treasury teams, journalists, and developers alike.

    The full coverage board with every tracked token at its current figures, a thirty-day history window on charts and keyless API responses, CSV export of what is shown, an email when a new attestation lands, and a self-serve key across all ten read endpoints — history at any depth included, paid for from the free allowance.

    20,000 compute units a month free, at a steady 20 compute units a second with up to 200 in any rolling 10 seconds. Those are the limits the service enforces today, not a marketing figure.

  2. For machines

    Pay as you go

    $0.05 per 1,000 compute units

    For the team that reads ReserveBeat from a service rather than a browser.

    Everything in Free, and: compute units past the free allowance, drawn from a prepaid balance at one published rate — no base fee and no tier. One endpoint is metered today, history, at 10 compute units for every token at once, 20 for one token inside the public thirty-day window and 50 for one token reaching past it; the current-state endpoints stay keyless and cost nothing. While a balance is held the account is served at 100 compute units a second and reads each token's restatement record — every superseded parse and score beside the one that replaced it. The read endpoints stay pull-only, and a balance also adds signed webhooks: an HTTPS endpoint you register is POSTed when an attestation report lands and when an issuer's own stated figure moves, with a per-endpoint secret shown once and any delivery replayable on request.

    Questions about buying compute units, or about an Enterprise arrangement, go to contact@reservebeat.com. Self-serve purchase is not open yet; the waitlist link opens a message to the same address asking to be told when it is.

  3. For data

    Enterprise

    Custom

    For the desk that wants the parsed attestation record itself rather than the views built on top of it.

    Everything in Pay as you go, and: the parsed attestation dataset behind these pages rather than the served views, throughput and refresh cadence arranged on the account, and redistribution terms beyond the board data licence. Priced per arrangement; no figure is published here.

Free is live and self-serve today: create an account, issue a key, and the limits below are the ones the service actually enforces. Past the free allowance, compute units are bought as a prepaid balance rather than a subscription, and a request that finds both spent is refused with the rate, the balance it read and a link to buy more — so a purchase can start from the API as well as from this page.

Checkout opens after launch. Until then, write to contact@reservebeat.com or ask about Enterprise. The free allowance needs no billing: create an account from the dashboard and issue a key.

02Compare

How Free, Pay as you go and Enterprise compare

How Free, Pay as you go and Enterprise compare
CapabilityFreePay as you goEnterprise
Coverage boardEvery tracked tokenEvery tracked tokenEvery tracked token
History depth30 days on the site; any depth through a key, meteredThe same window on the site; any depth through a key, meteredThe same window on the site; any depth through a key, metered
CSV exportWhat is on screenWhat is on screenWhat is on screen
Email when a new attestation landsIncludedIncludedIncluded
Read API compute units20,000 compute units a month free; 20 compute units a second, up to 200 in any 10 seconds$0.05 per 1,000 compute units past the free allowance, from a prepaid balance; 100 compute units a second while a balance is heldAgreed per account; the free allowance and throughput apply until a higher figure is set on the account
Parsed attestation datasetNot includedNot includedLicensed per arrangement

The board rows read the same for every account on purpose. What an account buys is depth, compute, and reuse terms — never which tokens or which current figures are visible.

The compute-unit figures on this page are derived from measurement rather than set by hand: each weight is the measured serving cost of the request shape it prices, rounded to a one-two-five step, the throughput sits below the measured capacity of the service, and the monthly allowance is the same number of median history requests the free key allowed before compute units.

03Estimate

Estimate a month of use

Enter the compute units you expect to use in a month. The estimate applies only the free allowance and the rate stated on this page.

Estimated cost for the month

$2.00
  • 60,000 compute units in the month
  • 20,000 paid for by the free allowance of 20,000 a month
  • 40,000 past the allowance
  • 40,000 compute units at $0.05 per 1,000 is $2.00

An estimate, not a quote. Compute units are bought ahead as a prepaid balance, at least 40,000 at a time ($2.00), and lapse twelve months after purchase.

04Questions

Common questions

Is the coverage board ever paywalled?

No. Every tracked token renders its current published figures for everyone at their stated scope, with source tier and freshness beside them. Compute units price history depth, volume, and reuse terms — never visibility of a current figure.

What exactly does a free API key allow?

20,000 compute units a month, at a steady 20 compute units a second with up to 200 in any rolling 10 seconds. Only responses the service actually served cost compute units, and a not-modified response costs none. Every served response from the keyed tier carries its allowance and rate-limit state in standard headers; the keyless endpoints carry none, because no ceiling applies to them.

How do I buy compute units?

Compute units past the free allowance are bought as a prepaid balance, from the checkout on this page once billing is enabled; a request refused for an empty balance carries a link to it. There is no plan to choose and no subscription. The free allowance needs no billing at all — create an account from the dashboard and issue a key.

Does buying compute units change what data exists?

No. Compute units change how much of the record you can reach and on what terms. The underlying evidence, and the figures read from it, are the same for everyone at the same stated scope.