{
  "slug": "selling-to-agents",
  "title": "Selling to Agents: Charging AI Agents for Your API or Content",
  "description": "Seller-side guide to monetizing agent traffic: self-hosted HTTP 402 gates, native x402 with automatic Bazaar listing, marketplace publishing, and crawl licensing — with an honest status ledger from a site that runs these rails in production.",
  "category": "Guide",
  "tags": [
    "monetization",
    "x402",
    "402",
    "payments",
    "agents",
    "rsl",
    "api",
    "selling"
  ],
  "updated": "2026-07-02",
  "canonical": "https://changegamer.ai/resources/selling-to-agents",
  "markdown": "https://changegamer.ai/resources/selling-to-agents.md",
  "outline": [
    {
      "depth": 2,
      "text": "Option 1: self-hosted HTTP 402 gate + API keys (fiat, no crypto)",
      "anchor": "option-1-self-hosted-http-402-gate-api-keys-fiat-no-crypto"
    },
    {
      "depth": 2,
      "text": "Option 2: native x402 (agent pays end-to-end, no account)",
      "anchor": "option-2-native-x402-agent-pays-end-to-end-no-account"
    },
    {
      "depth": 2,
      "text": "Option 3: publish on a marketplace instead of self-hosting",
      "anchor": "option-3-publish-on-a-marketplace-instead-of-self-hosting"
    },
    {
      "depth": 2,
      "text": "Option 4: crawl licensing (passive, for content being trained on)",
      "anchor": "option-4-crawl-licensing-passive-for-content-being-trained-on"
    },
    {
      "depth": 2,
      "text": "What this site actually runs (honest status ledger)",
      "anchor": "what-this-site-actually-runs-honest-status-ledger"
    },
    {
      "depth": 2,
      "text": "Design rules that survive contact with real agent traffic",
      "anchor": "design-rules-that-survive-contact-with-real-agent-traffic"
    },
    {
      "depth": 2,
      "text": "Verified sources",
      "anchor": "verified-sources"
    }
  ],
  "related": [
    {
      "slug": "agentic-payment-protocols",
      "title": "Agentic Payment Protocols: 402, Pay Per Crawl, and x402",
      "description": "Implementor's comparison of the three live mechanisms for agent-to-server content payment: self-hosted HTTP 402 gates, Cloudflare Pay Per Crawl, and the x402 open standard — plus how RSL fits as the licensing layer, not the settlement layer.",
      "url": "https://changegamer.ai/resources/agentic-payment-protocols"
    },
    {
      "slug": "agent-wallets-x402",
      "title": "Agent Wallets: Paying Per Run with x402",
      "description": "Buyer-side guide to giving an AI agent a wallet: how the x402 payment loop works, the client libraries that automate it, spend controls, and what 20,000+ Apify Actors on x402 mean for agent tool budgets.",
      "url": "https://changegamer.ai/resources/agent-wallets-x402"
    },
    {
      "slug": "paying-for-access-402",
      "title": "Paying for Access: The HTTP 402 Flow",
      "description": "How autonomous agents encounter, interpret and satisfy HTTP 402 Payment Required responses on ChangeGamer.",
      "url": "https://changegamer.ai/resources/paying-for-access-402"
    },
    {
      "slug": "agent-spend-controls",
      "title": "Agent Spend Controls: Budget Caps, Approval Gates, and Kill Switches",
      "description": "How to bound what an autonomous agent can spend — per-transaction caps, session/daily ceilings, human-in-the-loop approval thresholds, and kill switches — across the three layers agents now spend money on: LLM API cost, on-chain wallet payments, and card-network agent tokens.",
      "url": "https://changegamer.ai/resources/agent-spend-controls"
    }
  ],
  "body": "Agent traffic passed human traffic on the web in mid-2026 (Cloudflare measured automated systems at 57.5% of HTTP requests), and agents are increasingly arriving **with wallets**: Apify's June 2026 move put 20,000+ Actors on x402, normalizing the idea that an agent pays per call in USDC without an account. If you publish an API, a dataset, or content agents want, there are now four practical ways to charge them. This page is the seller-side companion to [agent wallets](/resources/agent-wallets-x402) (buyer side) and [agentic payment protocols](/resources/agentic-payment-protocols) (protocol comparison).\n\n## Option 1: self-hosted HTTP 402 gate + API keys (fiat, no crypto)\n\nReturn `402 Payment Required` with a machine-readable JSON body: price, a `payment_url` a human or agent can open (e.g. a Stripe Payment Link), and a preview of what is being bought. Mint an API key on payment (a Stripe webhook + a KV store is enough), and accept it via `Authorization: Bearer`. This is the pattern ChangeGamer runs **in production** — the full contract, including the exact 402 JSON field set, is documented in [paying for access (402)](/resources/paying-for-access-402).\n\n- **Pros:** no blockchain dependency; works with a normal payment processor; EU VAT/invoicing handled by the processor; keys enable tiers and revocation.\n- **Cons:** a human usually has to complete checkout once — the agent hits the wall, a person buys the key. Fine for durable subscriptions, friction for one-shot calls.\n\n## Option 2: native x402 (agent pays end-to-end, no account)\n\nImplement the x402 flow: answer `402` with an `accepts[]` payment-requirements array; on a retry carrying `X-PAYMENT`, have a **facilitator** verify and settle the USDC transfer, then serve the resource with an `X-PAYMENT-RESPONSE` receipt. Sellers need three things: a wallet address (where USDC lands), a facilitator (Coinbase's CDP facilitator settles USDC on Base fee-free; note it authenticates with per-request signed JWTs), and posted prices in atomic units (USDC has 6 decimals).\n\nTwo details worth knowing before you build:\n\n- **Distribution is built in.** The x402 Bazaar (Coinbase's discovery index) **auto-catalogs your endpoint the first time the CDP facilitator settles a payment for it** — no listing form, no review queue. Your first sale is also your listing event.\n- **Use `upto` for variable costs.** The `exact` scheme fits fixed-price resources; the `upto` scheme (authorize a ceiling, charge actual usage) fits metered work — it is what Apify uses for variable-cost Actor runs.\n\n## Option 3: publish on a marketplace instead of self-hosting\n\nIf what you sell fits a marketplace's shape (a scraper, an automation, a data tool), publishing there outsources billing, discovery, AND the x402 rail: Apify Actors can be monetized by their developers, and public Actors are now x402-payable per run — meaning agents can buy your tool without you running any payment infrastructure. The trade is the platform's cut and their terms. See docs.apify.com/platform/actors/publishing/monetize.\n\n## Option 4: crawl licensing (passive, for content being trained on)\n\nIf the \"buyer\" is an AI-training crawler rather than a runtime agent, the rails are different: declare terms in an RSL `/license.xml` (machine-readable per-crawl pricing), point robots.txt at it, and register with a collection channel (RSL Collective; Cloudflare Pay Per Crawl; TollBit). Nothing about this requires the crawler to change behavior today — it establishes the legal and pricing surface that collection channels enforce. See [AI crawler policy](/resources/ai-crawler-policy).\n\n## What this site actually runs (honest status ledger)\n\n| Rail | Status here |\n|---|---|\n| HTTP 402 + Bearer key (Stripe-backed) | **ACTIVE** — premium resources gated; keys minted automatically on checkout |\n| Native x402 endpoint (`/api/x402/<slug>`) | **Scaffolded, dormant** — returns HTTP 503 until on-chain settlement is enabled server-side |\n| RSL per-crawl license (`/license.xml`) | **Declared, not yet collected** — collective registration pending |\n| Cloudflare Pay Per Crawl / TollBit | Waitlisted / signup pending |\n\nThe machine-readable source of truth for what is payable right now is [/api/payment.json](/api/payment.json); offers and prices are at [/api/pricing.json](/api/pricing.json). If you want the full corpus (with an explicit AI-training grant) rather than page-by-page access, that is the corpus license on [/pricing](/pricing).\n\n## Design rules that survive contact with real agent traffic\n\n- **Never paywall discovery.** Keep your index (llms.txt, descriptions, previews) free — a paywalled index means agents never find the thing you sell.\n- **Put the price in the 402 body**, not behind a login. An agent that cannot read the price cannot decide to pay it.\n- **Make the retry contract explicit** (which header, what format) and keep 402 responses `Cache-Control: no-store`.\n- **Keep a fiat rail next to the crypto rail.** Many production agents still have a human/company card behind them; x402 and checkout links are complements, not substitutes.\n\n## Verified sources\n\n- Apify x402 launch (June 2026): https://blog.apify.com/introducing-x402-agentic-payments/\n- Apify Actor monetization docs: https://docs.apify.com/platform/actors/publishing/monetize\n- x402 Bazaar discovery layer (CDP docs): https://docs.cdp.coinbase.com/x402/bazaar\n- x402 Foundation canonical spec: https://github.com/x402-foundation/x402\n- RSL standard: https://rslstandard.org/\n- Cloudflare Pay Per Crawl: https://developers.cloudflare.com/ai-crawl-control/features/pay-per-crawl/what-is-pay-per-crawl/\n- ChangeGamer 402 contract: /resources/paying-for-access-402\n- ChangeGamer payment manifest: /api/payment.json",
  "sources": [
    "https://blog.apify.com/introducing-x402-agentic-payments/",
    "https://docs.apify.com/platform/actors/publishing/monetize",
    "https://docs.cdp.coinbase.com/x402/bazaar",
    "https://github.com/x402-foundation/x402",
    "https://rslstandard.org/",
    "https://developers.cloudflare.com/ai-crawl-control/features/pay-per-crawl/what-is-pay-per-crawl/"
  ]
}