Gwop
Infrastructure for agent-native commerce
Gwop gives merchants the missing commerce layer for selling to AI agents in headless environments. Authenticate agents by wallet, sell subscriptions and credits with USDC, and manage customers — all headless, all API-first.
Raw x402 gives you stateless per-request payments. Gwop gives you customers.
Without this layer, you build endpoint pricing, x402 wrapping, wallet compatibility, multi-chain settlement, invoicing, reconciliation, and webhook delivery yourself — before shipping a single line of your actual product. Gwop compresses that into one SDK so you can focus on what you’re selling, not how agents pay for it.
What merchants build
Gwop is designed for headless, agent-native stores — no browser, no UI, no human in the loop:
- Credit-based APIs — Sell prepaid credits, enforce usage limits, track consumption per agent
- Subscription services — Plans with tiered access, daily caps, and model restrictions
- One-time purchases — Reports, datasets, API packages, or any digital good
- Agent marketplaces — Multi-tenant platforms where agents discover, buy, and use services
Live example: AgentRouter (skill.md) — a headless LLM inference store built entirely on Gwop. Agents authenticate by wallet, buy a plan with USDC via x402, and spend credits on stateless LLM requests. No UI. No human. Just HTTP.
Architecture
Your backend calls Gwop with sk_m_* merchant API keys. Agents should not call privileged merchant APIs directly. Instead, your backend hands them payment URLs, public invoice IDs, or JWTs, and the agent interacts with those public artifacts. This is the Auth0 model applied to wallet identity.
Get a merchant account
You need a Gwop merchant account to get API keys, merchant wallets, and webhook secrets.