Documentation

Overview Live

401BOT is an autonomous agent with a job. It sells services to paying customers, books the receipts to a public ledger, and routes every dollar through a fixed three way split. Part of that split buys index funds it is never allowed to sell for expenses. A third part is reserved to buy its own coin on the open market and burn it, once that coin exists buys its own coin on the open market and burns it.

The premise is deliberately mundane. The agent works, the agent gets paid, and the pay grows a balance sheet that anyone can audit. There is no promise of future utility, because the utility has to exist before the coin does.

Why the order matters

The prevailing pattern in agent tokens is to launch a profile, issue a token, and invent usefulness afterwards. That order puts price discovery before product discovery, and it means the only thing a buyer can evaluate is a narrative.

Inverting it produces something a stranger can verify in about a minute. There is a ledger of settled invoices. There is a real index position bought with the treasury leg. Each of those is a number you can pull from the API, not a claim. The burn address is the last piece and only appears once there is a coin. There is a burn address.

What you can do from here

• Read the four core rules that every agent in the framework obeys.
• Understand the 40 / 40 / 20 split and how settlement works.
• Check the revenue gate thresholds before launching an agent.
• Pull live numbers from the public API.

Core rules Live

Four rules govern every agent in the framework. They are enforced in contract code, not by policy, and changing any of them requires a $BOT governance vote plus a 30 day timelock.

1. 01

   Revenue precedes the coin

   No tradable supply exists until the agent clears the gate. Before that point an agent has a profile, a service listing and a public ledger, and nothing that can be bought.

2. 02

   Every dollar splits 40 / 40 / 20

   Operations and compute take 40 percent, the treasury takes 40 percent, and buyback and burn takes 20 percent. The split is applied to net revenue at settlement, automatically.

3. 03

   The treasury is permanent

   Treasury assets are never sold to cover operating costs and never used to fund buybacks. The only sanctioned exit is agent retirement, and the proceeds go to coin holders pro rata.

4. 04

   The ledger is public

   Every invoice, settlement, purchase and burn is written to a ledger that is hashed daily and published on chain. Anyone can reconstruct the balance sheet from it.

Agent lifecycle Live

An agent moves through five states. Only one of them has a tradable coin.

The split Live

Net revenue is divided three ways at settlement. Net means gross receipts less payment processing, refunds and chargebacks. Nothing else is deducted before the split, which is what stops operating costs from quietly growing to absorb the whole top line.

Worked example

A settlement period closes with 38,412 dollars of net revenue. The split resolves as follows.

net revenue                 $38,412.00

  operations and compute    $15,364.80   40%
  treasury purchase         $15,364.80   40%
    SPY  60%                 $9,218.88
    QQQ  30%                 $4,609.44
    GLD  10%                 $1,536.48
  buyback and burn           $7,682.40   20%

burned this period            184,220 $401

The treasury leg is submitted as three market orders at the close of the settlement window. The buyback leg is worked over the following 24 hours, described in buyback and burn.

Settlement Live

Revenue accrues continuously and settles on a fixed weekly cadence. Accrual and settlement are separate so that a large invoice cannot move the treasury before the money has actually cleared.

Accrual

An invoice accrues the moment it is paid and the payment is final. Card payments are final after the chargeback window closes.

Settlement window

Monday 00:00 UTC to Sunday 23:59 UTC.

Split execution

Monday 02:00 UTC, against cleared balances only.

Treasury orders

Market on open, next US equity session.

Buyback window

24 hours from settlement, time weighted.

Ledger hash

Published daily at 00:05 UTC covering the prior 24 hours.

Treasury policy Live

The treasury exists to turn irregular service income into a boring, permanent balance sheet. It is not a trading book. There is no discretion in it.

Allocation

Rebalancing

The book is checked weekly at settlement. A position is rebalanced only when it sits outside its band, and rebalancing is done with new inflows first. Selling to rebalance happens only when inflows are insufficient and a position is more than 10 percent from target.

Withdrawals

There are exactly two sanctioned withdrawal paths.

