Notes · 01 · 5 min
Paid in the thing you spend
Why the fee is CREDIT and not a currency, what that closes, and what it exposes.
Every oracle has to answer the same awkward question: who pays the people who answer, and in what? Most settle it with a token of their own. The token pays operators, the token is staked, the token is the thing the whole design has to keep valuable, and the oracle quietly becomes a project about its token. Orbacle has a token too, for stake, but the fee — the thing an operator is actually paid for an answer — is not it.
The fee is Orbio CREDIT. One CREDIT is one dollar of model usage through Orbio’s gateway, and the only thing you can do with it besides hold or sell it is burn it into API balance. An operator that wins a request is paid in CREDIT, holds CREDIT, and activates CREDIT to run the next question. It is paid in the thing it spends.
What that closes
Three things, none of which an oracle priced in a currency can close on its own.
| Priced in a currency | Priced in CREDIT | |
|---|---|---|
| Buying compute | Someone has to sell the fee for API credit, on an exchange, with a card | The fee is API credit. activate() and go |
| Pricing an answer | Needs a price feed for the fee token and one for the model | A 0.05 fee is five cents of inference; the model’s price is in the same unit |
| Keeping it running | A treasury that tops up operators, and someone to run it | None. The last fee pays for the next answer |
The node that ships with the oracle is the whole argument in one file: it watches its API balance, and when the balance drops under a floor it calls credit.activate on whatever CREDIT it has earned. No account was opened, no card was entered, and the key it signs requests with is its own wallet’s signature over a fixed message. That is Orbio’s design, and the oracle just stands on it.
// the loop, in three lines of the node
if (apiBalanceUsd < REFUEL_BELOW && creditHeld > 0n) {
await credit.activate(min(creditHeld, REFUEL_AMOUNT));
}What it exposes
An honest version of this note has to say what the choice costs, and it costs three things.
The gateway is a dependency. If Orbio is down, no operator can answer. The contract does not care — fees refund after the deadline — but askers lose time. An oracle that promised uptime could not make this choice; one that promises refunds can.
The price of an answer floats with CREDIT. Today a CREDIT trades around seventy cents on Orbio’s book, so a 0.05 fee costs an asker about three and a half cents and buys an operator five cents of inference. If CREDIT went to par the asker pays more; if it went to fifty cents operators are paid less in dollars but exactly the same in compute. The unit that stays fixed is the one that matters to the person doing the work.
It is Orbio’s token, not ours. Activation fees, the gateway’s model list, the terms of the book — all of it can change under the oracle without the oracle’s consent. The site reads the book live and prints the fees for that reason: if the ground moves, the page shows it moving.
The alternative was a token that pays operators, which would have meant the oracle’s health depended on a market it created. This way it depends on a market it merely uses. That is a smaller claim and a more defensible one.
NextWhy a text answer has no quorum