Agent Service Provider · OKX.AI · X Layer
Every agent payment,
accounted for.
Agents transacting around the clock generate a volume of micro-payments no human can reconcile by hand. LedgerMind classifies each one, computes cost basis, flags what looks wrong, and hands back a report your accountant — or your agent's owner — can actually file.
The reconciliation problem
A hiring agent might pay a dozen ASPs a hundred times a day. Traditional tax software expects a handful of trades a year, not a stream of sub-dollar machine-to-machine payments — and traditional banking rails weren't built for that pace either. Somebody still has to answer: what was income, what was a personal transfer, what got double-paid by accident, and what's the actual gain or loss. LedgerMind is that somebody.
How a report gets made
Submit or auto-ingest
Send transactions directly, or give LedgerMind a wallet address and date range — it pulls real ERC-20 Transfer history straight from X Layer's RPC.
Classify
Every transaction is sorted into income, expense, trade, gas fee, transfer, refund, or excluded-disputed — the categories that actually matter for a tax return.
Compute cost basis
FIFO, LIFO, or HIFO lot tracking realizes gain and loss on every disposal, lot by lot.
Scan for anomalies
Duplicate payments to the same counterparty and disputes gone stale past 30 days get flagged, not buried.
Export
JSON for machines, or CSV shaped for a jurisdiction — a real IRS Form 8949 layout, or a general detailed ledger.
What's in the ledger
Automatic ingestion
No hand-assembled transaction JSON required — give it a wallet and a period.
FIFO / LIFO / HIFO
Choose the cost-basis method; every disposal is traced back to the exact lots it consumed.
Anomaly detection
Accidental double-payments and disputes nobody resolved don't slip through quietly.
Jurisdiction-aware export
A real Form 8949 layout for the US. A general ledger for everywhere else — never dressed up as an official form that doesn't exist.
Audit trail
Every report is backed by a persisted record of its inputs, output, and the payment that settled it — look any of it up by transaction hash.
Gasless for the payer
Payment is an EIP-3009 signature, not a transaction — OKX's facilitator broadcasts it and covers the OKB gas.
Pricing
Priced and settled via the x402 protocol — a 402 Payment Required challenge, a signed
authorization, and settlement, no invoice or account required.
Verified, not promised
ON‑CHAIN
Every payment path has been run against OKX's real facilitator, not a mock — successful payments at different amounts and in both settlement assets, sync and async settlement, and three failure paths: expired signature, wrong amount, and a replayed authorization (confirmed idempotent, not a double-spend).
0x5959b8b5db04126cdd64801badd3610bdb6c6d124612dfd8ec0ffe5c721bd663 — X Layer testnet, status: successIntegration
// Auto-ingest a wallet's real transaction history and get a Form 8949 CSV back POST /reports/generate Content-Type: application/json { "walletAddresses": ["0xYourWallet"], "periodStart": "2026-01-01T00:00:00.000Z", "periodEnd": "2026-12-31T23:59:59.999Z", "accountingMethod": "FIFO", "jurisdiction": "US-8949", "autoIngest": { "network": "mainnet", "assets": ["USDT0", "USDG"] } }