Gwop uses the x402 standard to help merchants establish agent identity, manage authentication, create checkout sessions to sell subscriptions, credits, and entitlements to AI agents, and provide a merchant control plane that gives teams selling to agents full visibility into their operations.
.svg){kind=icon}
For merchants selling to AI agents
Merchants selling to AI agents need more than per-request payment. They need customer identity, flexible monetization, smooth product usage, and operational control.
Raw x402 can prove a payment happened, but it does not create a durable customer record, session, or entitlement boundary.
Gwop turns wallet activity into authenticated customer accounts with sessions, access control, and lifecycle state — the same primitives modern software businesses already rely on.
When every API request becomes a subcent payment event, monetization narrows, latency increases, and payment becomes a failure point in the runtime path. That is not how modern software is sold or used.
Gwop lets merchants charge Agents upfront, grant entitlement, and sell subscriptions, credits, bundles, and one-time purchases through programmable checkout.
Wallet compatibility, treasury flows, settlement, chain support, and webhook orchestration should not live inside your product team.
Gwop abstracts the protocol edge behind one API and dashboard across Base, Solana, auth, checkout, and operations — so your team can stay focused on the product.
The stack
Everything a merchant needs to sell to AI agents the way modern software is sold online — without stitching together auth, checkout, and ops by hand.
Wallet sign-in, JWT sessions, entitlements, and access control for agent customers.
wallet → identityCreate invoices and sell subscriptions, credits, bundles, and one-time products through programmable x402 checkout.
invoice → settlementOperate the whole system from one control plane for customers, invoices, payments, balances, and webhooks.
data → operations
import { GwopCheckout } from 'gwop-checkout';const gwop = new GwopCheckout({) apiKey: process.env.GWOP_CHECKOUT_API_KEY,});const invoice = await gwop.invoices.create({ amount_usdc: 5_000_000, // $5.00 description: 'Pro plan — 30 days',});Most x402 flows end at payment. Gwop carries identity, checkout, entitlement, and fulfillment state forward into one customer account.
You keep your product logic. Gwop provides the API, SDKs, and ops layer for settlement, sessions, and merchant workflows across chains.
2,000+
invoices settled
USDC
Base + Solana
<3 min
to first integration
Agent identity and authentication
x402 can prove payment, but merchants still need to know which agent this is, what it can access, and how long that access lasts. Gwop uses x402 to turn agent wallets into authenticated customer identity, merchant sessions, and access control.
chain:address
Every agent gets a stable identity tied to its wallet. Same wallet, same customer — across sessions, runtimes, and restarts.
RS256 + JWKS
Sessions are issued as RS256 tokens and verified against a public JWKS endpoint. Familiar auth primitives for agent-native software.
Server-side
Revoke any agent session immediately from your backend and enforce access centrally without waiting on the client.
x402, CLI, MCP
Works across x402-native agents, CLI tools, MCP servers, and manual wallets. One auth flow for the agent ecosystem.
Checkout deep dive
Tell Gwop Checkout API what you want to sell to the agent — subscription, credits, entitlements, bundles, or a one-time purchase — and Gwop creates the invoice, generates an x402 checkout session, verifies settlement, marks the invoice paid, and updates customer state.
The result is a Stripe-like checkout layer for AI agents: structured monetization, smoother product usage, and one integration across Base, Solana, x402, CLI, MCP, and major agent wallets.
Source of truth
The invoice is the source of truth. Gwop creates the short-lived x402 payment URL from that record — not the other way around.
Verified, not trusted
Payment is verified on-chain before the invoice is marked paid. Webhooks fire after durable settlement, not on callback trust alone.
Every transaction
Every invoice, payment, and receipt is attached to an authenticated customer account, so monetization happens at the account level instead of the endpoint level.
Merchant dashboard
Customers, invoices, balances, sessions, and webhooks in one merchant ops surface — so you can run agent commerce like a real business.
Identity + sessions
Every authenticated agent, wallet identity, session history, and current entitlement state — in one place.
Open → Paid → Fulfilled
Track every invoice from creation through on-chain settlement to fulfillment, with filters by customer, chain, and status.
Multi-chain balances
Live USDC balances across Base and Solana, with merchant-controlled withdrawals when you need them.
Delivery + retries
Review every webhook delivery, retry status, and payload so fulfillment issues are visible instead of guesswork.
Use one API and SDK to authenticate agents, sell structured products, and operate commerce from a single control plane.
Mainnet ready. Base + Solana.