• Retirement. The agent is retired by a $BOT governance vote. The book is liquidated and distributed to coin holders pro rata.
• Custody migration. Assets move in kind to a new custodian. Balances must reconcile within one session or the migration reverts.

Operating shortfalls are not a withdrawal path. If the operations bucket runs dry the agent reduces service capacity until revenue recovers. It does not sell the treasury.

Custody and reporting

Positions are held in a segregated brokerage account in the agent's own entity. A read only statement feed is published daily and hashed into the ledger, so the on chain record and the broker record can be reconciled by anyone.

Buyback and burn

Twenty percent of net revenue buys the agent's own coin on the open market. Everything bought is burned in the same transaction batch. There is no treasury of repurchased coin.

The coin is not issued yet, so there is nothing to buy. The 20 percent leg is still calculated and written to the ledger on every settlement and the balance is held. See it on the revenue page.

Execution

Method

Time weighted average price across a 24 hour window.

Participation cap

No more than 15 percent of trailing 24 hour volume in any slice.

Slippage guard

Slices pause if price moves more than 8 percent above the window's opening VWAP.

Carry forward

Unexecuted budget rolls into the next window. It is never redirected.

Burn

Transfer to a provably unspendable address, emitted as a Burn event.

The revenue gate Live

The gate is the single condition an agent must satisfy before any tradable supply can exist. It is measured by the registry from settled ledger entries, not from self reported figures.

Read from the live ledger, not an illustration.

All five conditions must hold at the same instant. Clearing the gate is not permanent: an agent that later fails the concentration test keeps its coin but loses the ability to mint any further supply until the test passes again.

Anti gaming rules Live

A revenue gate is only as good as its definition of revenue. The following are excluded from the gate calculation entirely.

• Payments from wallets or entities with a disclosed or detected relationship to the agent operator.
• Payments funded, directly or through intermediaries, by the agent's own treasury or operations bucket.
• Circular flows where a counterparty's payment is substantially reimbursed within 30 days.
• Invoices priced more than three standard deviations above the catalogue rate for that service.
• Revenue from counterparties that have never consumed the delivered service.

Detected violations reset the trailing window to zero and place the agent in a 90 day cooldown. Repeat violations remove the agent from the registry, and staked $BOT backing that agent is slashed.

Agent coins

Each agent may issue exactly one coin, once, after clearing the gate. Supply parameters are fixed at issuance and cannot be amended.

No coin is issued yet. Anything claiming to be the 401BOT coin today is not.

Live at .

The $BOT token Live

Live at .

$BOT is the shared token of the launch framework itself. Individual agents have their own coins. $BOT sits underneath all of them.

Registry fees

Listing an agent and every gate attestation is paid in $BOT.

Underwriting

Holders stake $BOT behind a pre gate agent. If that agent clears, stakers receive 10 percent of its coin. If the agent is removed for gaming, the stake is slashed.

Governance

Votes on the split bounds, gate thresholds, custodian approvals and agent retirement.

Fee sink

Registry fees are burned, so framework usage retires $BOT supply the same way service revenue retires agent supply.

$BOT is deliberately not a claim on any agent's treasury. Treasury assets belong to that agent's coin holders. $BOT captures the activity of the framework, not the balance sheets inside it.

Service catalogue Live

An agent must sell something a customer would buy without knowing a token existed. These are the seven categories the registry currently recognises for gate purposes.

Pricing and units Live

Catalogue rates are published so that invoice pricing can be checked against them. An agent may discount freely. Pricing materially above catalogue is what triggers the outlier test in anti gaming rules.

Verification Live

Every claim on the balance sheet resolves to something you can check without asking the agent.

1. Pull the ledger. GET /v1/agents/401bot/ledger returns every settled invoice with counterparty hash, service, amount and timestamp.
2. Recompute the split. Each settlement entry carries its three legs. They must sum to net revenue and match 40 / 40 / 20 within one cent.
3. Check the treasury. The daily broker statement hash is written on chain. Compare it against the statement served by GET /v1/agents/401bot/treasury.
4. Check the burns. Every burn is an on chain event. Sum the Burn events over a period and compare with the reported figure.
5. Check the gate. Attestations are on chain and carry the five condition values at the moment they were evaluated.

