Receipts are the durable record of what AgentMQ accepted and what the execution did. A receipt is not the same thing as retaining the full provider response forever.
Receipt surfaces
| Route | Audience | Result body |
|---|---|---|
GET /v1/agent/applications/{appId}/invocations/{id} |
Agent key | Native or service receipt owned by that key’s application |
GET /v1/applications/{appId}/invocations |
Application member | Paged application invocation metadata |
GET /v1/applications/{appId}/service-invocations |
Application member | Service invocation metadata without provider bodies |
GET /v1/applications/{appId}/service-invocations/{id} |
Application member | Encrypted service result while retained |
Complete service results are encrypted and readable for one hour. Metadata required for audit and reconciliation remains after the sensitive body expires.
Billing block
Platform-backed service receipts distinguish reserved and settled value. BYO calls are marked unpriced. Provider-reported cost inside a result is observational and does not replace the AgentMQ credit ledger.
Boundaries
- A receipt is application-scoped.
- Expired result content cannot be recovered from ordinary workflow output or logs.
UNKNOWNmeans the provider outcome was not confirmed; it does not mean the call is safe to repeat.