Pricing

Pay per call.

No monthly minimum. Top-ups start at $0.50. The top-up fee is shown before you pay. You pay the price shown. If a call turns out to cost more than its quote, you pay the actual price, capped at twice the quote. A call never takes your balance below zero.

What a call costs, from the catalog today

ABS Statistical Time Series (Australian Bureau of Statistics SDMX Data)Price$0.0026 per call
American Community Survey Variable Finder (by Topic Keyword)Price$0.001 per call
Address to Coordinates (Single Best Match with Bounding Box)Price$0.0325 per call

You pay the price shown. If a call turns out to cost more than its quote, you pay the actual price, capped at twice the quote. Run omnial_execute with dry_run: true for an exact quote.

Install it on your AI See every price

What you pay for, and what is free.

Charged

A successful omnial_execute, priced by that tool. Nothing else: no plan, no seat, no monthly minimum.

For the exact amount of one specific call, run omnial_execute with dry_run: true. That amount is what gets held while the call runs. No tool is contacted to produce it.

Free, always

omnial_search: finding a tool
omnial_inspect: the contract and an estimate
omnial_learn: the whole usage doc
omnial_balance, omnial_runs: your own state
dry_run: true: pricing a call without making it

How a charge works.

You top up a balance
A card payment through Stripe adds to your balance. Top-ups start at $0.50. The top-up fee is shown before you pay. Auto top-up can refill it when it drops below a threshold you set.
Details
The refill must be bigger than the threshold, so one top-up can't trigger another. Auto top-up also waits out a cooldown after each successful charge and stops at a daily limit.
The quote is held while the call runs
Before the call starts, its quote moves from available to held. A held amount is a quote, not a cap on the charge.
Details
If the hold would exceed your available balance or a spend cap, the run is refused before anything is called, and nothing is charged.
You pay the call's final price
When the run finishes, you pay its final price. If that is at or under the quote, the rest of the hold comes straight back to your available balance.
Details
The final price is taken from the most reliable source that tool has, never blindly from the estimate. The charge and the release are written in one transaction.
A call that costs more than its quote
The difference is charged too, never beyond the hold, which is at most 2x the quote. It never takes your balance below zero.
Details
A call can cost more than its quote when the estimate was wrong about a quantity, or the tool used more than it was asked for. The hold is what makes the charge safe to take: a run only starts when your balance covers it.
Past the hold we absorb the difference and pull the tool from the catalog, because a call that costs a multiple of its quote is our defect, not your usage.
A failed run is not charged at all
A run that did not come back releases its hold in full.

The whole charge model

Before a call runs, we hold an amount from your balance: the quote, or up to 2x the quote on a tool whose final price is only known when the call ends. If your available balance does not cover the hold, the call is refused and the error names the amount you need. After the call, you pay its final price, never more than the hold, and the rest of the hold is released straight back to your available balance. A call can never take your balance below zero. If a final price passes the hold, we absorb the difference and pull the tool from the catalog, because a final price that is a multiple of its quote is our defect, not your usage. A run that fails is not charged at all.

Limits your AI cannot talk its way past.

Spending limits are enforced by the system that holds the money, not by the prompt.

Per-key spend caps

Each API key can carry its own cap. A capped key cannot create keys and can only lower its own cap, so a limited key cannot issue itself an unlimited one.

Scopes

A key without runs:execute can search, inspect and read usage docs, and is refused by omnial_execute. You see that when you choose the scopes.

The balance itself

A run whose quote exceeds the available balance is refused before the call starts, with the shortfall named so your AI can act on it. A call can never take your balance below zero.

Every charge links to the ledger entries behind it.

Append-only ledger: Entries are never edited or deleted, and each one records the balance after it, so any balance can be rebuilt from its own history.
Per-run breakdown: Each run shows its quote, the amount held and the amount charged, next to the ledger entries that moved the money.
Refunds: A refund writes a ledger reversal, shown next to the invoice it reverses. An invoice reads as refunded only when it was reversed in full.
Usage by day: A run counts on the day it settled, not the day it was submitted, so a render that finishes after midnight does not change a day you already read.

Install it on your AI Create an account