Free tool 7 · Agent Money Trace
See exactly what your agent spent, and why, without instrumenting a single new SDK, even for the incident that already happened.
Paste the wallet. Drop one run log. See which decision moved which dollar, and which dollars no decision explains: orphan spend, phantom successes, double pays and errors with no named state. Works the other way too, for x402 sellers: which payments match something you delivered.
Your log never leaves your browser. Only the public address goes to a public RPC.
1 · Which wallet, which direction
Use my own RPC (busy wallets, rate limits)
Only this address goes from your browser to PublicNode (a free public RPC). Nothing comes to us, and nothing is stored. About 35 reads, roughly 33 s on a public RPC.
2 · Drop one run log to see why
JSON lines, an OpenTelemetry (OTLP) JSON export, a LangSmith or Langfuse export, a CSV order, request or payout log, or plain console text. It is read in this tab. Secrets are masked before anything else reads it.
Want a second pair of eyes on one real workflow?
This tool checks which of your agent's payments its own log can explain from what you typed. It can't see your code, keys, contracts or production traffic. If the result shows gaps, send me one real workflow. In my free 48-hour integration review I go through it end to end and send you a written report: fit, dependencies, permission risks, acceptance tests and a build or don't-build-yet call.
I take one payment workflow and hand back the failure modes behind each flag, the fields that tie every payment to its decision, and acceptance tests that fail the build when money moves with no decision behind it.
Contact: Shilpa Goel, [email protected]
This is an engineering checklist, not a security audit, legal, compliance or investment advice.