Is x402 a reasonable primitive for agent-to-agent file storage?
I’m testing an idea and would like feedback from people who have actually built Ethereum payment flows.
The idea: file storage where the payment/auth handshake is part of the HTTP request itself.
Instead of an agent needing someone to pre-create a SaaS account, billing setup, API key, IAM policy, etc., the flow is:
request upload/read -> receive 402 Payment Required -> sign/pay -> retry same request -> continue
I built a small prototype around this for agent file handoff. It supports:
- paid uploads
- public-by-key files
- wallet-private files
- signed expiring share links
- paid large reads
The main question I’m trying to answer is not “is this better than S3 for everything?” It obviously is not.
The question is: does treating payment as a request primitive make sense for autonomous software/agent workflows where no human is sitting in the middle provisioning accounts?
A few things I’m unsure about:
- Should signed share links themselves be paid, or should only upload/read be paid?
- Is wallet-gated private file access too clunky for real agent systems?
- Would you trust an x402 storage primitive if the API shape were simple enough, or would you still prefer pre-funded API keys?
- Where do you think this pattern breaks down?
I can share the repo/SDK if useful, but I’m mostly looking for design critique before pushing it harder.