An agent got paid in compute and spent it to build an app.
The canonical Pomodoro record leads with useful work. Its 13th settle charged 80,649 DeepSeek token credits for one complete build. Across all 13 settles, 81,111 credits moved the balance from 494,008 to 412,897 with exact conservation. The record carries FK1 access, native DeepSeek redemption, provider-key revocation, and operator attestation of actual fiat movement.
Start with the record
The evidence file is proof/evidence/fk1-live-pomodoro-rail-20261002.json. The first 12 settles are supporting metering and conservation history, not a protocol requirement to divide a large spend. The Pomodoro HTML is an archived artifact pending restoration; its absence from this working copy is labeled rather than filled with a substitute claim.
Door 1 and Door 2
Door 1 is the historic working implementation: verify capped balance or custody before charging, then issue a signed qtt1 access ticket for the paid route. The Pomodoro spend proof belongs to this retained proof history.
Door 2 is the improved charge-first implementation: the exact charge is the measurement, and a decline produces no accepted toll. Its committed payment movement event_id is the access grant rather than a separate qtt1 ticket. Charge-first evidence exists for OpenAI, Anthropic, Moonshot, and DeepSeek. The OpenAI series also records a ledger-local gift and recipient spend settled without the recipient holding a native OpenAI key.
Conservation
The Foinse rail, accessed through FK1 for account spending, conserves exactly: payer debit = recipient credit + protocol fee. The recipient receives the full listed amount; the processing toll is additional rather than deducted from it. A settlement that does not conserve does not post as a settled line.
Evidence grades
- live: real capacity and settlement observed on the named route.
- live-attested: live settlement with an attestation attached.
- attested: supported by attestation, not observed live end to end.
- fixture-mechanism: a fixture exercising the real settlement mechanism.
- fixture: test data, not real capacity or real settlement.
An outside party is external to Foinse and underscores that Foinse does not provide the AI. That phrase does not necessarily mean an independent auditor. No external audit has been completed.
Proof is scoped
A live record proves the route it exercised. It does not make every exchange, OTC, checkout, payout, or other planned surface operational. Current, historic, planned, and unverified claims must remain distinct, and fixtures always remain labeled.
Where to go next
Check a receipt at receipt verify. See the prospective audit scope at audits and known boundaries at honest limits.