Infrastructure
Nothing metered is ever unlimited
Usage limits usually fail in one of two ways: they are checked and then acted on, so two simultaneous requests both pass; or they are exceeded quietly and appear on a bill. Both are closed here, and the first one is closed atomically rather than carefully.
14-day evaluation · no card · start before you connect anything
How it works
- 1
Reserved in one write
A limit is claimed with a single conditional update that either matches or does not. Two requests racing produce one success and one refusal, which no amount of checking-then-acting can guarantee.
- 2
Held while the work runs, settled at the end
Credits are held when work starts so a long job cannot take you past your allowance half way through, then settled at what it actually cost — returning the difference when the real cost was lower.
- 3
Four answers at a limit
Allow, deny, ask a person, or upgrade. There is no fifth answer that quietly proceeds and bills you, because an overage nobody agreed to is the one outcome this design exists to prevent.
- 4
Everything expensive is measured in one currency
Writing, plans, agent work and video all consume Xyranik credits, so a single allowance covers them and there is no second, parallel accounting to reconcile.
One request against an allowance
- 1
Reserved in one write
A single conditional update that either matches or does not. Two requests racing produce one success and one refusal.
- 2
Held while the work runs
So a long job cannot take you past the allowance half way through.
- 3
Settled at what it cost
The difference comes back when the real cost was lower than the estimate.
Four answers at a limit. There is no fifth that quietly proceeds and bills you.
What you can build with it
You can see where the credits went
The month breaks down by what asked for them, with what is left and roughly what that could still produce — rather than a single number with no explanation.
Buy more deliberately, and it does not expire
Extra allowance is bought as a pack, used only once the monthly allowance is spent, and what is left of it does not disappear at the end of the month.
Held credits are explained, not hidden
Because credits are held while work runs, the figure counted against your allowance can lead what has been recorded as spent. The difference is shown and explained rather than quietly reconciled.
Limits, and what is not served
Listed here rather than discovered against a rate limiter at three in the morning.
Overage is never charged automatically
At a limit, work stops until the allowance renews, you buy a pack, or you change plan. Nothing beyond your plan is billed without you choosing it — which does mean work can stop.
A limit is per workspace, not per person
Allowances belong to the workspace. There is no per-member budget, so a team shares one pool.
Build an agent that can act without a blank cheque
Your agents ask the same gateway ours do, on a credential of their own, and are held to the same permissions, limits and record. The endpoint list is served by the API itself rather than written out here.