Wallet

A wallet with a ceiling.

The agent has a wallet of its own, separate from yours. It is how Onyra pays for the APIs and the compute a task actually uses. You fund it on purpose. You decide how far it can go.

Not live There is no wallet to fund, and no transaction to show. The receipt below is an example of the record the wallet is designed to leave.

01

Separate on purpose

The agent wallet is not your personal wallet with a new label. You move funds into it when you mean to. What the agent can spend is what you put there, and no further than the ceiling.

02

Per use, not a retainer

APIs and compute are billed for the calls a task made. The agent is designed to pay those costs from its wallet as they happen, rather than hiding them inside a flat story about “unlimited” work.

03

A ceiling, and a rule

You set the most the wallet may spend. Under that line, auto mode may settle a cost the task already incurred. Over that line, it waits for you. The safety judge can also refuse a plan that spends outside the rules you wrote down.

04 — Receipts

A payment you can match.

When the wallet is live, a payment is meant to leave an on-chain receipt you can tie back to a task: what it was for, and the amount. Until then there is no hash to copy and no explorer link to trust.

If someone sends you a contract address or a transaction and calls it Onyra, check this site. The address is published in one file, js/config.js, and today that file is empty.

Example receipt — not a transaction
Task
Host the night log
Paid for
Model calls used by that task
Rule
Inside the ceiling you set
On-chain
A transaction id appears here when the wallet is live

05 — What it will not do

The ceiling is the product.

  • No blank check

    Auto mode is not permission to spend without a limit. The limit is yours, and crossing it is a stop, not a surprise.

  • No quiet mixing

    The agent does not spend from a wallet you use for other things. Its funds are the ones you moved, for this purpose.

  • No hidden call

    A payment is meant to be matchable to a task. A charge you cannot connect to work is a failure of the design, not a feature of it.

The token is not the wallet.

$ONYRA is planned as one way to buy cloud credits, and as a stake and a vote later. The wallet is how a task pays for what it used. They meet. They are not the same object, and neither one is live.