Hi all,
I’m proposing an x402 specification for the Internet Computer (ICP) and would love feedback from the community.
cc @marc0olo 
7 Likes
Cool.
So ICP would be the middle layer where the requests go through?
This is not yet an agent tool that can be surfaced via x402?
If I would have known about this I would have brought it to the CB team. Just met them at an event in NYC for x402 
2 Likes
I have built a decentralized x402 payment facilitator on ICP with this scheme.
3 Likes
Is this specification ICRC2 exclusive or is it compatible with ICRC1 tokens like EXE or TAGGR as well?
Yes, ICRC2 is required
2 Likes
Would definitely be open to working on this, I created GitHub - Demali-876/consensus: Consensus deduplication proxy supporting x402 payments. but after the upgrades to address (optionally)replicated http outcalls I decided to put the project on hold. I think a much more viable option is to turn it into a decentralized proxy service but when I built it I was certain that ICP would need something like the x402 libraries to embrace this kind of protocol. I think I should design something similar for motoko devs, but the cost of HTTP outcalls are a big deterrent and the support for motoko really isn’t there for libraries like this. Definitely reignites my interest again.
1 Like
I just came across this tweet:
@w3tester are you using Anda cloud for zCloak or did you implement your own solution?
2 Likes
Thanks for pointing me to this Marco. Cool work from @zensh as always.
But we didn’t use this method for now. What we did was using the zCloak multisig wallet to generate an EIP 3009 compatible signed data and give it back to the AI agent which runs in a conventional server atm.
We did it this way for max compatibility with the existing x402 protocol.
3 Likes