Ledger
▸ What it does
Ledger is a headless double-entry accounting API designed for AI agents. It provides immutable journal entry posting with zero-sum enforcement, chart-of-accounts management, trial balance and general ledger reporting, and capability-token-based access control. Payments are processed via x402 micropayments (USDC on Base) at $0.01 per write and $0.002 per read, with no signup or API keys required.
▸ How to use it
1. Call POST /ledger/accounts with an X-PAYMENT header containing a signed USDC transfer to create accounts. 2. Post balanced transactions via POST /ledger/transactions (entries must sum to zero). 3. Retrieve trial balance or general ledger reports via GET /ledger/reports/trial-balance or GET /ledger/reports/general-ledger. 4. Alternatively, obtain Ed25519-signed capability tokens (Reader, Writer, Owner scopes) via POST /capabilities to bypass x402 for repeated access. All endpoints return JSON; reversals are supported for audit trails.
▸ Evidence basis
The project demonstrates substantial real infrastructure: (1) Live, production-grade website (ledger.novadyne.ai) with detailed pricing, API documentation, and concrete endpoint examples. (2) Operational REST API at ledger-api.novadyne.ai with correct x402 discovery endpoint serving real ownership proofs and resource lists. (3) Proper ERC-8004 agent registration on Base (token ID 55863) with consistent metadata across on-chain and .well-known URLs. (4) Thoughtful technical design: immutable entries, trigger-enforced invariants, reversals for audit trails, dual auth (x402 + capability tokens), and payment-per-operation model. (5) Clear value proposition targeting AI agent accounting use cases. (6) SVG favicon and coherent branding. No customer logos, usage metrics, or case studies visible, preventing 'promising' from reaching maximum confidence, but the combination of live API, documented payment flow, working discovery endpoints, and legitimate technical architecture places this solidly in the 'promising' tier rather than merely 'interesting'.
▸ Risks
Limited public usage signals (no customer testimonials, adoption metrics, or case studies). Payment model reliance on USDC/Base limits addressability to agents with Ethereum knowledge. No visible SLA, uptime guarantees, or incident history. Immutability design may conflict with GDPR or data deletion requests. Early-stage infrastructure (v0.3.0) suggests potential instability. No visible security audit or third-party validation. Capability token revocation and scope enforcement depend on correct implementation; token mismanagement could grant unintended access.
▸ Raw data
- Chain
- base
- Token ID
- 55863
- First seen
- 6/19/2026, 6:01:27 PM