Pricing

Ten thousand free a month, then you pay for what you use.

No tiers, no seats, no minimum, no annual commitment. Reads are $0.08 per thousand requests and writes are $0.14 per thousand events. You can work out next month's bill from this month's traffic.

Billing is not live yetEvery account is on the free tier and nothing is charged. These rates are published so the cost of building on this is knowable in advance rather than a surprise later. When billing does start, an account over its allowance is warned on the responses it is already making, and only then refused — see Usage and billing.

Free

10,000

a month

Reads and events together, counted the same way as below. Enough to build against and decide. No card, and no human step — an agent signs itself up and starts working.

then: a hard stop, not a bill

Reads

$0.08

per 1,000 requests

Reads against a resource: availability, and the list of resources you hold. One request, one read, however much comes back.

Writes

$0.14

per 1,000 events

Each event in a PATCH: one booking, one release, one change of capacity. A call carrying fifty events counts fifty. Creating a resource counts as one.

What gets counted

One read

GET /range/…/inventories, its contiguous form, and GET /resources — one request, one read, whatever the size of the answer.

One write per event

Every event in the list a PATCH carries, plus one for each resource created. Grouping events into fewer calls does not change the total.

Nothing else is counted. The whole account surface is free — signing up, enrolling, reading your own account, issuing and revoking tokens, and checking health. So is any request we refuse: a rejected credential, a rate limit, or a 402 never reaches an invoice. You are billed for using your inventory, not for administering the account that holds it.

Where the invoice goes

An account is a uuid and what it can prove — no email, no password, no name. That is the premise: signup is unattended and a human step would defeat it. So an invoice needs somewhere to go, and billing_email is the one optional field on an account that is not a credential.

Set it at signup or later with POST /account/update. It is never verified, nothing authenticates against it, and two accounts may carry the same one — one operator holding many accounts is normal here.

Losing it does not lose the account, and it does not recover one eitherThe address decides nothing. If you lose the token and the TOTP secret, the account is gone — a billing address on file does not change that, and no support exception will be made, because the service has no way to tell you from anyone else who knows it.

Usage and billing Get a token