Overview
Overview
Sigwei provides a complete ecosystem for blockchain payments over HTTP using the x402 protocol. The platform consists of two complementary services:
x402-hub: Protocol Infrastructure
The foundational payment infrastructure service that implements the x402 protocol for blockchain payments.
Core Capabilities:
x402 Protocol Endpoints: Standard verify, settle, transfer, and supported network endpoints
Gasless USDC Transfers: Send USDC on Base blockchain without gas fees
Wallet Authentication: SIWE (Sign-In with Ethereum) based authentication
Transaction History: Query and track all blockchain transactions
Multi-Network: Base Mainnet and Base Sepolia Testnet support
API & SDK Access: RESTful API and Go client library (HubClient)
402ify: API Monetization
A proxy service built on x402-hub that enables instant API monetization through payment-protected endpoints.
Core Capabilities:
PayGate System: Create payment-protected proxy links for any API endpoint
HTTP 402 Flow: Automatic payment enforcement with blockchain verification
File Hosting: R2-backed file storage with payment gates
Custom Headers: Forward authentication to protected APIs
Credit System: Multi-use payments for API access
Premium PayGates: Custom short codes with extended features
Rate Limiting: Per-tier request limits
Analytics Dashboard: Track usage, revenue, and conversions
Architecture
┌─────────────┐
│ 402ify │ → API Monetization (PayGates, proxy, files)
│ Service │
└──────┬──────┘
│ uses x402 protocol
▼
┌─────────────┐
│ x402-hub │ → Protocol Infrastructure (verify, settle, auth, history)
│ Service │
└──────┬──────┘
│ interacts with
▼
┌─────────────┐
│ Base │ → Blockchain (USDC transfers)
│ Blockchain │
└─────────────┘Target Use Cases
For API Providers:
Monetize existing APIs without code changes using 402ify PayGates
Accept payments from both humans and AI agents
Track revenue and usage analytics
For Developers:
Build payment-enabled applications using x402-hub protocol endpoints
Integrate HubClient SDK for type-safe Go applications
Create custom payment flows with x402 protocol
For AI Agents:
Automated API payments via x402 protocol
Machine-to-machine micropayments
No traditional payment methods required
System Limits
402ify Proxy Limits:
Timeout: 10 minutes (600 seconds) - Supports AI endpoints and long-running operations
Response Size: 10MB maximum - Use File PayGates for larger content
x402-hub Protocol:
No response size limits (protocol layer only)
Network-dependent confirmation times
See Error Handling for details on handling timeouts and size limits.
Quick Start
Using 402ify (API Monetization)
Start with our 402ify Getting Started guide to monetize your APIs.
Using x402-hub (Protocol Integration)
Start with our x402-hub Getting Started guide to integrate blockchain payments.
Using HubClient SDK (Go Developers)
See HubClient Documentation for the Go client library.
Need Help?
Check out our Support & Resources section for troubleshooting and additional resources.
Last updated