{ "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, "target_query": "how a seller verifies an AI agent's spend limit before granting access", "secondary_queries": [ "seller-side spend limits for AI agent buyers", "how to trust an AI agent's payment authorization", "revoking API access from a misbehaving agent", "does agent reputation or trust scoring exist" ], "tags": [ "spend-controls", "trust", "agents", "payments", "x402", "revocation", "identity", "fraud" ], "published": "2026-08-03", "updated": "2026-08-03", "words": 1760, "premium": false, "license": "https://changegamer.ai/license.xml", "canonical": "https://changegamer.ai/articles/agent-spend-limits-and-trust", "markdown": "https://changegamer.ai/articles/agent-spend-limits-and-trust.md", "takeaways": [ "A bare Bearer API key tells a seller nothing about what the agent behind it is permitted to spend — x402's `upto` scheme, AP2's Intent Mandate, and ACP's Shared Payment Token each carry a cryptographically signed ceiling the seller can check before granting elevated access, which a static key cannot.", "Card-network agent tokens give a seller the cleanest kill switch available today: both Visa and Mastercard support revoking an agent's tokenized credential independently of the user's underlying card, so a seller (or the buyer's bank) can shut off one misbehaving agent without disrupting the human it acts for.", "Verified identity and a bounded, revocable payment ceiling are the two things a seller can actually check today — no portable agent-reputation or trust-score standard exists in the corpus as of August 2026, so \"trust\" for a seller currently means bounding the blast radius of an unknown counterparty, not scoring its history.", "Identity and authorization are separate checks a seller has to run independently: OAuth 2.1 for a remote MCP server proves a caller holds a validly issued, correctly audience-bound token, while a signed payment mandate proves a spend ceiling — neither one substitutes for the other.", "ChangeGamer's own revocation path (a Stripe subscription-cancellation webhook that deletes the token) is a working seller-side kill switch, but its worker has no per-key rate limit today — a real gap for a seller trying to bound how fast a single valid credential can be hit by a looping agent." ], "outline": [ { "depth": 2, "text": "What a bare API key does not tell a seller", "anchor": "what-a-bare-api-key-does-not-tell-a-seller", "url": "https://changegamer.ai/articles/agent-spend-limits-and-trust#what-a-bare-api-key-does-not-tell-a-seller" }, { "depth": 2, "text": "What each payment protocol actually lets a seller trust", "anchor": "what-each-payment-protocol-actually-lets-a-seller-trust", "url": "https://changegamer.ai/articles/agent-spend-limits-and-trust#what-each-payment-protocol-actually-lets-a-seller-trust" }, { "depth": 2, "text": "Seller-side kill switches and revocation", "anchor": "seller-side-kill-switches-and-revocation", "url": "https://changegamer.ai/articles/agent-spend-limits-and-trust#seller-side-kill-switches-and-revocation" }, { "depth": 2, "text": "What \"trust\" operationally means for a seller today", "anchor": "what-trust-operationally-means-for-a-seller-today", "url": "https://changegamer.ai/articles/agent-spend-limits-and-trust#what-trust-operationally-means-for-a-seller-today" }, { "depth": 2, "text": "The abuse angle: bounding what a valid credential can do", "anchor": "the-abuse-angle-bounding-what-a-valid-credential-can-do", "url": "https://changegamer.ai/articles/agent-spend-limits-and-trust#the-abuse-angle-bounding-what-a-valid-credential-can-do" }, { "depth": 2, "text": "What to check before granting access", "anchor": "what-to-check-before-granting-access", "url": "https://changegamer.ai/articles/agent-spend-limits-and-trust#what-to-check-before-granting-access" } ], "faq": [ { "question": "Can a seller trust a plain API key the same way it would trust a signed payment mandate?", "answer": "No. A plain Bearer key proves only that whoever holds the string can present it — it carries no information about what the caller is authorized to spend, when that authorization expires, or who signed it. A signed payment mandate — x402's `upto` authorization, AP2's Intent Mandate, or ACP's Shared Payment Token — carries a cryptographically bound ceiling and scope the seller can check independently of trusting the caller's own claims. A seller granting only metered, low-value access can reasonably run on bare keys; a seller granting high-value or irreversible access should prefer a mechanism that proves the ceiling rather than one that merely gates on possession of a string." }, { "question": "How does a seller revoke access from an agent that is spending too fast or misbehaving?", "answer": "The mechanism depends on which layer the agent is spending through. For a seller's own API key, revocation means deleting or invalidating the stored credential — ChangeGamer does this via a Stripe `customer.subscription.deleted` webhook that looks up and deletes the token, documented in [issuing API keys to AI agents automatically](/articles/api-key-issuance-for-agents). For a card-network agent token, both Visa and Mastercard support revoking the agent's tokenized credential independently of the user's underlying card — the cleanest kill switch of the three, since it does not require the seller to touch its own systems at all. Whatever the mechanism, pair every spend cap with an explicit, tested stop action before go-live — a cap without an enforcement path is just a number." }, { "question": "Does a trust score or reputation system exist for AI agents yet?", "answer": "No published, portable standard exists as of August 2026. There is no cross-seller agent-reputation registry, no signed history-of-good-behavior credential, and no scoring mechanism a seller can query before granting access. What exists instead is verified identity (workload identity plus a delegated-authority grant, or OAuth 2.1 for a remote MCP server) and bounded, revocable payment authorization — those are the two levers a seller actually has today. Treat any claim of a live agent trust-score standard as unverified until a primary source documents one." }, { "question": "Is verifying an agent's identity the same thing as verifying its spend limit?", "answer": "No, and conflating them is a common mistake. Identity answers \"is this the caller it claims to be, with a validly issued credential\" — the two-layer model of workload identity plus delegated authority covered in [agent identity and authentication](/resources/agent-identity-authentication), or the OAuth 2.1 Resource Server check covered in [MCP server authentication](/resources/mcp-server-authentication). Spend-limit verification answers a completely different question: what is this already-authenticated caller allowed to pay, and who signed that ceiling. A seller needs both checks, run independently — a well-authenticated agent can still present an unbounded or forged payment claim, and a bounded payment claim tells you nothing about who is presenting it." } ], "body": "A seller granting an inbound agent elevated access is running the mirror image of the question [agent spend controls](/resources/agent-spend-controls) answers. That resource is written from the agent-builder's chair: how do I bound what my own agent can lose. This article is written from the seller's chair: an agent is calling your API or trying to pay for your content — what can you actually verify about what it is allowed to spend, and what do you do once it has spent it? It sits inside [how to sell to AI agents](/articles/selling-to-ai-agents), the pillar for this cluster, as the trust-and-revocation layer underneath the rail decisions in [ACP vs. AP2 vs. x402](/articles/acp-vs-ap2-vs-x402) and the pricing structure in [pricing tiers for machine buyers](/articles/pricing-tiers-for-machine-buyers).\n\n## What a bare API key does not tell a seller\n\nA Bearer API key proves possession of a string, nothing more. When ChangeGamer's worker validates a key, it checks whether that exact token exists in its store and reads back a tier — it does not, and cannot, check what the caller behind that key is authorized to spend beyond the tier's flat price, because the key carries no ceiling of its own (mechanics in [issuing API keys to AI agents automatically](/articles/api-key-issuance-for-agents)). That is a fine model for flat-priced, low-value access: the buyer paid a fixed amount once, the key unlocks a fixed tier, and there is no variable spend to bound. It stops being sufficient the moment a seller wants to grant metered, variable-cost, or high-value access to a caller it has never seen before — at that point, a seller needs a mechanism that proves a ceiling, not just possession.\n\n## What each payment protocol actually lets a seller trust\n\nThe agent-purchase-authorization and content-payment protocols in [agentic payment protocols](/resources/agentic-payment-protocols) exist for a buyer to bound its own spend, but each also hands the seller a specific, checkable claim about that bound.\n\n| Mechanism | What the seller can verify | What it does not tell the seller |\n|---|---|---|\n| Bare API key | The caller holds a previously issued credential | Nothing about a spend ceiling; the tier price is the only bound, fixed at mint time |\n| x402 `upto` scheme | A signed authorization for a stablecoin ceiling, checked and settled by a facilitator before the resource is served | Nothing about the caller's off-chain identity or history beyond the wallet address that signed |\n| AP2 Intent Mandate | A W3C Verifiable Credential carrying a cryptographically signed price ceiling the merchant/network cannot exceed | Whether the human principal behind the mandate remains reachable if something goes wrong |\n| ACP Shared Payment Token | A token scoped to one seller and bounded by amount and time, so the agent cannot charge more than the user authorized | Anything beyond that single scoped transaction — it is not a standing credential |\n| Card-network agent token (Visa/Mastercard) | A tokenized credential bound to one agent, one merchant scope, and a consent policy set at issuance, with native per-transaction, MCC, time, and frequency limits | The agent's own reasoning or intent — only the payment rail's programmable limits |\n\nThe common thread across the bottom four rows: each shifts the ceiling from something the seller has to take on faith to something the seller (or a facilitator/network acting for it) can check cryptographically before granting access. A seller accepting x402's `upto` scheme is not trusting the calling agent's good behavior — it is trusting a signed authorization a facilitator verifies and settles against, per the verify-then-settle flow in [how to accept x402 stablecoin payments](/articles/accepting-x402-payments). A seller accepting an AP2 Intent Mandate or an ACP Shared Payment Token is trusting the same thing one layer up: a signed ceiling, not the agent's self-report of its own budget.\n\nNone of this is free of caveats. AP2's stable version number is not independently confirmable from primary FIDO Alliance sources as of this writing, per [agentic payment protocols](/resources/agentic-payment-protocols) — architect toward it, do not treat it as settled yet. And a signed ceiling only bounds the transaction it covers; it says nothing about whether the same agent, wallet, or mandate has behaved well on a hundred other sellers' sites, a gap covered further down.\n\nVerification runs in both directions, too: a seller checking a buyer's ceiling should also publish its own price as a parseable field, not a sentence, so an agent operating under its own cap — as described in [agent spend controls](/resources/agent-spend-controls) — can rule the resource in or out before it ever sends a request. That mechanism is covered in [machine-readable pricing pages](/articles/machine-readable-pricing-pages) and the tier-design decisions behind it in [pricing tiers for machine buyers](/articles/pricing-tiers-for-machine-buyers); publishing badly does not protect a seller, it just means agents with a real budget skip the resource rather than negotiate with it.\n\n## Seller-side kill switches and revocation\n\nA spend ceiling without an enforcement action on the seller's side is exactly as useful as one on the buyer's side: a number nobody acts on. ChangeGamer's own revocation mechanism is a concrete, working example of the credential-layer kill switch — its mint step writes a `subscription: -> token` mapping, and a `customer.subscription.deleted` Stripe webhook reads that mapping, deletes the token, and writes an audit record, all without an operator touching anything (full mechanism in [issuing API keys to AI agents automatically](/articles/api-key-issuance-for-agents)). That is a seller revoking its own credential in response to an external signal — cancellation — not in response to detecting bad behavior mid-session, a meaningfully different and harder trigger to build.\n\nAt the payment-rail layer, card-network agent tokens give a seller — or, more precisely, the network or the buyer's bank acting on the seller's dispute — the cleanest revocation path available today: both Visa and Mastercard support revoking an agent's tokenized credential independently of the user's underlying card, per [agent spend controls](/resources/agent-spend-controls). One call disables the agent on that rail without disrupting the human whose card it was scoped to. A seller cannot trigger that revocation directly — it sits with the network and the cardholder — but it is the backstop behind a card-rail transaction gone wrong.\n\nWhat ChangeGamer does not yet have is a rate-of-spend kill switch at the credential layer — no per-key request counter, no automatic pause when a single valid key is hit unusually fast, a gap already named in [issuing API keys to AI agents automatically](/articles/api-key-issuance-for-agents). A seller granting access to variable-cost or metered resources should treat a per-key rate limit as part of the same runbook as outright revocation: a looping agent can exhaust a seller's infrastructure budget as easily as it exhausts its own wallet, and a revocation trigger that fires only on cancellation does nothing about a loop happening right now on an otherwise-legitimate, still-paying key.\n\n## What \"trust\" operationally means for a seller today\n\nFor a seller granting access to an unfamiliar agent, \"trust\" resolves to two checkable things today — verified identity and a bounded, revocable payment claim — and explicitly not to a third thing that does not exist yet: a portable reputation or track record. The two checks answer different questions and a seller needs both, run independently.\n\nOn identity: an agent calling over MCP's remote Streamable HTTP transport should be authenticated via the OAuth 2.1 flow the spec has mandated since its 2025-06-18 revision — PKCE with S256, RFC 9728 metadata discovery, and RFC 8707 audience binding so a token issued for one MCP server cannot be replayed against another, covered in [MCP server authentication](/resources/mcp-server-authentication). Worth stating plainly: ChangeGamer's own `/mcp` endpoint is currently unauthenticated, with no OAuth flow or RFC 9728 metadata, gating only paid content via an application-layer `api_key` argument — a real gap, not a pattern to copy. One layer up, the two-layer model in [agent identity and authentication](/resources/agent-identity-authentication) separates what an agent *is* (a workload identity, ideally short-lived and attested) from what it is *authorized to act on behalf of* (a scoped delegated-authority grant) — a seller should know which of these two claims its access decision actually depends on. On payment, the table above is the seller-side answer: prefer a mechanism that proves a ceiling cryptographically over one that only proves possession of a string, when the value of what you are granting justifies the extra integration cost.\n\nWhat does not exist is the third leg: no published, portable agent-reputation or trust-score standard that would let a seller ask \"has this agent, wallet, or mandate behaved well across other sellers before\" and get a verifiable answer. No resource in this corpus documents one, and no primary source turned up one as of August 2026. Name that absence outright rather than work around it with an invented scoring scheme — a seller today bounds the blast radius of an unknown counterparty through identity verification, a checkable spend ceiling, and a tested revocation path, not a track record it can look up.\n\n## The abuse angle: bounding what a valid credential can do\n\nHigh-volume, fast, automated agent traffic against a paid resource is a security-adjacent problem as much as a finance one. [Agent spend controls](/resources/agent-spend-controls) points to OWASP's LLM Top 10 (LLM10:2025, Unbounded Consumption) as the framing for uncapped spend generally, and the [agentic security checklist](/resources/agentic-security-checklist) names per-identifier request logging with a trace id and least-privilege scoping as standing controls that apply whether the caller is a person or a script. Neither is written specifically about defending a paid endpoint against agent-driven abuse — treat both as general production-security guidance to apply here, not a bespoke fraud playbook. The concrete gap on ChangeGamer's own side is the one already named above: no per-key rate limit, so a single valid, paying key has no ceiling on how fast it can be called beyond whatever the underlying infrastructure tolerates — the honest state of a live example, not a template to copy.\n\n## What to check before granting access\n\nDecide whether what you are granting justifies more than a bare key; if it does, prefer a mechanism that proves a spend ceiling cryptographically — x402's `upto` scheme, an AP2 Intent Mandate, or an ACP Shared Payment Token — over one that only proves possession of a string. Verify identity separately from payment authorization. Build and test a revocation path before you need it. Add a rate-of-spend control at the credential layer if your resource is metered — a total cap alone will not catch a fast loop in time. And do not reach for a trust score that does not exist: as of August 2026, bounded and revocable is the whole toolkit.", "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": "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" }, "next": { "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" } }, "resources": [ { "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": "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-identity-authentication", "html": "https://changegamer.ai/resources/agent-identity-authentication", "markdown": "https://changegamer.ai/resources/agent-identity-authentication.md", "json": "https://changegamer.ai/api/resources/agent-identity-authentication.json" }, { "slug": "mcp-server-authentication", "html": "https://changegamer.ai/resources/mcp-server-authentication", "markdown": "https://changegamer.ai/resources/mcp-server-authentication.md", "json": "https://changegamer.ai/api/resources/mcp-server-authentication.json" }, { "slug": "agentic-security-checklist", "html": "https://changegamer.ai/resources/agentic-security-checklist", "markdown": "https://changegamer.ai/resources/agentic-security-checklist.md", "json": "https://changegamer.ai/api/resources/agentic-security-checklist.json" } ] }