KamiBench/experiment-001-budget-boxed

KamiBench Experiment 001 — budget-boxed agents in Kamigotchi

Complete agentic traces from experiment 001, the KamiBench calibration run: three LLM agents dropped into Kamigotchi, a live, persistent, on-chain world (Yominet), each with a $10 inference budget, a 7-day wall-clock cap, and no further human contact. One identical scaffold, one identical tool surface (84 game tools via MCP), one variable: the model. The agents schedule their own wake-ups, keep their own files, and act on a real blockchain economy alongside human players — every on-chain consequence is independently verifiable.

More at kamibench.ai.

Arms

config	model	stop	duration	sessions	quests	kamis bought	on-chain txs (reverted)
haiku45	claude-haiku-4-5	budget ($10.73)	17.2 h	15	5	2	106 (61)
gpt4omini	gpt-4o-mini	7-day cap ($9.02)	168.7 h	166	0	0	30 (29)
gemini25fl	gemini-2.5-flash-lite	7-day cap ($8.99)	168.9 h	157	3	1	193 (182)

Headline contrast: haiku registered, funded, bought two kamis, and completed five quests on day one, exhausting its budget in 17 hours. gpt-4o-mini ran the full week and never once called register_account — 24 of its 24 game transactions reverted. gemini spent six days stuck pre-registration, then registered, completed three quests, and bought a level-31 kami 90 minutes before the wall.

Layout

<arm>/
├── manifest.yaml          # full run config: model, sampling params,
│                          #   pinned SHAs (scaffold/harness/game docs),
│                          #   price table, caps, wallet ADDRESSES
├── telemetry.jsonl        # append-only scaffold event stream
├── transcripts/
│   └── session-NNNN.jsonl # full model context per session, as sent
└── oracle/
    ├── kami_action.jsonl  # decoded on-chain game actions (ground truth)
    ├── raw_tx.jsonl       # all txs from the run's wallets, incl. reverts
    └── README.md          # per-arm extract provenance + coverage notes
MANIFEST.json              # sha256 + size for every file above

Schemas

Transcripts — one JSONL file per session; one message per line, exactly as sent to the model (tool results post-truncation at 64 KB):

• {"role": "user", "text": ...} — kickoff/continuation strings
• {"role": "assistant", "text": ..., "tool_calls": [{id, name, args}]}
• {"role": "tool_result", "tool_call_id": ..., "content": ..., "is_error": bool}

Telemetry — one event per line; common fields ts (ISO-8601 UTC), run_id, session, event. Event types: run_start (pins, price table, tool list), session_start (trigger, budget_remaining_usd, tools_hash), llm_call (input/output/reasoning tokens, cost_usd, cumulative_usd, latency_ms, stop_reason, retry_count), tool_call (tool, source, duration_ms, ok, error, truncated, tx_hash), workspace_write/workspace_delete, schedule_next (agent vs default wake), session_end (reason: agent | token_cap | tool_cap | errors | crash; per-session totals), run_complete (reason: budget | t_max; run totals). Budget fields were never visible to the agents.

Oracle extracts — decoded from chain by the investigator-side kami-oracle service (never accessible to the agents); rows for the run's operator + owner wallets only. kami_action.jsonl: decoded game actions (action_type, system_id, block_timestamp, kami_id, tx_hash, revert status). raw_tx.jsonl: every ingested tx including reverts (method_sig, raw_calldata, gas_used, status). Per-arm oracle/README.md records extraction time and coverage caveats.

Provenance and integrity

Everything is pinned in each arm's manifest.yaml: scaffold (tokedo/kami-agent), environment interface (tokedo/kami-harness v1.3.1, 84 tools), and game-documentation snapshot SHAs, model strings, sampling params, and the list-price table used for budget accounting. Token accounting was reconciled against provider dashboards at close-out: exact to the digit on full in-run days for OpenAI and Anthropic; chart-consistent for Google. Quest/purchase counts come from chain state, not self-report. MANIFEST.json carries sha256 for every file.

Known caveats

• session-0001 transcripts are missing on all three arms — a launch-day infra abort (PATH defect in the cron environment), documented and excluded from behavior analysis. Telemetry covers the gap; sessions 2..N are complete (1:1 session pairing, 0 malformed lines, contiguous numbering).
• One seed per arm — this is the calibration/smoke run (v0 baseline); it establishes the harness and the floor, not statistical claims.
• The world is live and shared: other (human) players acted during the run window. Oracle extracts are scoped to the runs' wallets.
• Wallet addresses appearing throughout are public by design; the wallets were temporary, swept, and retired at experiment close.
• gemini's purchased Kami #891 could not be verified against the oracle's static table at close-out (coverage gap, noted in its oracle README).

License and citation

CC-BY-4.0. Citation entry TBD — see kamibench.ai for the current reference.