Terms of service

Who these terms are with

ReserveBeat is published by ReserveBeat LLC. In this document “we” and “us” mean ReserveBeat LLC, and “you” means anyone who uses the website, the figures it publishes, or the read API.

Using the site or the API means accepting these terms as they stand on the day you use them. If you do not accept them, do not use the site or the API.

The service is provided as it stands

The site, the figures it publishes and the API are provided as they stand and as they are available, without warranty of any kind, express or implied, including any implied warranty of merchantability, fitness for a particular purpose, or non-infringement. We do not warrant that the site will be uninterrupted, that any figure will be current, or that a third-party document linked from it will still be published.

No reliance

ReserveBeat prepares and republishes evidence about other companies’ disclosures. It is not an audit, an attestation, or an examination, and it is not a substitute for an issuer’s own reports or for professional advice. Do not rely on a figure here for a decision that matters without reading the source document that figure cites.

Not advice

ReserveBeat renders figures from issuer-published reports and public blockchains, verbatim and at their stated scope. It is not an auditor, makes no attestation, and states no opinion on any issuer's solvency. Nothing here is investment, trading, legal, tax, or accounting advice. No figure published here is a recommendation to hold, buy, sell, or redeem any token.

Limits of liability

To the fullest extent the law allows, we are not liable for indirect, incidental, special, consequential or exemplary loss, nor for lost profits, lost revenue or lost data, arising from use of the site or the API. Our total liability for all claims arising out of these terms is limited to the greater of the fees you paid us in the twelve months before the claim and one hundred United States dollars.

Acceptable use of the API

An API key is issued to one account. Do not share it, resell it, or use it to run a service whose product is raw ReserveBeat API responses. One account per organisation is expected; a key found in someone else’s hands is treated as misuse of the account it was issued to.

Do not work around the monthly free compute-unit allowance, the compute units a second an account may spend, or any other published limit — including by spreading usage across more than one account — and do not retrieve pages faster than the published limits allow or use the API in a way that degrades it for other readers. The published limits are the limits, not a suggestion. If one person or organisation uses more than one account to get around them, we may count the combined usage of all of those accounts against the allowance and the balance of any one of them. We first send a notice to the address on the account naming the term; if the usage does not stop, we may block the accounts’ keys until it does; and if it has not stopped ten days after the notice, or it happens again within twelve months of a first notice, we may close the accounts.

We may suspend or revoke a key, or close an account, when it is used against these terms. Where the circumstances allow it, we will say which term and give notice first.

Reuse of published data

Board figures carry their own reuse terms — Creative Commons Attribution 4.0 International — set out in full on the data license page, which also states what those terms do not cover. Data the API serves without a key, or against a key’s monthly free allowance, carries that same license; data paid for from a prepaid compute-unit balance is governed by the purchase terms below instead and may not be redistributed under CC BY 4.0. Data license and reuse

Purchase terms

A purchase buys prepaid compute units for the account that makes it, at the rate and in the units the pricing page publishes on the day of the purchase; the price, including any tax Stripe adds for your billing address, is the one shown on the checkout page before you pay. There is no base fee, no subscription and no automatic renewal: a purchase is a one-time charge, and nothing is charged again unless you buy again. The compute units a purchase buys are a fixed number recorded at checkout, are added to the account’s balance once the payment is confirmed, are spent only on metered requests past the monthly free allowance, and lapse twelve months after the purchase if they are still unspent.

Payment is taken by Stripe, which processes the card, holds the card details and issues the receipt; we never see or store a card number, and the terms Stripe sets for its checkout page apply alongside these. A purchase can be made only from a signed-in account whose email address has been confirmed, and the balance it buys belongs to that account: it is not transferable to another account, cannot be paid out as cash, and may not be resold.

A purchase whose compute units are entirely unspent can be refunded in full for twenty-four hours after it is made, by writing to contact@reservebeat.com from the address on the account. After that, or once any of its compute units have been spent, a purchase is not refundable except where the law that applies to you requires it. A refund of part of a purchase takes back compute units in proportion to the money returned, and lapsed compute units are not refunded. While a card dispute over a purchase is open, the whole balance on the account is held at zero; when the dispute closes, the balance returns, less the disputed purchase’s compute units if the card holder wins the dispute.

Rows paid for, in whole or in part, from a prepaid balance are licensed to the account for its own use, including inside the products and services it offers, but not for redistribution of the rows themselves: do not republish, resell or systematically redistribute them, and do not pass them on under CC BY 4.0, which they do not carry. The split is decided request by request and stated on each response, and rows the monthly free allowance paid for keep the board-data licence set out on the data license page. Corrections cost nothing: the revisions route is served free of compute units, so a correction to a figure never costs a second time to read.

Governing law

These terms are governed by the laws of the State of North Carolina, in the United States, without regard to its conflict-of-laws rules. Any dispute arising out of them belongs in the state or federal courts sitting in North Carolina.

How these terms change

These terms change by supersession, the same way a published figure is corrected here: a new dated version replaces the previous one, and the previous one stays listed in the revision log below rather than being deleted. A material change — to what the API costs, to what it serves, or to what you may do with what it serves — is announced on the changelog and to the address on every account at least 30 days before it takes effect; withdrawing a paid offering that a paying customer is using is announced at least 90 days before. An account that accepted an earlier version must accept the current one before it can create a new key or webhook endpoint; the keys it already holds keep working in the meantime.

Revision log

Version 4, drafted 14 October 2026, replaces version 3. It adds the purchase terms — what a prepaid compute-unit purchase buys, that Stripe takes the payment, when a purchase is refundable and how a card dispute is handled, and what may be done with rows a balance paid for — and points the reuse section at them; nothing else changed. Version 3, drafted 30 September 2026, replaces version 2. It names ReserveBeat LLC as the publisher and the party to these terms, gives contact@reservebeat.com as the address for questions about them, and says that the same inbox takes reports of a wrong figure, which still follow the corrections route; nothing else changed. Version 2, drafted 25 September 2026, replaces version 1. It restates the API limits in compute units, adds the rule against spreading usage across accounts and what we do about it, adds the notice periods above, and decides the reuse terms of API data per request: rows the free allowance pays for stay under CC BY 4.0, rows a prepaid balance pays for fall under the terms set out at purchase. Version 1, drafted 6 September 2026, was the first version.

Questions about these terms

Questions about these terms go to contact@reservebeat.com. The same inbox takes reports that a published figure is wrong, but those follow the corrections route set out on the contact page, which is a different process with a different promise.

The corrections path, and what happens after a report arrives, are set out in full on the contact page. Contact