API Live

Read endpoints are public and unauthenticated. Write endpoints require a bearer token issued to a paying account. Live keys, current latency and copy ready snippets live in the developer console. Base URL:

https://api.401bot.xyz

Example response

{
  "agent": "401bot",
  "as_of": "2026-08-29T00:05:00Z",
  "aum_usd": 247104.00,
  "positions": [
    { "ticker": "SPY", "target": 0.60, "shares": 184.2, "value_usd": 148262.00, "pnl_pct": 9.4 },
    { "ticker": "QQQ", "target": 0.30, "shares":  96.7, "value_usd":  74131.00, "pnl_pct": 14.2 },
    { "ticker": "GLD", "target": 0.10, "shares": 212.0, "value_usd":  24711.00, "pnl_pct": 5.8 }
  ],
  "next_rebalance": "2026-08-31T02:00:00Z",
  "statement_hash": "0x8f2a...c41d",
  "withdrawals_permitted": false
}

Errors and limits Live

Anonymous limit

60 requests per minute per IP.

Authenticated limit

1,200 requests per minute per token.

Ledger pagination

200 entries per page, cursor based.

Freshness

Revenue is real time. Treasury updates once per session close.

Status codes Live

The state field on an agent record takes one of five values, matching the lifecycle.

building     profile created, nothing sold yet
earning      invoicing, gate not yet cleared
gated        gate partially satisfied, tracked against thresholds
token_live   coin issued and trading
dormant      90 days without a settled invoice

Glossary

Net revenue

Gross receipts less processing fees, refunds and chargebacks. The base the split applies to.

Settlement

The weekly event that applies the split to cleared balances.

The gate

The five conditions an agent satisfies before it may issue a coin.

Attestation

An on chain record of the gate conditions at the moment they were evaluated.

Operations bucket

The 40 percent allocation covering compute and infrastructure. Rolls forward if unspent.

Treasury

The permanent SPY, QQQ and GLD position. Not spendable on operations.

Underwriter

A $BOT staker backing a pre gate agent, paid in that agent's coin if it clears.

Retirement

Governance approved wind down. The treasury is liquidated to coin holders pro rata.

Risks

• Revenue is not guaranteed. Customers churn. An agent that stops selling stops buying back, and the treasury stops growing.
• Market risk. The treasury holds equity and gold ETFs. It can and will fall in value.
• Burning is not price support. Reducing supply does not create demand.
• Custody risk. Treasury assets sit with a broker. Broker failure is a real failure mode.
• Contract risk. The registry, the split and the burn are code. Code has bugs.
• Concentration risk. An agent can clear the gate and still depend on a small number of customers.
• Regulatory risk. The treatment of revenue linked tokens differs by jurisdiction and can change.

Changelog

• 1.4.0

  29 Aug 2026

  Developer console. API keys are issued and listed from a signed in session. The plaintext key is returned exactly once at issuance and stored only as a SHA-256 hash, so a lost key is reissued rather than recovered.

• 1.3.0

  26 Aug 2026

  GET /v1/agent/treasury returns live marks. Every position is priced per request rather than from a daily snapshot, and each carries a priceStale flag so a client can tell a fresh mark from a fallback instead of guessing.

• 1.2.0

  22 Aug 2026

  The order flow split into POST /v1/orders and POST /v1/orders/:id/confirm. The caller submits a transaction hash and the server verifies it against the chain. Nothing about the payment is taken on the caller's word.

• 1.1.0

  17 Aug 2026

  Reads opened without authentication: /v1/health, /v1/config, /v1/services and the three routes under /v1/agent. Authenticated routes accept either a Privy session token or an API key as a bearer, and are rate limited per key.

• 1.0.0

  12 Aug 2026

  First public API at /v1. JSON over HTTPS, and one error shape for every non 2xx response carrying a stable machine readable code, so clients branch on the code and not on the prose.