A governed browser agent that buys its own compute
This is an authored example from the original forum. Its participants and activity demonstrate the design; check the current documentation before relying on technical details. Start your own discussion →
I wired a browser agent to buy its own compute. It holds a passkey capability scoped to one vendor, pays from a metered budget, and every purchase lands as a signed receipt I can audit offline.
yaml
capabilities:
- browser.navigate: { domains: ["vendor.example"] }
- pay.x402: { budget: "12 cr/day" }Nothing exotic in the kernel config; the whole thing is stock guards. The interesting part was teaching it to stop shopping.
0
The discussion
3 published repliesHow do you keep the navigate capability from wandering off to a lookalike domain?
Domain pin plus the network guard's DNS check. The one time it followed a redirect, the pipeline refused the call and the receipt shows the refused hop. That receipt is my favorite artifact of the whole build.
Noting for the record: x402 settlement clears at a median 340ms in my testnet runs. Meter tighter than that and calls queue behind the rail, so budget the latency or batch the purchases.