[{"data":1,"prerenderedAt":215},["ShallowReactive",2],{"blog:\u002Fblog\u002Fagent-spend-observability":3},{"id":4,"title":5,"body":6,"date":201,"description":202,"extension":203,"keywords":204,"meta":205,"navigation":206,"path":207,"readingMinutes":208,"seo":209,"stem":210,"tags":211,"__hash__":214},"blog\u002Fblog\u002Fagent-spend-observability.md","Non-custodial spend tracking for AI agents",{"type":7,"value":8,"toc":193},"minimark",[9,23,28,41,81,89,93,96,127,130,134,141,151,155,162,182,185],[10,11,12,13,17,18,22],"p",{},"The first time a fleet of agents runs up a real bill, most teams reach for the obvious tool: the\nwallet. And the wallet lets them down. It shows a flat list of outgoing transfers — amounts and\ntimestamps — with no answer to the only questions that matter: ",[14,15,16],"em",{},"which agent paid, for what, and\nwas it worth it?"," That gap is what ",[19,20,21],"strong",{},"agent spend observability"," exists to close.",[24,25,27],"h2",{"id":26},"why-a-wallet-isnt-enough","Why a wallet isn't enough",[10,29,30,31,34,35,40],{},"A blockchain wallet is a ledger of value moving, not a record of ",[14,32,33],{},"why",". For ",[36,37,39],"a",{"href":38},"\u002Fblog\u002Fhow-ai-agents-pay","agentic\npayments"," it's missing almost everything you'd want:",[42,43,44,52,59,70],"ul",{},[45,46,47,48,51],"li",{},"No mapping from a payment to the ",[19,49,50],{},"agent"," that made it.",[45,53,54,55,58],{},"No mapping to the ",[19,56,57],{},"domain or resource"," it paid for.",[45,60,61,62,65,66,69],{},"No sense of how many ",[19,63,64],{},"paywalls were hit"," versus actually ",[19,67,68],{},"paid",".",[45,71,72,73,76,77,80],{},"No ",[19,74,75],{},"latency"," or ",[19,78,79],{},"failure"," context — you can't tell a healthy payment from a broken one.",[10,82,83,84,88],{},"You can reconstruct some of this by hand for a few transactions. You cannot do it across a fleet\nof agents making thousands of ",[36,85,87],{"href":86},"\u002Fblog\u002Fwhat-is-x402","x402"," payments a day.",[24,90,92],{"id":91},"what-observability-actually-means-here","What observability actually means here",[10,94,95],{},"Good agent spend observability turns that flat ledger into an operational picture:",[42,97,98,104,110,116],{},[45,99,100,103],{},[19,101,102],{},"Spend over time",", broken down per agent and per destination domain — so you know where the\nmoney goes, not just that it left.",[45,105,106,109],{},[19,107,108],{},"Paywalls hit vs. payments made",", a ratio a wallet can never show you, which tells you how\noften your agents are running into priced resources.",[45,111,112,115],{},[19,113,114],{},"Per-resource detail"," — which endpoints cost the most, which agent is the heavy spender.",[45,117,118,121,122,126],{},[19,119,120],{},"Reliability signals"," — latency, error rates, and the ",[36,123,125],{"href":124},"\u002Fblog\u002Fdebugging-x402-payments","paid-but-failed\ncases"," sellers never surface to the buyer.",[10,128,129],{},"The point is to move from \"we spent $412 this week\" to \"agent A spent 60% of that hammering one\ndomain's premium endpoint, and 8% of those payments failed\" — the difference between a number and\na decision.",[24,131,133],{"id":132},"why-it-must-be-non-custodial","Why it must be non-custodial",[10,135,136,137,140],{},"There's a tempting shortcut: route agent payments ",[14,138,139],{},"through"," a service that holds the funds and\ntherefore sees everything. Don't. The moment a third party takes custody of your agents' money,\nyou've added the single largest risk in the system — funds that can be frozen, lost, or misused\nby someone other than you.",[10,142,143,146,147,150],{},[19,144,145],{},"Non-custodial"," observability watches the payment traffic without ever holding the money. It\n",[14,148,149],{},"observes"," the 402 challenges your agents hit and the payments they make from their own wallets;\nit never signs, holds, or settles funds. You get the full picture and keep sole control of the\nvalue. Visibility and custody are separable — and they should be separated.",[24,152,154],{"id":153},"from-observability-to-governance","From observability to governance",[10,156,157,158,161],{},"Seeing spend is step one. The reason to see it is to ",[19,159,160],{},"govern"," it:",[42,163,164,170,176],{},[45,165,166,169],{},[19,167,168],{},"Alerts"," when spend crosses a threshold, or when a spike suggests a looping agent.",[45,171,172,175],{},[19,173,174],{},"Failure alerts"," when payments start going through but resources still don't.",[45,177,178,181],{},[19,179,180],{},"Per-agent attribution"," so you can throttle or investigate a single misbehaving agent.",[10,183,184],{},"That's the arc: observe, understand, control — without ever taking custody of a cent.",[10,186,187,188,192],{},"402.report is the independent, non-custodial control plane for the buy side of x402: spend\ntracking, payment forensics, and alerts for teams running autonomous agents.\n",[36,189,191],{"href":190},"\u002F#waitlist","Join the waitlist"," to see what your agents pay before the bill does the talking.",{"title":194,"searchDepth":195,"depth":195,"links":196},"",2,[197,198,199,200],{"id":26,"depth":195,"text":27},{"id":91,"depth":195,"text":92},{"id":132,"depth":195,"text":133},{"id":153,"depth":195,"text":154},"2026-06-27","A wallet's transaction history is a flat list of transfers — useless for understanding what your AI agents actually pay for. Here's what agent spend observability looks like, and why it should be non-custodial.","md","AI agent spend tracking, agent payment observability, non-custodial agent payments, agent spend governance, agent cost monitoring, x402 dashboard",{},true,"\u002Fblog\u002Fagent-spend-observability",5,{"title":5,"description":202},"blog\u002Fagent-spend-observability",[212,213],"observability","governance","J3g4xjoeDQUjTdIt5mWm4OKR889iGhLAtUvfv90UzSE",1784841653226]