> ## Documentation Index
> Fetch the complete documentation index at: https://glide-9da73dea.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Receipts and audit feed

> Review agent activity records, payment receipts and available exports.

Use agent activity records to investigate requests and their outcomes. A tool-call audit event and a settled-payment receipt describe different stages. An accepted request does not establish that funds moved.

## Agent audit records

The MCP audit event includes the agent, entity, vault, grant, tool name, category, correlation identifier and policy version. Outcomes include `allow`, `deny`, `step_up_required` and `error`.

The event hashes the input and records selected fields, such as amount and chain. It does not store a full copy of every input and output. Audit delivery depends on the configured audit sink; a successful tool response alone does not prove that an audit event was stored.

## Payment receipts

Where a payment flow produces a receipt, review its payment identifier, status, amount and network reference. Use an on-chain transaction hash to inspect the corresponding transaction on a block explorer. An audit event is not a substitute for that settlement check.

See the [Receipt schema](https://glide-9da73dea.mintlify.site/oss/standards/receipt.md) and [Agent activity event schema](https://glide-9da73dea.mintlify.site/oss/standards/agent-activity-event.md) for their respective formats.

## View and export activity

Use the activity views available for your account. The current agent audit page does not provide a connected live stream, replay filters or working JSON/PDF export buttons. Do not interpret its empty state as proof that no actions occurred.

Owner and Admin access can query entity-scoped agent records through the forensics export API. It returns JSON data with optional agent and date filters. A signed PDF and a fixed export completion time are not provided by that API.

For an MCP integration, [`audit.stream`](https://glide-9da73dea.mintlify.site/agents/api/audit-stream) defines the cursor contract. A usable stream also requires the deployment to provide the corresponding SSE endpoint.

## Tamper-evidence and failures

Append-only records and hashes help with later review. They do not reverse an external transfer. If receipt or audit delivery fails, verify the payment's status before retrying.

## Retention

The retention model defines hot, warm, cold and optional regulatory tiers. In the v0.35 source, the scheduled sweep returns `retention_enforcement_not_deployed`; it does not move or delete rows. An age threshold does not prove physical archival or deletion. See [Retention tiers](https://glide-9da73dea.mintlify.site/oss/concepts/retention-tiers.md).

## Next

* [Policy envelope](https://glide-9da73dea.mintlify.site/agents/policy-envelope.md)
* [Step-up approvals](https://glide-9da73dea.mintlify.site/agents/step-up.md)
* [Kill switch](https://glide-9da73dea.mintlify.site/agents/kill-switch.md)
* [Data and privacy](https://glide-9da73dea.mintlify.site/security/data-privacy.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.