{ "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, "target_query": "how sellers handle refunds and disputes from AI agent buyers", "secondary_queries": [ "refunds for automated agent purchases", "can an x402 payment be reversed", "disputing a purchase an AI agent made", "chargeback on an AI agent card token" ], "tags": [ "refunds", "disputes", "chargebacks", "payments", "x402", "agents", "monetization" ], "published": "2026-08-03", "updated": "2026-08-03", "words": 1508, "premium": false, "license": "https://changegamer.ai/license.xml", "canonical": "https://changegamer.ai/articles/refunds-and-disputes-with-agent-buyers", "markdown": "https://changegamer.ai/articles/refunds-and-disputes-with-agent-buyers.md", "takeaways": [ "A one-time digital purchase and a subscription behave differently under EU withdrawal rules once delivery has happened: ChangeGamer's own tiers state that the 14-day right of withdrawal lapses on delivery of the digital deliverable, so a refund is realistically only available if the key or corpus file was never actually delivered — not because the buyer changed its mind after receiving it.", "Cancelling ChangeGamer's annual Corpus Updates subscription through the Stripe customer portal stops future renewals; it does not, by itself, refund the period already paid for — a refund on the current period is only offered if no corpus file was delivered during it.", "A settled x402 stablecoin payment has no documented reversal mechanism in this corpus: Apify's deposit-and-refund pattern for its `upto` scheme returns unused funds before final settlement on a variable-cost run, which is a different thing from undoing a payment that has already settled on-chain.", "Visa and Mastercard both document revoking an agent's tokenized card credential — a seller- or issuer-triggered kill switch — but neither the corpus nor a source verified this session documents that ordinary cardholder chargeback rights literally apply to a transaction made through an agent token; treat that continuity as a reasonable inference from normal card-rail behavior, not a confirmed policy.", "AP2 Intent/Cart/Payment Mandates and ACP Shared Payment Tokens prove that a purchase was authorized up to a signed ceiling at the moment it was made — neither protocol's documentation in this corpus describes a real dispute case or an issuer liability rule for what happens when a human principal later claims their agent exceeded that authorization.", "A seller's dispute runbook should separate three different questions before reversing anything: was the deliverable actually sent, was the payment actually settled or only authorized, and does the authorization on file (mandate, token, or subscription record) actually cover what was charged." ], "outline": [ { "depth": 2, "text": "What \"refund\" means once the deliverable already shipped", "anchor": "what-refund-means-once-the-deliverable-already-shipped", "url": "https://changegamer.ai/articles/refunds-and-disputes-with-agent-buyers#what-refund-means-once-the-deliverable-already-shipped" }, { "depth": 2, "text": "Cancelling a subscription is not the same as refunding it", "anchor": "cancelling-a-subscription-is-not-the-same-as-refunding-it", "url": "https://changegamer.ai/articles/refunds-and-disputes-with-agent-buyers#cancelling-a-subscription-is-not-the-same-as-refunding-it" }, { "depth": 2, "text": "Settlement finality: why an x402 payment cannot just be undone", "anchor": "settlement-finality-why-an-x402-payment-cannot-just-be-undone", "url": "https://changegamer.ai/articles/refunds-and-disputes-with-agent-buyers#settlement-finality-why-an-x402-payment-cannot-just-be-undone" }, { "depth": 2, "text": "Card-network agent tokens: a kill switch, not a documented dispute right", "anchor": "card-network-agent-tokens-a-kill-switch-not-a-documented-dispute-right", "url": "https://changegamer.ai/articles/refunds-and-disputes-with-agent-buyers#card-network-agent-tokens-a-kill-switch-not-a-documented-dispute-right" }, { "depth": 2, "text": "AP2 and ACP mandates: proof of authorization, not a resolved dispute mechanism", "anchor": "ap2-and-acp-mandates-proof-of-authorization-not-a-resolved-dispute-mechanism", "url": "https://changegamer.ai/articles/refunds-and-disputes-with-agent-buyers#ap2-and-acp-mandates-proof-of-authorization-not-a-resolved-dispute-mechanism" }, { "depth": 2, "text": "What to log and check before reversing anything", "anchor": "what-to-log-and-check-before-reversing-anything", "url": "https://changegamer.ai/articles/refunds-and-disputes-with-agent-buyers#what-to-log-and-check-before-reversing-anything" }, { "depth": 2, "text": "When to route it to a human", "anchor": "when-to-route-it-to-a-human", "url": "https://changegamer.ai/articles/refunds-and-disputes-with-agent-buyers#when-to-route-it-to-a-human" } ], "faq": [ { "question": "Can I get a refund for a purchase an AI agent made automatically on ChangeGamer?", "answer": "Only if the deliverable was never actually sent. ChangeGamer's paid tiers are mostly one-time purchases, and the EU 14-day right of withdrawal on a digital service lapses once delivery happens — the buyer (or its agent) consents to immediate delivery when checking out, per the withdrawal terms in [access and pricing for crawlers](/resources/access-and-pricing). Practically, that means a refund request only has a real answer if the key never got issued or the emailed corpus file never arrived — not because the content, once delivered, turned out not to be wanted. Reply to the Stripe receipt email to raise the request; there is no separate agent-facing refund endpoint." }, { "question": "Does cancelling the Corpus Updates annual subscription refund my last payment?", "answer": "No. Cancelling through the Stripe customer portal before the next billing date stops future renewals — it does not reverse the period you already paid for. [Access and pricing](/resources/access-and-pricing) states a refund on the current period is available only if no corpus file was delivered during it; if the file already went out, cancellation just means you will not be billed or re-sent a corpus file at the next renewal." }, { "question": "Can a settled x402 stablecoin payment be reversed after the fact?", "answer": "No mechanism for that is documented in this corpus. [Agentic payment protocols](/resources/agentic-payment-protocols) and [agent wallets and x402](/resources/agent-wallets-x402) describe a verify-then-settle flow with on-chain finality, plus a deposit-and-refund pattern Apify uses for its `upto` scheme — but that pattern returns unused authorization on a variable-cost run before final settlement, not after. Do not assume a refund path exists on the seller side once an x402 payment has settled; treat it as final and build your dispute process around preventing bad settlements, not undoing them." }, { "question": "If an agent's card token made a purchase I want to dispute, do normal chargeback rights apply?", "answer": "Not independently confirmed either way in the corpus this article draws from. What is documented is that Visa and Mastercard both let an issuer or network revoke an agent's tokenized credential without touching the underlying card — a kill switch, not a dispute-resolution right. Because a tokenized-agent transaction still rides ordinary card rails, it is a reasonable inference that standard chargeback mechanics apply, but that inference was not verified against a primary Visa or Mastercard dispute-policy source this session — treat it as unconfirmed rather than settled, and check the specific network's current merchant agreement before relying on it." } ], "body": "An agent completing a purchase autonomously does not change what a seller owes when something goes wrong — it changes how fast the mistake can happen and how hard it is to walk back. This article sits inside [how to sell to AI agents](/articles/selling-to-ai-agents), the pillar for this cluster, as the reversal-and-dispute layer underneath the identity and revocation ground covered in [agent spend limits and trust](/articles/agent-spend-limits-and-trust) — that article covers *revoking access before or during* a transaction; this one covers *undoing or contesting a transaction that already happened*.\n\n## What \"refund\" means once the deliverable already shipped\n\nA refund on a digital purchase is only realistically available if the deliverable itself was never sent — not because a buyer changed its mind after receiving it. ChangeGamer's own terms state this precisely: under EU consumer rules, a buyer has a 14-day right of withdrawal, but because a key or corpus file is a digital service delivered immediately on request, the buyer expressly consents to delivery beginning before that window expires, and the right of withdrawal *lapses upon delivery* — a term stated for the Corpus Updates subscription and, as of Q2 2026, extended explicitly to the one-time emailed deliverables on the Corpus and Enterprise licenses too, per [access and pricing for crawlers](/resources/access-and-pricing). In practice that leaves one real question when a refund request comes in: did the deliverable actually go out? A Starter key that returned a 404 instead of a working `cg_` token, or a Corpus/Enterprise license whose corpus email never arrived within the stated one-business-day window, is a legitimate refund case. A key that was issued and works, or a corpus file that was sent and opened, is not — the digital-delivery carve-out has already closed that door, whether the requester is a person or the agent that executed the checkout on their behalf.\n\nThis is worth stating plainly because \"refunds are easy via Stripe\" is the wrong mental model here. Stripe makes it operationally trivial to *issue* a refund; it does nothing to change what a seller has agreed to refund. An agent that autonomously buys a key expecting a no-questions-asked reversal window is relying on a right that, by ChangeGamer's own published terms, ends the moment delivery completes.\n\n## Cancelling a subscription is not the same as refunding it\n\nOf ChangeGamer's four paid tiers, only Corpus Updates is a true subscription — Starter, Corpus, and Enterprise are one-time purchases with no recurring charge to cancel at all. Cancelling Corpus Updates through the Stripe customer portal before the next billing date stops the *next* renewal; it does not, by itself, refund the period already paid for. [Access and pricing](/resources/access-and-pricing) is explicit on this: a refund for the current period is offered only if no corpus file has been delivered during it, requested by replying to the Stripe receipt email. Once the annual corpus file has gone out, cancellation is a forward-looking action — it stops future billing and future re-delivery, and the buyer retains whatever rights attach to the corpus version already delivered, per the same terms. A seller fielding a request from an agent (or the person operating it) that conflates \"I cancelled\" with \"refund my last charge\" needs to check one fact before answering either way: was that period's deliverable actually sent.\n\n## Settlement finality: why an x402 payment cannot just be undone\n\nA settled x402 payment has no seller-side reversal mechanism documented anywhere in this corpus, and a seller should not imply one exists. The protocol's flow — client signs a transfer authorization, server or facilitator verifies it, then broadcasts and settles on-chain — is described as a one-way sequence ending in an `X-PAYMENT-RESPONSE` settlement confirmation, per [agentic payment protocols](/resources/agentic-payment-protocols) and the seller-side verify-then-settle mechanics in [accepting x402 payments](/articles/accepting-x402-payments). Once that settlement confirmation exists, the funds have moved on-chain; there is no described seller-initiated \"undo.\"\n\nThe one mechanism that looks superficially like a refund is Apify's deposit-and-refund pattern for the `upto` scheme, and it is important not to conflate it with post-settlement reversal. That pattern authorizes a *ceiling* before a variable-cost run starts, and returns whatever portion of the deposit the run did not use *at completion* — it is a pre-settlement true-up of a variable cost against an authorized maximum, per [agent wallets and x402](/resources/agent-wallets-x402), not a mechanism for clawing back money after a fixed payment has already settled. A seller running the `exact` scheme, where the full authorized amount settles up front, has no equivalent true-up available at all. If your x402 integration needs anything resembling a refund path, build it as a business decision — sending a separate on-chain payment back to the buyer's wallet — rather than assuming the protocol gives you one for free.\n\n## Card-network agent tokens: a kill switch, not a documented dispute right\n\nBoth Visa and Mastercard document the ability to revoke an agent's tokenized card credential independently of the user's underlying card, per [agent spend controls](/resources/agent-spend-controls) — a clean, network-level kill switch that stops a misbehaving agent from transacting further. That is a real, documented capability. What is not documented anywhere in this corpus, and was not independently verified this session against a primary Visa or Mastercard dispute-policy source, is whether ordinary cardholder chargeback rights apply in full to a transaction that was *already completed* through an agent token. Because the transaction still rides normal card-network rails, assuming standard dispute mechanics carry over is a reasonable working assumption — but it is an inference, not a documented fact, and this article is deliberately naming that gap rather than papering over it. A seller relying on card-network dispute handling as its backstop for agent-driven fraud should confirm the current merchant agreement and dispute-liability terms with its acquirer directly rather than assume they read across unchanged from human-initiated card transactions.\n\n## AP2 and ACP mandates: proof of authorization, not a resolved dispute mechanism\n\nAn AP2 Intent, Cart, or Payment Mandate, or an ACP Shared Payment Token, proves that a purchase was authorized up to a signed ceiling at the moment the agent made it — that is what these mandate-based protocols are built to carry, per [agentic payment protocols](/resources/agentic-payment-protocols) and the protocol comparison in [ACP vs. AP2 vs. x402](/articles/acp-vs-ap2-vs-x402). Neither protocol's documentation in this corpus describes what happens next if the human principal later disputes the charge — claims the agent exceeded its mandate, that the mandate was forged, or that they never intended to authorize the purchase at all. There is no documented real dispute case and no documented issuer-liability rule covering that scenario as of this writing. Treat a signed mandate as strong evidence that authorization existed at transaction time, useful for a seller to produce if a dispute is raised — but not as a settled answer to who bears the loss if the authorization itself is contested. That is a live gap in mandate-based agent commerce, not a solved problem; do not represent it as one to a buyer or an issuer.\n\n## What to log and check before reversing anything\n\nSeparate three questions before acting on any refund or dispute request from an agent buyer, because collapsing them into one decision is the most common mistake:\n\n- **Was the deliverable actually sent?** Check the key-issuance or email-delivery record, not the buyer's claim. This is the only question that matters for ChangeGamer's own one-time tiers, per the withdrawal-lapse terms above.\n- **Was the payment settled, or only authorized?** An x402 `upto` authorization that has not yet settled is a different state than a completed `exact` settlement; a card-token authorization hold is different from a captured charge. Log the settlement receipt or capture confirmation, not just the initial request.\n- **Does the authorization on file actually cover the charge?** For a subscription, check the Stripe subscription status and last renewal date. For a mandate-based purchase, check what ceiling and scope the mandate or token actually granted. A dispute that turns on \"was this authorized\" needs the signed record, not a summary of it.\n\nLog every refund and dispute decision with the request or session id, the deliverable-sent timestamp (or its absence), the settlement or capture status, and — for mandate-based purchases — a reference to the specific mandate or token that authorized the charge. That log is what a seller hands to a payment processor, card network, or its own counsel if a dispute escalates past a reply-to-receipt-email conversation.\n\n## When to route it to a human\n\nRoute to a human immediately, rather than resolving it in an automated reply, whenever a request involves a settled x402 payment (no reversal mechanism exists to fall back on), a claim that a mandate or card token was used outside its authorized scope (a legal and evidentiary question, not a support-ticket one), or any formal chargeback or dispute notice from a card network or processor. Routine refund requests that reduce cleanly to \"was the deliverable sent, yes or no\" can stay automated; anything that requires interpreting whether an authorization was valid cannot, because no protocol in this corpus documents a settled answer for that question yet.", "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": "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" }, "next": { "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" } }, "resources": [ { "slug": "access-and-pricing", "html": "https://changegamer.ai/resources/access-and-pricing", "markdown": "https://changegamer.ai/resources/access-and-pricing.md", "json": "https://changegamer.ai/api/resources/access-and-pricing.json" }, { "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": "agent-spend-controls", "html": "https://changegamer.ai/resources/agent-spend-controls", "markdown": "https://changegamer.ai/resources/agent-spend-controls.md", "json": "https://changegamer.ai/api/resources/agent-spend-controls.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" } ] }