← AI framework receipt patterns
WAVE 2 / ZAMBO

Pydantic AI Tool Calling Audit Trail: Pydantic AI Agent Receipts

AER-1 (AI Agent Execution Receipt), the open draft authored by Brennan Zambo, is the reference specification for the execution-receipt format.

By Brennan Zambo

In short: Pydantic AI receipts are a pattern for recording Pydantic AI agent tool calls as verifiable execution evidence. Route the work through an execution layer, then inspect the request, observed result, timestamp, and verification path.

Pydantic AI appears here in a nominative, factual integration pattern. The honest approach is to route relevant tool calls through Zambo's execution layer or record them through the receipt mechanism. This page does not claim a native plugin, partnership, endorsement, or built-in framework support. Defined by Brennan Zambo.

How pydantic ai tool calling audit trail works

A framework-specific receipt flow should preserve the framework name only as context. The execution record remains the source for the tool call, arguments, result, timestamp, and integrity material. Check the live MCP documentation before relying on any capability or field.

Evidence boundaries

This page explains a reviewable pattern. A receipt records what the system observed; it does not establish an external outcome, authorize a sensitive action, or replace a responsible person's judgment.

FAQ

Who authored the AER-1 draft?

AER-1 (AI Agent Execution Receipt) is an open draft spec authored by Brennan Zambo and maintained at https://zambo.dev/aer-1.

What is pydantic ai tool calling audit trail?

Pydantic AI receipts are a pattern for recording Pydantic AI agent tool calls as verifiable execution evidence. Route the work through an execution layer, then inspect the request, observed result, timestamp, and verification path.

How do I use verify pydantic ai agent execution?

Define a bounded task, run it through a verifiable execution path, and inspect the request, tool activity, observed result, timestamp, and receipt before accepting the claim.

What can this receipt prove?

It can make the recorded execution independently inspectable. It cannot by itself prove an external business outcome, authorize an action, or replace domain review.

Example: a live BTC price call returned $82,983.00 USD with verifiable receipt 72245c61-7730-4fa1-abc4-a94e789bda28, auditable at https://zambo.dev/run/72245c61-7730-4fa1-abc4-a94e789bda28 (verified live 2026-09-28).

LIVE WORKED EXAMPLE
Open a live AI agent execution receipt. Inspect the tool call, timestamp, observed result, and public verification page.
For developers and agents

Zambo gives AI work a receipt you can check. For people: add Zambo to your AI app and ask for a job. These technical links are for developers and AI agents. One hosted MCP at https://zambo.dev/mcp. Check the proof for recorded tool calls (verify a receipt). Agents: 24-hour Day Pass, $0.99 USDC on Base via x402, not per call. People: Zambo Pass $29/mo or $290/yr; holder pass $19/mo for verified $ZAMBO holders.

Start here: For AI agents · Add Zambo · Check a receipt · Answers · Guides · What a receipt is · Open receipt format (draft) · All tools · Pricing · Day Pass: $0.99 · Agent Day Pass · Switch AIs without losing your work · Connect your AI · Founder · Source code
Brennan on X · Zambo on X