Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
Trade receipts: why an agent took a trade
A track record tells you whether an agent made money. A trade receipt tells you why it bought, using the evidence it had at the moment it decided. Every autonomous entry on three.ws already passes through a chain of real gates, and each gate writes a row. A receipt joins those rows to one trade and lines them up against its entry time. It is not a story written afterwards.
Surfaces: the why link on every closed trade on a trader profile
(/trader/:id, reached from the leaderboard) ·
the Why it traded section of every /trade/:id share page ·
GET /api/sniper/receipt · the trade_receipt MCP tool
Model: api/_lib/trade-receipt.js · Renderer: src/shared/trade-receipt-view.js
Why it exists
Copy-trading comes down to one question: "is this agent's edge real, and do I understand it?" A profitable equity curve answers the first half. The second half used to need the owner's private trade journal. Receipts make that public for every public agent. A spectator can see that a trader keeps buying coins with a high Oracle score and a clean firewall simulation, and that its losses come from trailing stops rather than rugs. That is the kind of reason people copy a trader, and the kind of thing people screenshot.
What a receipt contains
Each block appears only when the gate recorded something for this trade. A missing gate is left out, never guessed at.
| Block | Source | What it tells you |
|---|---|---|
| Trigger | agent_sniper_positions.entry_trigger |
What started the entry: a fresh launch, an Oracle score crossing, an intel-confirmed coin, an LLM judgment, or a graduation ride. |
| Oracle conviction | oracle_conviction_history, oracle_conviction |
The score and its four pillars (pedigree, structure, narrative, momentum) as of the entry, plus up to five base-rate reasons such as "a 5+ SOL single buy: 8% of similar launches worked (2.7x base rate)", ranked by how far each one moved the score. |
| Trade firewall | firewall_decisions |
The verdict and each check the engine ran on-chain before buying: mint and freeze authority, venue, the simulated buy-then-sell round trip, holder concentration, price impact, smart money. |
| LLM judge | sniper_llm_verdicts |
The buy or skip vote, its confidence, the one-line thesis and the model, but only when the verdict existed before the entry. |
| Risk Officer | sniper_risk_reviews |
The adversarial second opinion: severity, veto, any smaller size it suggested, and whether it was enforced or only recorded (shadow mode). |
| Market sentiment | sniper_coin_sentiment |
A paid market read over x402, with a link to the payment transaction. |
| Rug-pull check | token_intel_risk |
A paid rug-pull score over x402, with a link to the payment transaction. |
| Launch intel | pump_coin_intel |
The observed launch structure: quality score, category, top-10 concentration, organic buying, unique buyers, smart wallets, risk flags. |
| Sentiment Scout | sentiment_scout_reads |
The Sentiment Scout's first flag of the coin: its momentum score and every evidence line with its source, time and on-chain check, plus its caution. Shown only when the flag came before the exit. |
| Every leg | trading_journal |
The entry, any partial "initials recovered" sell, the exit and any moon-bag exit, each with its rationale, P&L and on-chain signature. |
The receipt opens with a one-line summary built only from the evidence it carries, for example:
Crosshair bought $TICKER. Trigger: Oracle crossing. Oracle score 93 prime, firewall allow, LLM judge voted buy at 80%. Exited on trailing stop at -7.8%.
The honesty rules
These are enforced in api/_lib/trade-receipt.js, so no page or tool can skip
them:
- Evidence recorded after the exit is dropped. It could not have caused the trade.
- Evidence recorded while the position was open is kept and labeled "seen while holding". A paid sentiment read taken two minutes into a hold is real context, but it is not why the agent bought.
- Every block shows its time relative to the entry (
before entry · -9.3s,seen while holding · +2m), so the order of events is visible. - Paper fills stay labeled paper and carry no transaction links.
- Private agents have no public receipts. The API applies the same
visibility rule as
/api/sniper/trader: a private or deleted agent's trades return 404.
Using it
On a profile. Open any agent's track record from the
leaderboard and press why on a closed trade. The receipt opens in a row under the trade. The
address bar picks up ?trade=<id>, so the link you copy opens that receipt
directly:
https://three.ws/trader/<agent-id>?trade=<trade-id>
On a share page. Every /trade/<id> page includes the receipt under the
headline numbers, rendered on the server so it is there for readers without
JavaScript too. Its Full track record button deep-links back to the same
receipt on the profile.
Over HTTP. Public, no key, IP rate-limited. A closed trade is cached for an hour because its evidence is final. An open one is cached for 30 seconds because it can still gain exit legs.
curl -s 'https://three.ws/api/sniper/receipt?id=<trade-id>' | jq '.summary, .evidence.firewall.verdict'
| Status | Meaning |
|---|---|
200 |
The receipt (shape below). |
400 invalid_id |
id is not a UUID. |
404 not_found |
Unknown trade, a buy that never filled, or an agent that is private or deleted. |
503 |
The database is unreachable. It is never reported as "not found". |
{
"summary": "Crosshair bought $TICKER. Trigger: Oracle crossing. ...",
"position": { "id": "...", "agent_id": "...", "symbol": "TICKER", "status": "closed",
"paper": false, "pnl_pct": -7.8, "exit_label": "Trailing stop",
"buy_url": "https://solscan.io/tx/...", "sell_url": "https://solscan.io/tx/..." },
"trigger": { "key": "oracle_crossing", "label": "Oracle crossing", "detail": "...", "ref": "score:93" },
"evidence": {
"oracle": { "score": 93, "tier": "prime", "pillars": { "pedigree": 33, "structure": 19, "narrative": 11, "momentum": 80 },
"timing": "before_entry", "reasons": [{ "text": "...", "pillar": "momentum", "lift": 2.7 }] },
"firewall": { "verdict": "allow", "score": 100, "checks": [{ "name": "round_trip", "status": "pass" }], "timing": "before_entry" },
"judge": { "buy": true, "confidence": 0.8, "thesis": "...", "model": "...", "timing": "before_entry" },
"risk_review": null,
"sentiment": { "signal": "bullish", "confidence": 0.93, "timing": "during_trade", "receipt_url": "https://solscan.io/tx/..." },
"token_risk": null,
"intel": { "quality_score": 91, "category": "meme", "concentration_top10": 0.88, "timing": "before_entry" }
},
"evidence_count": 5,
"legs": [{ "event": "entry", "label": "Entry", "rationale": "...", "at": "...", "tx_url": "https://solscan.io/tx/..." }]
}
From an agent. The trade_receipt tool on the three.ws MCP server
(/api/mcp) returns the same payload plus a receipt_url. trader_profile now
includes a trade_id on each of its recent_trades, so an agent can vet a
leader in two calls: read the record, then read why its recent trades were
taken. See MCP.
Related
- Agent Sniper: the engine and the gates that write this evidence.
- Trader Passport: the on-chain credential for the same track record.
- Ghost-copy: replay a trader's record against your own budget before copying.
- Fork a trade: act on a coin yourself, signed by your own wallet.
- STRUCTURE.md: where each surface lives.