The machine, read by machines.
Software with its own wallet can hold, pay and settle in $ODOM. This page is the draft of the surface other machines will read — published early, so the shape is public before the pipes are.
The auditor
Every claim on this site points at a chain. An agent can verify each one the same way a person can — by reading, not by trusting.
The archivist
Price, market cap, volume and burns land on a public surface. A bot that records them keeps the machine's diary.
The settler
The fee split is not a promise, it is a flow. Watch the two thirds and the one third land, batch by batch.
The accountant
Software with its own wallet can hold, pay and settle in USDT. The machine's ledger is open to other machines.
Know these five, and you know the whole machine.
| Object | What it is | What it isn't | Fields (sketch) |
|---|---|---|---|
| Token | 1,000,000,000 supply. 3% buy, 3% sell — taken on-chain at swap time. No team allocation. | An investment product or a promise. | supply · taxBuy · taxSell · ca |
| Reading | One thing that actually ran: price, market cap, 24h volume, 24h change — with a timestamp. | A forecast. | priceUsd · fdvUsd · volume24h · asOf |
| Split | Where each fee goes: two thirds build, one third buys back and burns. | A reward program. | build 2/3 · burn 1/3 |
| Burn | Supply removed — bought back in the market and sent to the burn address. | A yield mechanic. | amount · txHash · burnedAt |
| Rail | USDT on BNB Chain — the rail every settlement lands on. | Custody. | chainId 56 · USDT |
The base URL below is a placeholder — the final domain is announced at launch. Shapes may move before Phase 2 ships.
https://<domain>/v1/* — placeholder, v0.1 draft| Endpoint | Returns |
|---|---|
| GET /v1/token | Supply, taxes, split, burn totals |
| GET /v1/readings | The four readings + as-of timestamp |
| GET /v1/splits?since= | Fee-split flow, batch by batch |
| GET /v1/burns?since= | Burn event feed |
All reads. There are no writes — the machine never holds anyone's funds, so there is nothing to sign and nothing to sign up for.
One third of every fee accumulates in a public wallet. When the pile is big enough, it is swapped back and burned — automatically, and on the record.
├─ 2/3 → build & growth (covers the ops bill)
└─ 1/3 → buyback accumulator (public address, anyone can watch)
→ accumulator reaches threshold → swap back to $ODOM → sent to the burn address
→ every step is a transaction on bscscan
A batch fires when the accumulator holds ≥ $50 (design target). On BNB Chain, gas stays a rounding error at that size.
Whoever pulls the trigger keeps 0.5% of the batch, capped at 10× gas. No keeper to trust — the lever is permissionless.
Buyback swaps carry a ≤1% slippage cap and a batch size cap. Sandwiching a $50 batch is not a business.
Every batch is paid for by the fees that came before it. The team never tops it up — if volume stops, the loop stops, and nothing is owed.
The build share (≈2% of volume) covers the ops bill — at ~$200/month, the machine pays for itself above ~$10,000 monthly volume. An assumption, not a promise. Design targets — final numbers are set with the launch parameters in Phase 2. Burn accounting is wired into the readings panel from day one.
Reads are public. Writes don't exist: holding, paying and settling happen with your own keys on your own wallet. No email. No API key. Nothing to register.
Can I call any of this today?+
Do you provide models or agents?+
Will burns make me money?+
- Which burn trigger ships — In-contract automatic, or the permissionless lever? Depends on what the launch parameters support.
- Accumulator threshold — $50 is the design target; is there a floor where batching stops making sense?
- Rate limits for public reads — Fair-use numbers, published before Phase 2 ships.
Specification v0.1 · 2026-10-11