Pick a volume. Ship the lookup.

Limits are per account, not per key. A second key splits the same allowance.

What counts as a request?

One lookup is one request. Counted when the key is authorised, before the resolve runs — a miss counts the same as a hit. A settled record replayed from storage still counts.

What happens past the monthly ceiling?

With overage enabled, extra lookups are served and billed at the rate on the plan. Without it, the next request is refused with 429 and costs nothing. Nothing is queued either way, and usage is summed across every key on the account — adding keys does not add allowance.

When are the extra lookups charged?

They are metered as they happen and invoiced in arrears: at the start of each month you get one invoice for the previous month, charged automatically to the card on file. A month with no overage produces no charge. The plan fee itself is separate and bills on its own cycle, monthly or yearly.

How do I pay, and can I cancel myself?

Card payment through Stripe — the card never touches our servers. Cancel, switch plans or replace the card yourself from the billing portal in the dashboard. Cancelling stops the next renewal and closes the credit window; the final month of overage is still invoiced.

Is there a free tier?

No. A plan is required: an account without an active subscription is refused with 402. You can sign up, mint keys and run a handful of evaluation lookups from the dashboard first, so you see a real response before paying.

Do I need to register a company?

No. Nothing gates on it. A company profile only exists so invoices and contracts can carry a legal entity instead of an email address — add it if you need that, skip it if you do not.

How do I know how much is left?

Every metered response carries X-Credits-Used, X-Credits-Remaining and X-Credits-Period-End, so you can back off before hitting the ceiling. GET /api/v1/account returns the same figures and is deliberately unmetered.

How do keys work?

Keys are prefixed flt_ and stored as a SHA-256 hash. The raw secret is shown once, at creation. Send it as Authorization: Bearer or as x-api-key.

Which timezone?

UTC everywhere — flight dates, block times, the three-day settle window, and the timestamps on the usage log.