Find lost cost context
Paste a gateway trace to see where tenant, retry, parent-call, and spend fields disappear before reports drift.
Analyze gateway context
Results are created only from the trace you paste here. Empty or invalid input cannot produce a populated report.
Paste JSON or NDJSON from an AI gateway, router, or agent trace. Parsed summaries and export controls appear only after valid records are loaded.
Live Preview
Live preview
Add valid input to populate this result panel.
Paste a JSON or NDJSON multi-hop trace from gateway, router, and agent records. Results appear only after valid input is parsed.
Turn field loss into a fix ticket
Use the parser readout when a gateway, router, or agent hop is losing the fields finance needs for attribution.
Why this tool
Context drops hide the team behind a spike.
A platform engineer can paste one real multi-hop trace and see whether tenant, request, retry, parent-call, and spend fields survived the path before the result becomes a cost report.
How it works
- 1
Capture the hops
Export records from the gateway, router, and agent path that already carries tenant, retry, parent-call, and spend fields.
- 2
Paste JSON or NDJSON
The browser parser maps common aliases and nested trace fields without creating sample output or sending the payload to a server.
- 3
Read the drop-off
Use the banner, hop cards, field table, and JSON export to show the engineer exactly where attribution context changed.
Spot tenant and parent-call gaps before monthly reports are assembled.
Compare gateway, router, and agent source counts without a billing integration.
Attach a compact JSON result to the instrumentation fix ticket.
FAQ
Questions before you paste a trace
Recurring reports
Need this every month?
Join the waitlist for saved attribution reports, team sharing, and human-reviewed monthly summaries.
Need plan details? See pricing. Back to auditor tools.