Skip to content
Orbacle
Pre-launchThe contracts are written and tested; nothing is deployed yet. The state table says exactly what is real.
LLM oracle · Paid in Orbio CREDIT · Chain 4663

A language model your contract can call, paid in Orbio CREDIT.

Orbacle lets a contract on Robinhood Chain ask a question in plain language and get a typed answer back on chain. The fee is Orbio CREDIT, the token that burns into a dollar of model usage, and the operators who answer are paid in it. Resolve a dispute, grade a deliverable, classify a submission, pick an option: the things a contract could never decide alone.

Orbacle is built on Orbio’s public contracts and gateway and is not affiliated with Orbio. Nothing here has been audited. Each claim on this site says which of those it is.

1 CREDIT on Orbio’s book · live
—
reading the Exchange…
Operators bonded
—
oracle not deployed
Questions asked
—
since deployment
Price read from Orbio’s Exchange on chain 4663 by this browser, every thirty seconds. The plate is computed, not drawn: move the pointer to probe and tilt it.

Capabilities

What Orbacle does

Six properties, and every one of them is a line you can find in the contract.

01

A contract asks in one call

ask() takes a model id, a prompt, the shape of answer you want and a fee. The prompt is emitted, never stored, so the question costs the same whether it is one line or eight kilobytes.

One call · Any model on Orbio · 8 KB prompts
02

Paid in inference, not in a currency

The fee is Orbio CREDIT: the ERC-20 that burns into a dollar of model usage. The operator who answers is paid in the very thing it spent to answer, so the loop closes without a treasury.

CREDIT escrow · 0.01 minimum · Refund on silence
03

Typed answers, so a contract can act

Bool is one byte. Uint is thirty-two. Choice is an index. Text is UTF-8 up to two kilobytes. The contract checks the shape on the way in, so onAnswer never sees a malformed reply.

Bool · Uint · Choice · Text
04

A quorum, and a majority rule

For typed questions you name one, two or three operators. The first digest to reach a majority settles the request. Three answers that all disagree refund you, and nobody is paid.

Quorum 1–3 · Majority wins · Dissent earns nothing
05

Operators are staked, not appointed

Anyone bonding $ORBACLE above the minimum may answer any request. There is no allowlist to get on and no address that can take you off it; unbonding is a day, so a bad actor cannot leave in the same block.

Permissionless · Bonded · One-day unbond
06

Every answer carries a receipt

A reply names the model that actually answered and the hash of the gateway response id. Anyone with an Orbio key can ask the gateway what that call was: the oracle does not ask you to trust the operator.

Model named · Receipt hashed · Checkable

How it works

Four steps, two of them on chain

Ask and Reply are transactions. Infer happens on Orbio’s gateway. Callback is the same transaction as the settling reply.

  1. 01

    Ask

    Your contract calls ask() with a model, a prompt, an answer shape, a quorum and a fee in CREDIT. The fee is escrowed; the prompt goes out in the log.

  2. 02

    Infer

    Operators watching the log run the prompt through the Orbio gateway, each on its own key, each paying for its own tokens. Nothing about this step touches the chain.

  3. 03

    Reply

    Each operator writes its answer back with reply(), typed to the shape you asked for. The contract tallies digests; a majority settles it and pays the winners.

  4. 04

    Callback

    If you named callback gas, the oracle calls your onAnswer() in the same transaction. If you did not, the answer waits in storage for you to read.

On chainOff chainask()escrow CREDIT · emit promptOrbio gatewayoperator pays its own tokensreply() × quorumtally digests · pay winnersonAnswer()your contract, same txeach operator: read log → infer → encode → signmajority settles · split refunds · silence refunds after the deadline
The blue node is the only one Orbacle does not run. Everything on the top lane is one contract with no owner.

Trust model

Who you are trusting, and with what

An oracle is a claim about the world written into a chain. This one is honest about where each part of that claim comes from.

What the contract guarantees

  • Only a bonded operator can reply, and only once per request
  • An answer has the shape you asked for or it is rejected
  • A majority of your quorum settles; a split refunds you
  • The fee reaches the winners minus a cut fixed at deployment
  • Nobody can pause it, upgrade it, or take your fee
  • A silent request refunds in full after the deadline

What it cannot guarantee

  • That the model was right. A quorum makes a wrong answer rarer, not impossible
  • That an operator ran your prompt unchanged. The receipt lets you check, after
  • That three operators are independent. Stake makes collusion cost something, not nothing
  • That Orbio’s gateway is up. Operators depend on it; the refund path does not
  • That a Text answer is settled by agreement. It is one operator’s reply, by design

The honest summary: Orbacle moves the question of “do I trust this model’s answer” from a private API key to a public, staked, receipted reply that a contract can act on. That is a smaller claim than “decentralised truth”, and it is the one the code supports.


Why CREDIT

The fee is the fuel

Orbio turned inference into an ERC-20. That is the one thing that lets an oracle pay its operators in what they actually spend.

One CREDIT is one dollar of model usage through Orbio’s gateway. It trades on an order book below par, because the people who earned it by staking do not all need to spend it. Activating it burns the token into API balance, one way.

An Orbacle operator is paid in CREDIT, holds CREDIT, and activates CREDIT to run the next question. Its wallet signature is its Orbio API key, so there is no account to open and no card on file. The node refuels itself from its own earnings. An oracle priced in a currency needs a treasury to buy compute; an oracle priced in compute does not.

It also means the price of an answer is public. The plate above shows what a dollar of inference costs on the book right now, read from the Exchange contract by your own browser. An asker can see what it is paying for; an operator can see whether a fee clears its cost before it spends a token.

CREDIT, the Exchange, the gateway and the models behind it are Orbio’s. Orbacle uses them as any agent would, through the public ABI and the public API. If Orbio changes its terms, every operator here feels it, and this page will say so.

CREDIT token
0xe33322da1380e61e5ae5dfb21e7f62924c73004c
Exchange (order book)
0x6951ffd32630b05e06f50062aea801625a58ebc0
Gateway
https://api.orbio.so/api/v1
Decimals
6 · 1,000,000 = $1.00 of inference
Activation
credit.activate(amount) burns into API balance
API key
the operator wallet’s signature, per Orbio’s agent guide
Orbio’s agent guide

What to ask it

Questions a contract could never answer alone

Every one of these is a typed request with a quorum, not a chat.

Bool · quorum 3

  • Did this deliverable meet the spec?
  • Is this listing a scam?
  • Does this text violate the rules?

Uint · quorum 3

  • How many units does this invoice bill?
  • What score, 0–100, does this essay earn?
  • Which block did this event describe?

Choice · quorum 2

  • Which of these four bids best fits the brief?
  • Which category does this item belong to?
  • Which party does the evidence favour?

Ask it something. Or be the one who answers.

Askers need CREDIT and a question. Operators need $ORBACLE to bond and a wallet that signs once for an Orbio key. Both start from the same page.