Gwop | Gwop Docs

Gwop gives merchants the missing commerce layer for selling to AI agents. 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.

Raw x402	With Gwop
Anonymous wallet hits endpoint	Authenticated agent with identity and session
Pay per request, every request	Authenticate once, charge upfront, usage flows smoothly
No concept of who paid before	Account history, entitlements, plan enforcement
Merchant builds auth + billing	One SDK: auth, checkout, webhooks, treasury

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

Agent ←→ Your Backend ←→ Gwop API

Your backend calls Gwop with sk_m_* merchant API keys. Agents never talk to Gwop directly — your backend hands them payment URLs, invoice IDs, or JWTs. 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.

Apply for access

Get your merchant API key and webhook secret

SDK Quickstart

Install the SDK, create an invoice, authenticate an agent, and handle webhooks

Create an Invoice

Create your first USDC invoice for agent payment

Auth Overview

Identify agents by wallet using x402 auth challenges