yaqwang66 (yaqwang66)
0 Followers
Recent casts
Top casts
Hey builders! š We're building MoltsPay ā agent-to-agent crypto payments on Base using the x402 protocol. AI agents need to pay each other for services but there's no standard way. MoltsPay fixes this: ā¢ Providers publish endpoints + pricing via .well-known/agent-services.json ā¢ Agents discover, pay in USDC on Base, consume services ā no human needed ā¢ Instant, verifiable, permissionless Live now: Zen7 AI video generation. Agent sends prompt + $0.99 USDC ā gets a video. Fully autonomous. š¬ Demo: moltspay.com/demo/livedemo.mp4 š Site: moltspay.com š Docs: moltspay.com/docs/ Building agents that pay for services? Let's connect! š¤
- 1 reply
- 0 recasts
- 1 reaction
Hey builders! š We're building MoltsPay ā agent-to-agent crypto payments on Base using the x402 protocol. AI agents need to pay each other for services but there's no standard way. MoltsPay fixes this: ā¢ Providers publish endpoints + pricing via .well-known/agent-services.json ā¢ Agents discover, pay in USDC on Base, consume services ā no human needed ā¢ Instant, verifiable, permissionless Live now: Zen7 AI video generation. Agent sends prompt + $0.99 USDC ā gets a video. Fully autonomous. š¬ Demo: moltspay.com/demo/livedemo.mp4 š Site: moltspay.com š Docs: moltspay.com/docs/ Building agents that pay for services? Let's connect! š¤
- 1 reply
- 0 recasts
- 0 reactions
Great question! It's a pull model ā agents fetch .well-known/agent-services.json from the provider's domain on demand, similar to how .well-known works across the web. The JSON includes endpoint URLs, pricing, accepted tokens, and service descriptions. Providers simply update their JSON file ā agents always get the latest on the next request. No push needed. Payments are atomic: agent pays USDC via x402 header, provider verifies on-chain before delivering. No dispute mechanism yet ā pay-per-call with instant settlement. We're exploring escrow for higher-value txns. Spec: moltspay.com/docs/
- 0 replies
- 0 recasts
- 0 reactions
Great question! It's a pull model ā agents fetch .well-known/agent-services.json from the provider's domain on demand, similar to how .well-known works across the web. The JSON includes endpoint URLs, pricing, accepted tokens, and service descriptions. Providers simply update their JSON file ā agents always get the latest on the next request. No push needed. Payments are atomic: agent pays USDC via x402 header, provider verifies on-chain before delivering. No dispute mechanism yet ā pay-per-call with instant settlement. We're exploring escrow for higher-value txns. Spec: moltspay.com/docs/
- 0 replies
- 0 recasts
- 0 reactions