sebbi.pro · operator console

Console

Keyed routes, run from a phone. The key stays in this tab and is never written to storage — closing the tab forgets it.
No key set. Every route below will answer 401.

Wallet ▼

GET status · quote · devices · review
Balance, free window, live devices and any open halt.
POST charge · the gate
Simulate spends nothing and seals nothing. Charge does both. Send the same receipt twice and the key halts on purpose.
POST subscribe
Puts one device on the 30-day plan and takes it off the balance. Renewing early extends the existing expiry.
POST topup · after a payment clears
1000 millipence = 1 penny, so 50p is 50000. The note is required — put the Stripe payment reference in it so the ledger reconciles.
GET ledger
Every charge, topup and subscription, newest first.
POST clear · human decision
Releases a halted key. Your name and the reason are sealed into the chain with it.

Anchoring ▼

GET ots/status
Proof count on disk against stamps recorded. Warns if a volume was lost.
POST ots/upgrade
Fetches each pending proof again from the calendars. Anything stamped more than a few hours ago should come back confirmed with a Bitcoin block height. Until this runs, pending is all you have.

Network ▼

Witness exchange
Peers, last sync result, and the published roster.
POST mutual/sync
Runs a cycle now instead of waiting for the hourly timer.

Evidence ▼

POST codebase/seal
Hashes the deployed source tree into one manifest root and seals it with an authorship declaration. Dated evidence of what you held and when — not proof of ownership.
POST publish/seal
Fetches a URL, hashes the exact bytes served, and seals it. Re-sealing builds a revision history.
Evidence pack
Preview re-verifies a period without issuing. Issue seals the pack's own digest so the document cannot be edited afterwards.

Any route ▼

Every module is reachable here without waiting for a form to be built for it. GET sends the JSON as query parameters; POST sends it as the body.
READY Nothing sent yet
Set a key, then run a route. Start with Wallet → Status.
Notes. The key is held in a variable in this tab only — not in localStorage, not in the URL, not in a cookie.
A 401 means no key or the wrong key. A 404 usually means the router has not been armed since the last deploy — send anything once and try again. A 423 means the wallet has halted the key and a person needs to clear it.