You pay for what you ingest and what you ask.

Yes, and it is meant for evaluating the API against your own data rather than for running a product on. It carries the full engine: all four endpoints, entity resolution, temporal history and answers with evidence. What it limits is volume.

By talking to us, on every tier including the free one. Tokens are issued by hand during early access: there is no dashboard, no programmatic issuance and no rotation endpoint yet. Self serve signup is dated on the roadmap, and the free tier becomes a real signup the day it lands.

An ingest request is one call to POST /ingest carrying one data point: an email, a transcript, a ticket, a note. A question is one call to /recall or /answer. Ingestion is idempotent by content hash, so re-sending unchanged content does not count again.

No. The people using your software never touch Revo, which is why every tier says unlimited end users and why we count what the API does rather than how many people touch it.

Not materially. We read a roughly fixed amount per question whether the record holds a hundred thousand tokens or ten million, which is where the 23x figure against sending 1M tokens of history comes from. Ingesting more does cost more; asking about more does not.

Every response carries its own cost under usage, so you can price a feature or cap a customer without instrumenting anything yourself.

Because the per unit rates are not agreed yet, and we would rather show you nothing than a number we intend to change. What is settled is the shape: you prepay credits, three meters draw them down, and there are no ceilings. Tell us your volumes and we will model the actual spend with you on the call.

You buy a balance up front and every call draws it down at the published rate for that meter. Set a threshold and a top up amount, and the balance refills itself when it gets low, so a spike in traffic does not fail your calls. Every response already carries its own cost under usage, so you can see the draw down per feature rather than waiting for a statement.

With auto top up on, they should not: the balance refills at the threshold you set. If you have turned it off, or a card fails, calls start returning a clear billing error rather than silently degrading, and the data already in your project is untouched. Nothing is deleted for a lapsed balance.

The engine is identical and both are unlimited. Pay as you go is prepaid credits on a card, which suits a team that wants to start this week. Enterprise trades an annual commitment for volume rates and moves you onto an invoice, and adds the things procurement asks for: dedicated or in region deployment, an SLA, a DPA with retention and legal hold, audit logging and SSO.