A paid tool call should leave enough evidence to explain why it was made, what was submitted and what result was obtained. A response ID alone may not answer a later billing or debugging question.
Quick answer: Record the selected product and operation, authorization scope, relevant input reference, cost basis, attempt identifiers and observed result. Capture actual usage where available, distinguish estimates from final charges and exclude credentials or unnecessary sensitive content.
Connect the action to its purpose
For an illustrative document conversion, preserve which document version was intended and where the result should go. If the wrong file is converted, a successful response does not establish task success.
An access token should not appear in the record. Use appropriately protected references to sensitive inputs rather than copying their full contents into a general log.
Design the receipt
| Record | Question answered |
|---|---|
| Task and scope | Why was the operation permitted? |
| Product and operation | Which service was used? |
| Input reference | What exact artifact was submitted? |
| Attempt and status | What was tried and what happened? |
| Usage or charge reference | What cost evidence is available? |
| Result reference | What did the user actually receive? |
The receipt is a proposed design. It does not claim that every provider returns itemized final billing in its response.
Preserve estimates honestly
A pre-call estimate and a settled invoice measure different stages. Store the label and source of each. If the provider exposes usage later, reconcile it without rewriting the original decision record.
Keep retries distinct, including a retry that eventually succeeds. One completed task can involve several charged attempts depending on the product's policy.
Use the record for a decision
A good receipt supports troubleshooting, explaining usage or choosing whether another attempt is appropriate. Do not collect fields merely because they are available.
I'm Shashank Agarwal, creator of API.market and founder and CEO of Noveum AI. See API.market setup, the retry-reporting guide and tool-boundary evidence for the surrounding workflow.
Follow my work on LinkedIn. Drafted with AI assistance.
Top comments (0)