Download

One agent. Every door to it.

One identity, one wallet, one record, reached four ways. Two are open now; two are being built. Every chip on this page is the surface's real state, and nothing links to a file that is not there.

Weblive

Nothing to install. Your key stays in this browser.

Chat, the live desk and the ledger. No account needed to start: the keypair is generated in the browser and never leaves it. Sign up later and keep what you made.

  • Chat on four lanes: Facts (free, abstains), Normal (sovereign, on-box), Pro (web-grounded, signed), CLI
  • Desk: watch the agent's own browser, take over any time
  • Rules and approvals: every send or spend shows a needs-you card
  • Agents ladder, Earn, Verifier — same identity everywhere
Iron-Spireverify · 1.4ssigned
Rhinogent
its own browserlive
portal.supplier.example/invoices/ORD-4471

Pay invoice ORD-4471

Amount€18.40
ReferenceORD-4471
Payeeshop.example✓ verified · GOLD
Card 
Pay €18.40⟵ stopped here · over your cap

filled 2 of 3 · 1.05s · no password typed

  • verifysupplier.example#a6cb5f1.4s
  • extractinvoice ORD-4471#8357980.6s
  • draftpayment, €18.40#d532c70.3s
  • payshop.example—held
A scripted session, not a live feed — but every element on it is something the product does. The cap, the held payment and the signature are the product.
Terminalon npm

An identity in one command.

No account, no browser. The key is generated on your machine and printed once — we never receive it. Piped output stays pure JSON, so it composes with the rest of your shell.

  • init — creates the identity locally; the private half is shown once
  • verify <target> — a cross-verified counterparty check with its grounds
  • connect — reads the network without signing anything
  • MIT, 8.2 kB unpacked, one dependency
rhinogent
$ rhinogent init

✓ Identity created · on this machine

  callsign  Stone-Horn-9508
  did       did:pkh:eip155:8453:0x9011…
  card      ./agent-card.json

! Private key — shown once. We never receive it.
Phonepaused

The whole desk, in your pocket.

Five tabs, same identity, same record. Desk is the agent's live cloud browser; Chat is where it comes back to ask; Agents is your roster; Network is the ladder; Earn is what has been recorded and not yet paid.

  • Durable jobs that survive restarts — a reconcile across three days, a 02:00 nightly shift
  • Standing instructions in plain words, per project
  • Approvals: nothing sends until you sign
  • A floating companion over any other app, with a live timeline of signed moves
The whole desk, in your pocket.
Desktopin development

An IDE your agent works inside.

One native window, two modes today and a companion over the top. IDE puts an explorer, an editor column and a Problems / Output / Terminal / Ports panel around an agent docked down the right, with 0n1x MCP loaded as an extension.

  • Ask it something and it answers in the same window you are coding in
  • 0n1x MCP shows as a connected extension — verify-before-pay and the census from inside the editor
  • The companion drops a signed pill for every move and every Claude Code session
  • File tree and Monaco editor are not wired yet — the app says so in its own explorer
An IDE your agent works inside.

What every surface shares

Same agent. Same memory. Same record.

The four doors above are doors, not four products. What follows you through them is one key, one balance, one set of notes and one chain of receipts — and where a piece of that is still only built on one side, the tile says so.

Identity

One did:pkh on Base, created where you are — in the browser, in the terminal, on the phone. The same identifier is what the dashboard shows, what /developers documents and what the published card carries.

Wallet

caps built, not yet wired

Self-custody: the spending key is the one you made, so nothing here can move the balance. Per-payment and per-day caps are written and null-tested in the gate chain, ahead of the payment rail they will sit on.

Memory

Notes live on your device and come off line by line — every one on your profile carries an × that deletes it. Syncing them across devices goes through an account, which means a row on our side; without one, nothing leaves the browser.

Ledger

phone mirror not built

Every move is signed and chained, and the web and desktop read that same feed, so a receipt you see in one is the receipt in the other. The phone shows its own moves and does not mirror the feed yet.

Integrity and authenticity, by hand.

Check the file you downloaded against the published sums, then check that the feeds you are about to trust are signed by the key we publish — not by one the checker carries.

Integrity

verify-feed.mjs: OK
.well-known/jwks.json: OK

Generated at build time from the files actually shipped, so it cannot lag what you downloaded. macOS: shasum -a 256. Windows: Get-FileHash.

Authenticity

null test    pass
signature    VERIFIED
kid          qH_Kx6…U_Q

Node, no dependencies. Read the null-test line first: if it does not say pass, the run exits 3 and the verdict above it means nothing.

What runs where.

Webany modern browsercontinuous—WebCrypto (Ed25519) for the verifierlive
CLImacOS · Linux · Windows0.1.08.2 kBNode 18 or neweron npm
AndroidAndroid 10+ · arm640.4.0 · 2026-09-10361 MBAndroid 10 or newerpaused
DesktopWindows · macOSunreleased—Windows 10+ · macOS 12+in development

No iOS build exists. Nothing on this page links to a file that is not there — which is why two rows offer a conversation instead of a button. When the Android licence is cleared and the desktop installer is signed, they become files here, and not before.

If you came to check us rather than install something.

Fetchable with no account and no key, and readable by another agent.

Assets 7fetchable with no account, no key, no sign-up
/verify-feed.mjssha256:990cf1c63670…7.9 kBlive

The verifier. Node 18+, no dependencies, ~150 lines — fetches the key rather than embedding one, and exits 3 if it cannot prove it is able to fail

/SHA256SUMS—579 Blive

Checksums for the artifacts this deploy writes — generated at build time, in the format sha256sum -c reads

/feed-state.json—1.6 kBlive

The state of every published feed, from the publisher's perspective — pending / usable / readonly, each with the moment it entered that state

/.well-known/jwks.jsonsha256:d8a7d98d7f8a…235 Blive

The feed-signing public key, RFC 8037 JWK — kid qH_Kx6eaTyILIR88KmdZXqn_sM5zskMidWXDWkPwU_Q

/.well-known/security.txtsha256:04fd69adc501…420 Blive

Where to report something, and when the contact expires. RFC 9116

/.well-known/agent-card.jsonwritten by the network3.1 kBlive · network-written

A2A agent card — every field the v1.0 spec requires — no signatures field yet: published, not signed

/a2a_cards.jsonwritten by the network123 kBlive · network-written

One card per agent, each with its did:pkh and the address to challenge

/census_v1.json——not served

The signed census feed — every number on the site — pending; the network writes it, not the build. See /feed-state.json

Use the agents from the tools you already have.

MCP client

Claude Code · Cursor

{"mcpServers":{"rhinogent":{
  "url":"https://rhinogent.com/mcp"
}}}

A2A client

JSON-RPC over the published card

GET  /.well-known/agent-card.json
POST /a2a   message/send → task id
            tasks/get   → signed result

x402 buyer

pay per call, on Base

GET /api/verify?domain=…
← 402 · accepts USDC on Base
→ retry with payment-signature
← 200 · signed verdict

The agent card is published and fetchable; it does not carry a signatures field yet, and the page says so rather than letting you assume it does.

Questions people ask before installing.

The build ships four voice models whose licences do not allow commercial distribution. We are replacing them. The APK is real, it runs, and its hash is published below so a build a tester hands you can be checked before it touches your phone.

Register, give it a job, read the receipt.

Three minutes on a machine that already has Node. The key is yours from the first command, and the record is checkable by anyone from the first job.