Feature Request: Spraay x402 Payment Provider Integration

[plagtech]

Problem Statement

Feature Request: Spraay x402 Payment Provider Integration

Problem

Autonomous agents running in NemoClaw sandboxes currently have no native way to execute cryptocurrency payments. As agents become more autonomous — spawning sub-agents, accessing premium data, hiring robots — they need a payment rail. Without one, agents hit a wall every time a task requires spending money.

Proposed Solution

Integrate [Spraay](https://spraay.app) as a payment provider in NemoClaw, enabling OpenClaw agents to execute crypto payments via the [x402 protocol](https://www.x402.org) across 13 blockchains.

What is x402?

The x402 protocol makes payments native to HTTP. When an agent calls a paid API endpoint:

1. Server returns HTTP 402 Payment Required with payment details
2. Agent signs a USDC micropayment
3. Agent resends the request with payment proof in the header
4. Server verifies on-chain and executes the request

No wallet UX. No API keys for payment. Just pay-per-call with USDC.

What Spraay Provides

• 76+ paid gateway endpoints at gateway.spraay.app
• 13 blockchains: Base, Ethereum, Arbitrum, Polygon, BNB, Avalanche, Solana, Bitcoin, Stacks, Unichain, Plasma, BOB, Bittensor
• Categories: batch payments, escrow, payroll, token swaps, price oracles, NFT minting, bridging, staking, governance, analytics, AI inference proxy, wallet management, agent wallets, Robot Task Protocol (RTP), identity
• MCP Server: Published on Smithery as @plagtech/spraay-x402-mcp (60+ tools)

Integration Points

1. Network policy preset — Allow egress to gateway.spraay.app and required RPC providers within the NemoClaw sandbox
2. OpenClaw MCP tool — The Spraay MCP server can be added as an OpenClaw tool, giving the agent access to all 76+ endpoints
3. Agent wallet management — Spraay's Agent Wallet category (Category 17) provides managed wallets for autonomous agents, with session keys and spending limits

Network Policy

spraay_gateway:
  destination: "gateway.spraay.app"
  port: 443
  protocol: tcp
  action: allow
  note: "Spraay x402 payment gateway"

Alternatives Considered

• Manual wallet integration per chain — too complex for sandbox agents
• Coinbase Commerce — not designed for agent-to-agent micropayments
• Direct on-chain transactions — requires per-chain SDK integration and breaks sandbox isolation

Additional Context

• Spraay is already submitted as an [OpenShell Community sandbox](feat: add spraay sandbox — crypto payment layer for autonomous agents OpenShell-Community#50)
• Spraay is already submitted as a [NeMo Agent Toolkit example](feat: add spraay crypto payments agent example NeMo-Agent-Toolkit-Examples#20)
• The x402 protocol is supported by [Coinbase CDP](https://www.x402.org) as the payment facilitator
• Jensen Huang at GTC 2026: "Claude Code and OpenClaw have sparked the agent inflection point — extending AI beyond generation and reasoning into action." Agents that act need to pay.

Links

• Gateway: https://gateway.spraay.app
• Docs: https://docs.spraay.app
• MCP Server: https://smithery.ai/server/@plagtech/spraay-x402-mcp
• x402 Protocol: https://www.x402.org
• RTP Spec: https://github.com/plagtech/rtp-spec
• GitHub: https://github.com/plagtech

Proposed Design

Integrate Spraay as a payment provider in NemoClaw, enabling OpenClaw agents to execute crypto payments via the x402 protocol across 13 blockchains.

Integration Points

1. Network policy preset — Allow egress to gateway.spraay.app and required RPC providers within the NemoClaw sandbox
2. OpenClaw MCP tool — The Spraay MCP server (@plagtech/spraay-x402-mcp) can be added as an OpenClaw tool, giving the agent access to all 76+ endpoints
3. Agent wallet management — Spraay's Agent Wallet category provides managed wallets for autonomous agents, with session keys and spending limits

Network Policy

spraay_gateway:
  destination: "gateway.spraay.app"
  port: 443
  protocol: tcp
  action: allow
  note: "Spraay x402 payment gateway"

How x402 Works

1. Agent calls a paid endpoint
2. Server returns HTTP 402 with payment details
3. Agent signs a USDC micropayment
4. Agent resends request with payment proof
5. Server verifies on-chain and executes

Alternatives Considered

• Manual wallet integration per chain — too complex for sandbox agents
• Coinbase Commerce — not designed for agent-to-agent micropayments
• Direct on-chain transactions — requires per-chain SDK integration and breaks sandbox isolation

Category

enhancement: feature

Checklist

• I searched existing issues and this is not a duplicate
• This is a design proposal, not a "please build this" request

[plagtech]

Great breakdown. The three-phase pattern you're describing — payment_required → payment_approval → payment_receipt — maps cleanly onto what we've been building on the Spraay side.

Here's where we are today:

• Spraay's gateway already enforces session-key spending limits per agent wallet, which gives you the policy layer before gateway.spraay.app is called. The batch contract on Base handles the execution.

• What we don't yet surface in the gateway response is the operator principal — the authorized_by field and structured per-call receipts with correlation tracking. That's the gap you're identifying and it's the right one.

We're going to build this out. Concretely:

1. authorized_by as a required field in the gateway request — null = fail-closed, gateway rejects until an operator principal is resolved
2. correlation_id threading across the full lifecycle (required → approval → receipt) so operators get a complete audit trail
3. Structured payment_receipt in the gateway response bundling tx_hash, amount, chain, tool, authorized_by, and correlation_id

On your design question — I think the answer is both. Below a configurable threshold, agents should be autonomous (that's the session-key spending cap we already enforce). Above it, surface a checkpoint to the operator. The threshold should be operator-configurable, not hardcoded. A sandbox running sub-agents hiring robots needs different limits than a single agent making API calls.

Happy to coordinate on this if the NemoClaw team wants to align on the schema. The payment execution layer is live — this is about adding the accountability wrapper.

spraay.app | docs.spraay.app | gateway.spraay.app