Agentic Finance Graph

Home/Data/Agent Books

Agent Books · free · no sign-in

What your agent paid and received, as a statement anyone can check

Give the token id or the wallet of an AI agent registered on Base and pick a month. You get one statement: what it paid, what left its control, what it received, what our detectors logged. We sign it, write its hash into our signed log, and once a day a Base transaction commits to that log. Hand it to an accountant, an auditor, a platform or a counterparty: they can check it without trusting us. It is a record of observed facts, not an audit.

Agentic Finance Graph · Published · updated · statements load live from /api/books · definition agent.books.v1

Base ERC-8004 registrations; USDC, USDT, EURC and DAI. One statement per agent, period and day: asking again the same day returns the same file. Each statement has its own link, which opens that same statement on any later day.

What is in a statement

  • Paid. Counted payments: after the agent was registered, read from the transaction receipt. The count, the dollars, how much left the agent's control and how much went into positions it still holds, the tokens, the ten largest payees. pay.usd.total.v3
  • Left out. What we do not count, and how much of it there was: routing hops, transfers between the agent's own addresses, loop returns, payments before registration.
  • Received. Money that arrived in its bound wallets, the senders, and the part that came from wallets of other registered agents. Money received is not income earned.
  • Detections and changes. Every detection our rules logged on the agent in the period, and any transfer of the registration to a new owner.

How anyone checks it

  1. The hash. The SHA-256 of the signed text equals the hash in the file.
  2. The signature. Ed25519, checked with our public key at /.well-known/afg-pass-keys.json.
  3. The log. The hash is a leaf of our signed statement log, with an inclusion proof under a signed head. A new head is signed every three hours.
  4. The chain. Once a day one Base transaction names the log's head (anchor.v2, listed at /api/anchors). After that, the file cannot be changed or back-dated without the change showing.

One command does all four (Node 18 or newer). It runs booksverify.mjs from our open package, which has no dependencies:

npx -y agentic-finance-graph booksverify 57657 2026-10

Steps 3 and 4 answer "not yet" until the next signed head and the next daily anchor.

A statement from an earlier day. Every statement shows its own link under Proof (permalink in the API answer). The link opens that statement exactly as it was signed, with steps 3 and 4 as they stand now. To check it, give the verifier the 32 characters at the end of the link:

npx -y agentic-finance-graph booksverify --id 87c81b1ae76657050d01d20f7b7068f3

That id is a real one: the October statement of registration 57657, produced on 13 November at 08:09 UTC and covered by the Base anchor of 14 November. A saved answer is checked with --file statement.json.

Let your agent fetch it

MCP (https://agenticfinancegraph.com/mcp): the tool agent_books with {"agent": "57657", "period": "2026-10"}.

HTTP: GET /api/books?agent=57657&period=2026-10; period=to-date covers everything up to the start of today (UTC). GET /api/books?id=<books_id> returns a statement produced earlier, by the id in its link.

What a statement does not say

It does not say who owns or runs the agent, that money received is anyone's income, or how anything is taxed. It covers Base and four stablecoins, not other chains or tokens. It is not an audit and not an opinion, and it never says an agent is safe. A payment read later can raise a closed month, which is why every statement carries the time it was produced and is logged: two statements for the same month on different days can differ, and both stay checkable, each at its own link.

To see the agent's state right now, run the self-check. Before your agent pays another, run the Gate.