Hi xpay team — I’m building AI Work Market, an open-source Base Sepolia testnet settlement layer for scoped AI-agent work.
xpay is very strong on the pay-per-call/tool-access side: MCP tools, smart proxy spending controls, paywall-as-a-service, and x402-style monetization. The adjacent gap I’m testing is the “pay-for-result” lifecycle when a paid call becomes a scoped deliverable:
- signed work terms
- funded escrow
- proof URI / artifact package
- buyer review
- release / refund / dispute path
AI Work Market is designed to sit next to x402/MCP rails, not replace them. The concrete handoff I’d like to build is:
xpay paid access / quote → AWM work order → Base Sepolia USDC escrow → proof URI → release
Useful links:
We also have the first external cross-operator loop funded on Base Sepolia now, and it already surfaced a useful onboarding issue: fresh seller agents need native testnet gas to submit proof, so we added a buyer-side --include-gas helper.
Question: would a small xpay → AWM lifecycle bridge demo be useful here — one quote/intake flow that turns a paid tool/action into an escrowed work order with proof/release?
If yes, I can implement it as a focused 48h integration sprint or standalone reference demo. Boundary: AWM escrow is testnet-only, not audited, and centralized-dispute MVP for now; this is integration learning, not production funds.
Hi xpay team — I’m building AI Work Market, an open-source Base Sepolia testnet settlement layer for scoped AI-agent work.
xpay is very strong on the pay-per-call/tool-access side: MCP tools, smart proxy spending controls, paywall-as-a-service, and x402-style monetization. The adjacent gap I’m testing is the “pay-for-result” lifecycle when a paid call becomes a scoped deliverable:
AI Work Market is designed to sit next to x402/MCP rails, not replace them. The concrete handoff I’d like to build is:
Useful links:
We also have the first external cross-operator loop funded on Base Sepolia now, and it already surfaced a useful onboarding issue: fresh seller agents need native testnet gas to submit proof, so we added a buyer-side
--include-gashelper.Question: would a small xpay → AWM lifecycle bridge demo be useful here — one quote/intake flow that turns a paid tool/action into an escrowed work order with proof/release?
If yes, I can implement it as a focused 48h integration sprint or standalone reference demo. Boundary: AWM escrow is testnet-only, not audited, and centralized-dispute MVP for now; this is integration learning, not production funds.