Ora

Documentation

How Ora works

Ora is a procurement agent for Orbio CREDIT. It watches the live CREDIT market and helps determine when to acquire inference at a better available price.

In short: Ora makes CREDIT procurement more deliberate by combining live market conditions, your procurement rules, and executable purchase checks.

What is Ora?

Ora is an agent for procurement of Orbio CREDIT.

Ora operates through a procurement desk. CREDIT is treated as a tradable unit of inference capacity on Orbio. Ora does not invent market data; it reads the live Orbio order book.

The product surface is a Market desk for the live decision, a Purchase review before any transaction, History for recorded decisions, and Performance for confirmed outcomes.

How Ora decides BUY or WAIT

  1. Live Orbio book
  2. Minimum discount
  3. Can requested CREDIT be fulfilled?
  4. BUY / WAIT

You set three procurement parameters: CREDIT to procure, a USDG spending limit, and a minimum discount. The requested purchase size is the CREDIT to procure amount, floored to the live book minimum purchase size when that book minimum is higher.

Ora then inspects the live depth. A level qualifies when its discount is at least your minimum discount. BUY is offered only if a qualifying level has enough CREDIT to fulfill the requested amount. Otherwise Ora waits.

If the best qualifying level cannot fill the request, Ora does not treat that as BUY. Review purchase appears only when the current decision is BUY.

Market data and order-book depth

Market snapshots come from Orbio’s CREDIT book. Ora normalizes each depth level to a discount percent and available CREDIT, ordered from the deepest discount downward. The desk shows CREDIT price, best available discount, total available CREDIT, and CREDIT available at the best discount.

The book also reports a minimum CREDIT purchase size. Ora keeps that constraint: requested size cannot go below it. Depth on the desk highlights the level that matches your current minimum discount when that level exists on the book. Listed book discount is not automatically the fill price of a later quote.

Purchase review and executable quotes

Review purchase fetches a fresh executable quote for the requested CREDIT amount. The review keeps market decision and execution quote separate: the book may show one discount, while the quote states the price and discount at which CREDIT would actually be bought.

If the quoted discount is below your minimum, or the quoted USDG cost exceeds the spending limit, or the quote cannot fill, Ora does not offer a purchase. Confirm stays subject to those checks.

Execution and wallet confirmation

  1. Market decision
  2. Fresh quote
  3. Validate
  4. User confirms
  5. Buy + activate

A purchase is sent only after you confirm. The connected wallet must be on Robinhood Chain 4663. Payment is USDG: Ora checks allowance, requests approval if needed, then calls buyAndActivate on the exchange.

Confirm purchase stays disabled when a wallet is disconnected, the network is wrong, the quote fails the minimum discount, USDG is insufficient, ETH for gas is insufficient, or a transaction is already pending. A BUY decision is not a completed purchase until the transaction confirms onchain.

Decision history

Each recorded decision is stored in a local ledger with time, BUY or WAIT, discount at decision, requested amount, and status. Status is Decision, Review, Pending, Confirmed, or Failed. History and Recent decisions use that ledger. Selecting a row shows the stored reason and any quote, block, or transaction details.

Performance and outcome evaluation

Performance counts BUY and WAIT decisions, but only confirmed onchain purchases enter procurement totals. Reviewed, pending, rejected, or failed BUY rows are unresolved; they are not treated as savings or as successful fills.

When a confirmed fill exists and a later market snapshot is available, Ora can compare USDG paid against buying the same CREDIT size later at the later book’s listed CREDIT price. That comparison is a log, not proof of a winning strategy. WAIT outcomes describe how the later listed discount moved; they do not claim that waiting is a strategy.

Limitations and assumptions

CREDIT markets can be thin. A qualifying discount with too little CREDIT at that level produces WAIT. A BUY reflects the current book and your procurement rules. It does not guarantee a better fill than waiting.

The executable quote can differ from the book. Outcomes versus a later buy-on-demand price stay unresolved until a later market snapshot exists. Ora presents early results as a log, not a strategy score, and does not count unconfirmed BUY decisions as purchases.

Open Ora