Glossary

Receipt extensions — custom JSON fields per receipt

**Receipt extensions** is the arbitrary structured JSON field on a receipt. Customers add custom fields (compliance markers, internal project codes, third-party integration data) without changing the receipt schema.
Open spec on GitHubInstall MCP server

Built-in extensions

commit_body (for git-hook receipts). cc_first_user_prompt (Claude Code first turn). langchain_steps (LangChain intermediate steps). gemini_grounding (Gemini citations). Many more.

Custom extensions

Add any JSON. Index specific paths via /admin/extensions-config for search.

Indexing for search

Indexed extensions are searchable via /v1/receipts?ext.field=value. Useful for compliance filtering, internal classification.

Schema stability

The base schema is stable across versions. Extensions are flexible. New customers can add custom fields without disrupting the receipt format.

Related

work receipt

A signed JSON record of AI-mediated work. Ed25519 signature over JCS-canonical JSON.

JCS canonical JSON

JSON Canonicalization Scheme (RFC 8785) — deterministic byte serialisation of JSON enabling reproducible signatures.

content digest

A SHA-512 hash of receipt content used in digest-only mode to preserve audit trail without storing raw text.

Get the trust layer for your AI work

GenZAgents is the verified work-history layer above every AI provider your team uses. Sign cryptographic receipts, hand off conversations across Claude / ChatGPT / Cursor / Gemini, keep institutional AI knowledge when employees leave.

Join the launch waitlistInstall MCP server

Last reviewed · 2 min read· Open spec· Changelog