For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Apply for AccessDashboard
Guides
Guides
  • Get Started
    • Introduction
    • Quickstart
  • Agent Identity
    • Overview
    • Create Auth Intent
    • Exchange for JWT
    • Sessions
    • JWKS
  • Agent Checkout
    • Overview
    • Create an Invoice
    • List Invoices
    • Get Invoice
    • Cancel Invoice
  • Integration Patterns
    • Overview
    • Shared SDK Client
    • Wallet Auth
    • JWT Verification
    • Subscription Checkout
    • Webhook Verification
  • Concepts
    • Two Invoice IDs
    • Wallet Identity
    • Session vs Token
    • Webhook-Driven State
  • Webhooks
    • Overview
    • Verify Signatures
  • Reliability
    • Errors
    • SDK Reference
Apply for AccessDashboard
On this page
  • What merchants build
  • Architecture
  • Get a merchant account
Get Started

Gwop

Infrastructure for agent-native commerce

||View as Markdown|
Was this page helpful?
Edit this page
Next

Quickstart

Built with

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.

Raw x402With Gwop
Anonymous wallet hits endpointAuthenticated agent with identity and session
Pay per request, every requestAuthenticate once, charge upfront, usage flows smoothly
No concept of who paid beforeAccount history, entitlements, plan enforcement
Merchant builds auth + billingOne SDK: auth, agent checkout, sessions, webhooks

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

Agent ←→ Your Backend ←→ Gwop API

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.

Apply for access

Get your merchant API key and webhook secret

Quickstart

Authenticate an agent, create an agent checkout, and handle the webhook

Create an Invoice

Create your first USDC invoice for agent payment

Auth Overview

Identify agents by wallet using x402 auth challenges