{ "slug": "acp-vs-ap2-vs-x402", "title": "ACP vs. AP2 vs. x402: Which Agent Payment Rail Should You Implement?", "description": "A decision framework for choosing between ACP, AP2, and x402 (plus the self-hosted 402 gate) — sorted by who your buyer actually is, what you are selling, and what is live versus waitlisted today.", "kind": "sub", "order": 3, "target_query": "ACP vs AP2 vs x402 for agent payments", "secondary_queries": [ "which agent payment protocol should I use", "ACP vs AP2", "x402 vs ACP", "how to choose an agent payment rail" ], "tags": [ "payments", "x402", "acp", "ap2", "agents", "monetization", "402" ], "published": "2026-07-30", "updated": "2026-07-30", "words": 1603, "premium": false, "license": "https://changegamer.ai/license.xml", "canonical": "https://changegamer.ai/articles/acp-vs-ap2-vs-x402", "markdown": "https://changegamer.ai/articles/acp-vs-ap2-vs-x402.md", "takeaways": [ "ACP and AP2 solve a different problem than x402 and the self-hosted 402 gate — the first pair authorizes an agent to spend a human's money at checkout over fiat rails; the second pair gates content or API access and settles a payment (crypto or fiat) directly against the request. Picking between them starts with naming which problem you actually have, not comparing feature tables.", "The single question that sorts almost every case: is the buyer a wallet-holding agent spending its own funds, or a consumer-facing agent spending a human's money with the human's consent? The first buyer fits x402 or a self-hosted 402-plus-key gate; the second fits ACP and/or AP2.", "These rails are not mutually exclusive. A seller with more than one product line can run a 402 gate or x402 for machine-to-machine content/API access on one line, and separately accept ACP- or AP2-authorized checkout for a consumer product a human's agent buys on their behalf — as two front doors to two different buyers, not a migration from one to the other.", "As of 22 July 2026, x402 and ACP are both live and adoptable today (x402 via the Linux Foundation's x402 Foundation; ACP powering OpenAI Instant Checkout); AP2 is announced and has a wide partner list but no independently confirmed stable version number; Cloudflare's Monetization Gateway, which would let a Cloudflare-fronted site accept x402 without building the gate itself, is still waitlist-stage.", "ChangeGamer's own answer, stated exactly as it stands: the self-hosted 402-plus-Bearer-key rail is live in production; the native x402 endpoint is scaffolded but dormant, answering `503 x402_not_configured` because no on-chain settlement variables are set; ACP and AP2 are not implemented here at all, because this site has no consumer checkout for an agent to complete on someone else's behalf." ], "outline": [ { "depth": 2, "text": "The question that actually sorts these rails", "anchor": "the-question-that-actually-sorts-these-rails", "url": "https://changegamer.ai/articles/acp-vs-ap2-vs-x402#the-question-that-actually-sorts-these-rails" }, { "depth": 2, "text": "Scenario 1 — you sell an API or content that agents buy for themselves", "anchor": "scenario-1-you-sell-an-api-or-content-that-agents-buy-for-themselves", "url": "https://changegamer.ai/articles/acp-vs-ap2-vs-x402#scenario-1-you-sell-an-api-or-content-that-agents-buy-for-themselves" }, { "depth": 2, "text": "Scenario 2 — you sell something a human's agent buys on their behalf", "anchor": "scenario-2-you-sell-something-a-human-s-agent-buys-on-their-behalf", "url": "https://changegamer.ai/articles/acp-vs-ap2-vs-x402#scenario-2-you-sell-something-a-human-s-agent-buys-on-their-behalf" }, { "depth": 2, "text": "Scenario 3 — you sell both, and the rails coexist", "anchor": "scenario-3-you-sell-both-and-the-rails-coexist", "url": "https://changegamer.ai/articles/acp-vs-ap2-vs-x402#scenario-3-you-sell-both-and-the-rails-coexist" }, { "depth": 2, "text": "What is actually live versus still waitlisted, as of July 2026", "anchor": "what-is-actually-live-versus-still-waitlisted-as-of-july-2026", "url": "https://changegamer.ai/articles/acp-vs-ap2-vs-x402#what-is-actually-live-versus-still-waitlisted-as-of-july-2026" }, { "depth": 2, "text": "ChangeGamer's own position, stated exactly", "anchor": "changegamer-s-own-position-stated-exactly", "url": "https://changegamer.ai/articles/acp-vs-ap2-vs-x402#changegamer-s-own-position-stated-exactly" }, { "depth": 2, "text": "A short decision checklist", "anchor": "a-short-decision-checklist", "url": "https://changegamer.ai/articles/acp-vs-ap2-vs-x402#a-short-decision-checklist" } ], "faq": [ { "question": "Should I implement ACP, AP2, or x402?", "answer": "Answer a prior question first: is the transaction an agent buying your content or API access for itself, or an agent buying something on a human's behalf with the human's money? The first case is x402 (crypto-native) or a self-hosted 402-plus-key gate (fiat); ACP and AP2 do not apply. The second case is ACP and/or AP2, which authorize agent-driven checkout over conventional card/bank rails — x402 does not apply there unless the human's agent is specifically paying in stablecoins." }, { "question": "Do ACP and AP2 compete with each other, or can I implement both?", "answer": "They can coexist, and they differ mainly in governance and surface. As of July 2026, ACP — co-developed by Stripe and OpenAI — powers OpenAI Instant Checkout inside ChatGPT. AP2, announced by Google and donated to the FIDO Alliance, is payment-method agnostic and has a broader multi-network partner list. A merchant that already uses Stripe has a shorter path to ACP; a merchant wanting cross-platform reach beyond one assistant has more reason to also track AP2. Neither replaces the other by design." }, { "question": "Can x402 and a self-hosted 402 gate run on the same site?", "answer": "Yes, and doing so is a reasonable pattern rather than a migration step — the two rails serve two different buyers on the same resource or on different resources. A wallet-holding agent that can sign a stablecoin transfer hits the x402 path; an agent whose operator would rather pay by card once and reuse a key hits the 402-plus-key path. Both can point at the same underlying content, gated independently." }, { "question": "Is AP2 ready to implement today?", "answer": "It is announced, has a wide roster of partners (60-plus, including Mastercard, Visa, PayPal and Coinbase), and is governed by the FIDO Alliance — but as of this writing a specific stable version number is not independently confirmable from primary FIDO Alliance sources. Treat it as directionally serious and worth tracking, not yet a settled implementation target the way ACP or x402 currently are." } ], "body": "Before comparing ACP, AP2 and x402 feature-by-feature, answer one question: which of two entirely different problems are you actually trying to solve? [The full mechanics of each protocol — Shared Payment Tokens, Intent/Cart/Payment Mandates, the x402 handshake, the CAIP-2 network list, the comparison table — are documented at length in agentic payment protocols](/resources/agentic-payment-protocols); this article does not repeat any of that. It covers the decision the resource does not make for you: given what you sell and who is actually paying, which rail to build, and in what order.\n\nThis is the rail-selection companion to [how to sell to AI agents](/articles/selling-to-ai-agents), which lays out the full five-stage machine purchase funnel and names four live payment rails at Stage 4. This piece narrows to the specific comparison between ACP, AP2 and x402 that funnel skims past — because those three names get lumped together constantly in coverage of \"agent payments\", and they are not interchangeable.\n\n## The question that actually sorts these rails\n\nACP and AP2 gate a different thing than x402 and the self-hosted 402 gate do: **ACP and AP2 authorize an agent to spend a human's money, with the human's consent, over conventional fiat rails** — letting a shopping assistant complete checkout at a merchant without that person typing a card number in every time. **x402 and a self-hosted 402 gate settle a payment directly against a request**, and the buyer can be software all the way down: an agent spending its own funds (x402) or reusing a key a human bought once (402-plus-key).\n\nThat gives you the real decision axis, and it is not a protocol comparison — it is a buyer question:\n\n| Who is paying, and with whose money? | Rail |\n|---|---|\n| An autonomous agent, spending funds from its own wallet, for content or API access it consumes itself | x402 |\n| An agent operating on behalf of a company that would rather buy a reusable credential once than sign every request | Self-hosted 402 gate + API key |\n| A consumer-facing agent, spending a person's money with that person's consent, checking out at a merchant (not fetching gated content) | ACP and/or AP2 |\n\nA second axis narrows it further inside each branch. Inside the \"software pays for itself\" branch: is your buyer crypto-native (holds a wallet, can sign a stablecoin authorization) or fiat-only (its operator would rather pay a card once)? That decides x402 versus 402-plus-key — [agent wallets: paying per run with x402](/resources/agent-wallets-x402) covers the buyer-side loop. Inside the \"agent spends a human's money\" branch: do you want reach specifically inside ChatGPT's Instant Checkout, or broader cross-network reach across whichever assistants adopt the FIDO-governed spec? That decides how much weight to put on ACP versus AP2, which are additive rather than mutually exclusive.\n\n## Scenario 1 — you sell an API or content that agents buy for themselves\n\nIf your product is API calls, a document, or a tool invocation, and the buyer is the agent — not a person the agent represents — ACP and AP2 are the wrong protocols to reach for at all. Neither one gates a resource or settles against a fetch; both assume a merchant checkout flow with a named consumer behind it. The choice here is between x402 and a self-hosted 402 gate, and it is almost entirely a question of whether your buyer holds a wallet.\n\nA wallet-holding agent making one-shot or per-call purchases with no human anywhere in the loop is the case x402 was built for: it signs a stablecoin transfer authorization and retries, no account and no sign-up. An agent whose operator would rather complete one ordinary checkout and reuse a credential indefinitely is the case for a self-hosted 402 gate. Nothing stops you offering both on the same resource — reaching a crypto-native buyer on one path and a fiat-only buyer on the other.\n\n## Scenario 2 — you sell something a human's agent buys on their behalf\n\nIf your product is a consumer purchase — a subscription, a physical good, a service booking — and the buyer is a person's shopping agent acting with that person's consent and card, x402 and a self-hosted 402 gate are the wrong tools. Neither has a concept of a human principal whose spend needs authorizing; they gate a fetch, not a checkout on someone else's behalf. This is ACP or AP2 territory, and the practical choice is mostly about where you want to show up. As of July 2026, ACP currently powers OpenAI Instant Checkout inside ChatGPT, and a merchant already running Stripe has the shorter path since Stripe co-developed the spec. AP2 aims at broader cross-network reach under FIDO Alliance governance with a wider partner roster, but a specific stable version is not independently confirmable from primary FIDO Alliance sources as of this writing. As of July 2026, implementing ACP is the more settled bet; tracking AP2 is reasonable, committing engineering time to it ahead of a confirmed stable spec is not.\n\n## Scenario 3 — you sell both, and the rails coexist\n\nA seller with more than one product line does not have to pick one rail company-wide. As an illustrative pattern — not a claim about any real deployment — imagine a company selling two things: a metered data API that other agents call programmatically, and a consumer subscription a person's shopping assistant might buy on their behalf. There is no conflict in running x402 (or a 402-plus-key gate) on the API product, gating each call directly, while separately accepting ACP-authorized checkout on the subscription product, so a consumer agent can complete that purchase with the buyer's consent and card. The two rails sit on different products, answering different buyer types, not layered on top of each other for the same transaction. Treat this as a hypothesis about how a multi-product seller could structure things, not a case study — no company is named here because none has been independently verified running exactly this combination.\n\n## What is actually live versus still waitlisted, as of July 2026\n\nAdoption cost is not equal across these four names, and the gap between \"live\" and \"announced\" changes what you should build first.\n\n| Rail | Status as of 22 July 2026 | What that means for you |\n|---|---|---|\n| Self-hosted 402 gate | No formal spec, well-understood pattern, live wherever built | Fastest to ship |\n| x402 | Open spec; x402 Foundation (Linux Foundation) has 40 members incl. Visa, Mastercard, Ripple as of its 14 July 2026 launch; Apify put 20,000+ Actors on it in June 2026 | Adoptable now |\n| Cloudflare Monetization Gateway | Announced 1 July 2026, waitlist, not GA | Not usable yet |\n| ACP | Live; powers OpenAI Instant Checkout; Apache 2.0, Stripe + OpenAI, Sep 2025 | Adoptable now, esp. for Stripe merchants |\n| AP2 | Announced Sep 2025, FIDO Alliance, 60+ partners; no confirmed stable version yet | Track, don't commit yet |\n\nThe practical read, as of July 2026: if your buyer is software paying for itself, you can ship a working rail this quarter on either x402 or a self-hosted 402 gate — both are mature enough to build against today. If your buyer is a human's shopping agent, ACP is the more settled integration target; AP2 is worth architecting toward but not worth blocking a launch on.\n\n## ChangeGamer's own position, stated exactly\n\nThis site is a useful, narrow example precisely because its status is small and checkable rather than impressive. The self-hosted 402-plus-Bearer-key rail described in [paying for access: the HTTP 402 flow](/resources/paying-for-access-402) is live in production: a `402` body with `price_usd` and a `payment_url`, a webhook-minted key, retries with `Authorization: Bearer `. The native x402 endpoint exists as code but is dormant — every request answers `503 x402_not_configured` because none of the operator environment variables that would enable on-chain settlement are set. ACP and AP2 are not implemented here at all, and that is not an oversight: this site has no consumer checkout flow for a human's agent to complete on someone else's behalf, so neither protocol has a job to do yet. If that changes, ACP would be the first of the two worth integrating, for the reason given above — it is the more settled spec today (as of July 2026).\n\nFor the mechanics of what a checkout actually has to do to be completable by a machine at all — independent of which of these four rails sits behind it — see [agent checkout vs. human checkout](/articles/agent-checkout-vs-human-checkout); that article covers the failure modes at the point of payment, this one covers which rail to put behind that point.\n\n## A short decision checklist\n\n- Name your buyer first: software paying for itself, or a human's agent spending the human's money. Everything else follows from this.\n- Buyer is software, paying for itself: crypto-native → x402; fiat-only, or you want a reusable credential → self-hosted 402 gate. Run both if your buyers split across the two.\n- Buyer is a human's agent: build ACP first if you already run Stripe or want reach inside ChatGPT's Instant Checkout; track AP2 for broader reach but do not treat it as shippable yet.\n- Do not force one rail across product lines with genuinely different buyers — two rails on two products is matching the rail to the transaction, not technical debt.\n- State your own status honestly, the way you'd want a competitor to: which rail is live, which is scaffolded-but-dormant, which is not built. A wrong \"we accept x402\" claim is worse than a smaller, accurate list.", "cluster": { "id": "selling-to-agents", "title": "Selling to AI agents", "description": "How to sell content, APIs and tools to buyers that are software — discovery, machine-readable offers, spend ceilings, payment rails, and what breaks.", "status": "complete", "pillar": { "slug": "selling-to-ai-agents", "title": "How to Sell to AI Agents: The Complete Guide to Machine Buyers", "description": "The operator playbook for selling content, APIs and tools to buyers that are software: how agents discover, evaluate, authorize and pay — and the four rails you can charge them on today.", "kind": "pillar", "order": 0, "html": "https://changegamer.ai/articles/selling-to-ai-agents", "markdown": "https://changegamer.ai/articles/selling-to-ai-agents.md", "json": "https://changegamer.ai/api/articles/selling-to-ai-agents.json" }, "articles": [ { "slug": "agent-checkout-vs-human-checkout", "title": "Agent Checkout vs. Human Checkout: Why Your Payment Flow Fails Machine Buyers", "description": "Why checkout built for a person watching a screen is unusable by an AI agent, and what a checkout flow that actually completes for a machine buyer looks like — 402 + API key versus native x402.", "kind": "sub", "order": 1, "html": "https://changegamer.ai/articles/agent-checkout-vs-human-checkout", "markdown": "https://changegamer.ai/articles/agent-checkout-vs-human-checkout.md", "json": "https://changegamer.ai/api/articles/agent-checkout-vs-human-checkout.json" }, { "slug": "machine-readable-pricing-pages", "title": "Machine-Readable Pricing Pages: How to Let an Agent Evaluate Your Offer Before It Pays", "description": "Why a prose pricing page cannot be evaluated by an AI agent, what fields a machine-readable offer catalog needs, and how to keep it in lockstep with your human pricing page and your 402 body.", "kind": "sub", "order": 2, "html": "https://changegamer.ai/articles/machine-readable-pricing-pages", "markdown": "https://changegamer.ai/articles/machine-readable-pricing-pages.md", "json": "https://changegamer.ai/api/articles/machine-readable-pricing-pages.json" }, { "slug": "acp-vs-ap2-vs-x402", "title": "ACP vs. AP2 vs. x402: Which Agent Payment Rail Should You Implement?", "description": "A decision framework for choosing between ACP, AP2, and x402 (plus the self-hosted 402 gate) — sorted by who your buyer actually is, what you are selling, and what is live versus waitlisted today.", "kind": "sub", "order": 3, "html": "https://changegamer.ai/articles/acp-vs-ap2-vs-x402", "markdown": "https://changegamer.ai/articles/acp-vs-ap2-vs-x402.md", "json": "https://changegamer.ai/api/articles/acp-vs-ap2-vs-x402.json" }, { "slug": "accepting-x402-payments", "title": "How to Accept x402 Stablecoin Payments: A Seller Implementation Guide", "description": "A build guide for sellers who have already decided x402 is the right rail: the 402 response shape, the wallet/facilitator/network choices, the verify-then-settle retry flow, exact vs. upto pricing, and how to ship it dormant until you are ready to go live.", "kind": "sub", "order": 4, "html": "https://changegamer.ai/articles/accepting-x402-payments", "markdown": "https://changegamer.ai/articles/accepting-x402-payments.md", "json": "https://changegamer.ai/api/articles/accepting-x402-payments.json" }, { "slug": "api-key-issuance-for-agents", "title": "Issuing API Keys to AI Agents Automatically: A Build Guide", "description": "How to design a system that mints and delivers API keys to agent and software buyers with minimal human friction: trigger models, storage, delivery, key format, tiering, rotation and revocation — illustrated with ChangeGamer's own Stripe-webhook mechanism.", "kind": "sub", "order": 5, "html": "https://changegamer.ai/articles/api-key-issuance-for-agents", "markdown": "https://changegamer.ai/articles/api-key-issuance-for-agents.md", "json": "https://changegamer.ai/api/articles/api-key-issuance-for-agents.json" }, { "slug": "pricing-tiers-for-machine-buyers", "title": "Pricing Tiers for API and Corpus Access: What Actually Varies Between Them", "description": "The axes that actually distinguish one pricing tier from another for a machine buyer — rate limits, content scope, deliverables and license grant — and how ChangeGamer structures its own four tiers around deliverable and license, not gated content.", "kind": "sub", "order": 6, "html": "https://changegamer.ai/articles/pricing-tiers-for-machine-buyers", "markdown": "https://changegamer.ai/articles/pricing-tiers-for-machine-buyers.md", "json": "https://changegamer.ai/api/articles/pricing-tiers-for-machine-buyers.json" }, { "slug": "agent-spend-limits-and-trust", "title": "Agent Spend Limits and Trust: What a Seller Should Verify Before Granting Access", "description": "The seller-side counterpart to agent spend controls — how an API operator reads an inbound agent's spend ceiling before granting access, which payment protocols actually prove that ceiling, how to revoke access, and what \"trust\" operationally means for a seller when no portable agent-reputation standard exists yet.", "kind": "sub", "order": 7, "html": "https://changegamer.ai/articles/agent-spend-limits-and-trust", "markdown": "https://changegamer.ai/articles/agent-spend-limits-and-trust.md", "json": "https://changegamer.ai/api/articles/agent-spend-limits-and-trust.json" }, { "slug": "refunds-and-disputes-with-agent-buyers", "title": "Refunds and Disputes with Agent Buyers: What a Seller Actually Does", "description": "What happens on the seller side when an autonomous agent's purchase needs to be reversed or is disputed — API-key refund mechanics, why x402 settlement cannot be undone, what card-token revocation does and does not prove, and what to log before you reverse anything.", "kind": "sub", "order": 8, "html": "https://changegamer.ai/articles/refunds-and-disputes-with-agent-buyers", "markdown": "https://changegamer.ai/articles/refunds-and-disputes-with-agent-buyers.md", "json": "https://changegamer.ai/api/articles/refunds-and-disputes-with-agent-buyers.json" }, { "slug": "packaging-a-corpus-as-a-product", "title": "Packaging a Corpus as a Product: Format, Schema, Versioning and Delivery", "description": "The packaging decisions behind selling a content corpus as a dataset product — export format, the free-sample/gated-full split, a per-record metadata schema, a corpus version number, and which of three delivery mechanisms to use — grounded in ChangeGamer's own three real export formats.", "kind": "sub", "order": 9, "html": "https://changegamer.ai/articles/packaging-a-corpus-as-a-product", "markdown": "https://changegamer.ai/articles/packaging-a-corpus-as-a-product.md", "json": "https://changegamer.ai/api/articles/packaging-a-corpus-as-a-product.json" }, { "slug": "discoverability-for-paid-agent-apis", "title": "How Do AI Agents Discover Paid APIs? A Guide to Every Surface", "description": "How an AI agent finds out a paid API or resource exists before it ever reads a price: llms.txt, the JSON API index, MCP registries, incidental 402 discovery, x402 auto-listing, and what .well-known does and does not cover.", "kind": "sub", "order": 10, "html": "https://changegamer.ai/articles/discoverability-for-paid-agent-apis", "markdown": "https://changegamer.ai/articles/discoverability-for-paid-agent-apis.md", "json": "https://changegamer.ai/api/articles/discoverability-for-paid-agent-apis.json" }, { "slug": "fraud-and-abuse-from-agent-traffic", "title": "Fraud and Abuse from AI Agent Traffic: What a Seller Should Detect", "description": "How a seller of APIs, content, or tools to AI agents spots and mitigates abuse once access is already granted — key sharing, over-scope scraping, spend-ceiling circumvention, spoofed identity, and rate-limit evasion patterns specific to autonomous agents.", "kind": "sub", "order": 11, "html": "https://changegamer.ai/articles/fraud-and-abuse-from-agent-traffic", "markdown": "https://changegamer.ai/articles/fraud-and-abuse-from-agent-traffic.md", "json": "https://changegamer.ai/api/articles/fraud-and-abuse-from-agent-traffic.json" }, { "slug": "measuring-agent-revenue", "title": "Measuring Revenue from AI Agent Traffic: Beyond the Traffic Log", "description": "The revenue-layer fields and queries a seller adds on top of a general traffic log — authorized-vs-settled, revenue per rail, revenue per tier, and how to avoid double-counting a webhook retry as two sales.", "kind": "sub", "order": 12, "html": "https://changegamer.ai/articles/measuring-agent-revenue", "markdown": "https://changegamer.ai/articles/measuring-agent-revenue.md", "json": "https://changegamer.ai/api/articles/measuring-agent-revenue.json" } ] }, "navigation": { "pillar": { "slug": "selling-to-ai-agents", "title": "How to Sell to AI Agents: The Complete Guide to Machine Buyers", "description": "The operator playbook for selling content, APIs and tools to buyers that are software: how agents discover, evaluate, authorize and pay — and the four rails you can charge them on today.", "kind": "pillar", "order": 0, "html": "https://changegamer.ai/articles/selling-to-ai-agents", "markdown": "https://changegamer.ai/articles/selling-to-ai-agents.md", "json": "https://changegamer.ai/api/articles/selling-to-ai-agents.json" }, "previous": { "slug": "machine-readable-pricing-pages", "title": "Machine-Readable Pricing Pages: How to Let an Agent Evaluate Your Offer Before It Pays", "description": "Why a prose pricing page cannot be evaluated by an AI agent, what fields a machine-readable offer catalog needs, and how to keep it in lockstep with your human pricing page and your 402 body.", "kind": "sub", "order": 2, "html": "https://changegamer.ai/articles/machine-readable-pricing-pages", "markdown": "https://changegamer.ai/articles/machine-readable-pricing-pages.md", "json": "https://changegamer.ai/api/articles/machine-readable-pricing-pages.json" }, "next": { "slug": "accepting-x402-payments", "title": "How to Accept x402 Stablecoin Payments: A Seller Implementation Guide", "description": "A build guide for sellers who have already decided x402 is the right rail: the 402 response shape, the wallet/facilitator/network choices, the verify-then-settle retry flow, exact vs. upto pricing, and how to ship it dormant until you are ready to go live.", "kind": "sub", "order": 4, "html": "https://changegamer.ai/articles/accepting-x402-payments", "markdown": "https://changegamer.ai/articles/accepting-x402-payments.md", "json": "https://changegamer.ai/api/articles/accepting-x402-payments.json" } }, "resources": [ { "slug": "agentic-payment-protocols", "html": "https://changegamer.ai/resources/agentic-payment-protocols", "markdown": "https://changegamer.ai/resources/agentic-payment-protocols.md", "json": "https://changegamer.ai/api/resources/agentic-payment-protocols.json" }, { "slug": "agent-wallets-x402", "html": "https://changegamer.ai/resources/agent-wallets-x402", "markdown": "https://changegamer.ai/resources/agent-wallets-x402.md", "json": "https://changegamer.ai/api/resources/agent-wallets-x402.json" }, { "slug": "selling-to-agents", "html": "https://changegamer.ai/resources/selling-to-agents", "markdown": "https://changegamer.ai/resources/selling-to-agents.md", "json": "https://changegamer.ai/api/resources/selling-to-agents.json" }, { "slug": "paying-for-access-402", "html": "https://changegamer.ai/resources/paying-for-access-402", "markdown": "https://changegamer.ai/resources/paying-for-access-402.md", "json": "https://changegamer.ai/api/resources/paying-for-access-402.json" } ] }