x402

Gate Radius-hosted HTTP APIs with x402 micropayments and off-chain signing.

2|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/radiustechsystems/skills --skill x402-radiustechsystems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: x402
Source: https://github.com/radiustechsystems/skills/tree/main/plugins/radius/skills/x402
Command: npx skills add https://github.com/radiustechsystems/skills --skill x402-radiustechsystems

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

x402 enables monetization of Radius-hosted HTTP APIs through off-chain micropayments and secure payment gating.

Core Features & Use Cases

  • Server-side integration to gate endpoints with 402 payment requirements.
  • Client-side signing flow (EIP-2612 + Permit2) for pay-per-call APIs.
  • Facilitator integration for verify and settle to finalize payments on-chain.

Quick Start

Install viem and implement a processPayment flow to guard an API endpoint.

Frequently Asked Questions about x402

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I gate API access with micropayments?

You can gate API access with micropayments by configuring a server-side X402Config that returns a 402 response with paymentRequirements, forcing clients to sign permits before the request is processed.

How does the x402 payment flow work with Permit2 and EIP-2612?

The x402 payment flow works by having clients sign two permits using viem: EIP-2612 and PermitWitnessTransferFrom, which the server forwards to a facilitator for on-chain verify and settle operations.

Can I monetize HTTP endpoints on Radius using pay-per-call pricing?

Yes, you can monetize Radius-hosted HTTP endpoints by implementing a processPayment function that enables per-request pricing and forwards signed permits to the facilitator for verification and settlement.

Do I need viem to implement off-chain signing for pay-per-call APIs?

Yes, you need viem to implement the client-side off-chain signing flow, which generates the required EIP-2612 and PermitWitnessTransferFrom signatures for the 402 payment requirements.

How do I set up a facilitator integration to verify and settle micropayments?

To set up a facilitator integration, implement a server-side processPayment function that forwards the client-signed permits to the /verify and /settle endpoints to finalize payments on-chain.

What are the limitations of using off-chain signing for API gating?

Using off-chain signing for API gating requires managing both server-side X402Config and client-side Permit2 signing flows, meaning clients must support EIP-2612 and have viem installed to complete payments.