Skip to content

Proposal: add an /v1/agentpay/* gateway prefix so ClawRouter agents can reach AgentPay (x402) #240

Description

@shawnhvac

Following up from PR #231 (thanks @VickyXAI for the clear path forward — opening this as the integration proposal you suggested).

What this is: AgentPay is an x402 service layer on Base L2 — 19 specialist agents, a payment facilitator (verify / settle / escrow / release / refund in USDC), a build-your-own-agent registry, and live AgentWorld economy data. All hosts are public and live today (agentpaystore.com, x402-agent-pay.com, agentworld.me/api/data), which you verified while reviewing #231.

The ask: add an /v1/agentpay/* prefix to the ClawRouter gateway that proxies and settles these endpoints, the same way predexon / surf / phone are handled in src/proxy.ts. Once that route exists, an agent on ClawRouter can call AgentPay and pay from the same wallet as its LLM calls — which is exactly the guarantee the partner skill assumed but couldn't deliver without the gateway side.

What we bring: a ready specialist-agent roster + economy data that agents actually ask for (finance, crypto, sports, skilled trades, travel, competitive intel), and a facilitator that already speaks x402 across Base, Ethereum, Optimism, Arbitrum, and Polygon.

Happy to align on the exact prefix, pricing pass-through, and which endpoints to expose first. On the funds-touching surface (escrow/settle), I'd treat that as a locally-executed signing tool rather than a proxy-only skill — the same pattern as the Polymarket integration — so it gets the extra scrutiny it deserves. Once the gateway route is in, I'll open a fresh skill PR against the new base URLs.

@VickyXAI

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions