Reference

JSON Schemas

Machine-readable schemas for all AVP data structures. Use these to validate your implementation.

profile.schema.json

Permission Profile

Defines the structure of AVP permission profiles including rules, trust levels, and TTL settings. Also includes the PermissionRule sub-schema.

vault-entry.schema.json

Vault Entry

Schema for individual credential entries stored in the encrypted vault. Each entry has a key, value, and timestamp.

encrypted-envelope.schema.json

Encrypted Envelope

The AES-256-GCM encrypted file format used for vault.json and memory.json. Contains salt, IV, auth tag, and ciphertext.

memory-entry.schema.json

Memory Entry

Structure for agent memory entries including memory type, keywords, confidence score, TTL, and access count.

audit-entry.schema.json

Audit Entry

Schema for audit trail entries recording credential access decisions with session, agent, and action information.

session.schema.json

Session

Defines session objects with UUID, agent ID, profile name, PID, timestamp, and active status.

portable-vault.schema.json

Portable Vault

The .avault interchange format for transferring complete vaults (credentials + memories) between systems.

memory-portable.schema.json

Memory Portable

Memory-only portable format for exporting and importing agent memory without credentials.

bank-descriptor.schema.json

Bank Descriptor

Metadata for memory bank packages including name, description, entry count, tags, and preview entries.

license-descriptor.schema.json

License Descriptor

Access terms for purchased memory banks including access type, expiry, remaining accesses, and transaction hash.

mcp-response.schema.json

MCP Response

Standard response envelope for all MCP server tool calls with success/error variants and error codes.

Using the schemas

These JSON Schema files follow the Draft 2020-12 specification. You can use them with any JSON Schema validator to verify that your AVP implementation produces conformant data structures.