{ "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, "target_query": "how do AI agents discover paid APIs", "secondary_queries": [ "how does an agent find a paid API", "AI agent discovery surfaces for paid content", "llms.txt vs MCP registry vs x402 discovery", "how do agents find out an endpoint is payable" ], "tags": [ "discovery", "llms.txt", "mcp", "x402", "agents", "json-api" ], "published": "2026-08-04", "updated": "2026-08-04", "words": 1576, "premium": false, "license": "https://changegamer.ai/license.xml", "canonical": "https://changegamer.ai/articles/discoverability-for-paid-agent-apis", "markdown": "https://changegamer.ai/articles/discoverability-for-paid-agent-apis.md", "takeaways": [ "An agent discovers a paid surface in one of two modes that call for different designs: proactive discovery, where it is specifically shopping for a capability and reads an index before touching anything gated, and reactive discovery, where it stumbles into a 402 mid-task and learns the paid surface exists only at that moment.", "Four proactive surfaces matter as of August 2026: a curated `/llms.txt` index, a JSON API index such as `/api/resources.json`, listing in an MCP registry or aggregator, and automatic inclusion in the x402 Bazaar the moment a first payment settles — none of these require the same investment, and a seller can be found by some without building all four.", "There is no established `.well-known` convention for discovering prices or offers. The corpus confirms `.well-known` conventions for identity and auth discovery only — `/.well-known/agent-card.json` for A2A agent identity, `/.well-known/oauth-protected-resource` and `/.well-known/oauth-authorization-server` for MCP OAuth — none of it is about what something costs.", "For an agent with a fixed, single-fetch discovery budget, an `/llms.txt` or JSON index fetch outranks an MCP connection attempt: it costs one HTTP GET with no handshake, no auth negotiation, and no persistent session, and it can point onward to everything else in the same response.", "A seller with no MCP server and no x402 activity is still discoverable through llms.txt and a JSON API index alone — it is a weaker footprint, reaching only agents that already crawl or fetch directly, but it is not a non-starter, and it is the cheapest surface to stand up first.", "The x402 Bazaar inverts the usual order of marketing and revenue: a seller does not submit a listing, the facilitator auto-catalogs the endpoint the first time it settles a payment for it, so the first sale is the listing event, not the result of one." ], "outline": [ { "depth": 2, "text": "Proactive vs. reactive discovery", "anchor": "proactive-vs-reactive-discovery", "url": "https://changegamer.ai/articles/discoverability-for-paid-agent-apis#proactive-vs-reactive-discovery" }, { "depth": 2, "text": "Your own site's entry points: llms.txt and the JSON API index", "anchor": "your-own-site-s-entry-points-llms-txt-and-the-json-api-index", "url": "https://changegamer.ai/articles/discoverability-for-paid-agent-apis#your-own-site-s-entry-points-llms-txt-and-the-json-api-index" }, { "depth": 2, "text": "MCP registry listing and community aggregators", "anchor": "mcp-registry-listing-and-community-aggregators", "url": "https://changegamer.ai/articles/discoverability-for-paid-agent-apis#mcp-registry-listing-and-community-aggregators" }, { "depth": 2, "text": "The HTTP 402 itself as an incidental discovery signal", "anchor": "the-http-402-itself-as-an-incidental-discovery-signal", "url": "https://changegamer.ai/articles/discoverability-for-paid-agent-apis#the-http-402-itself-as-an-incidental-discovery-signal" }, { "depth": 2, "text": "x402's auto-listing rail: the first sale as the listing event", "anchor": "x402-s-auto-listing-rail-the-first-sale-as-the-listing-event", "url": "https://changegamer.ai/articles/discoverability-for-paid-agent-apis#x402-s-auto-listing-rail-the-first-sale-as-the-listing-event" }, { "depth": 2, "text": "What .well-known does — and does not — cover", "anchor": "what-well-known-does-and-does-not-cover", "url": "https://changegamer.ai/articles/discoverability-for-paid-agent-apis#what-well-known-does-and-does-not-cover" }, { "depth": 2, "text": "Two edge cases worth a direct answer", "anchor": "two-edge-cases-worth-a-direct-answer", "url": "https://changegamer.ai/articles/discoverability-for-paid-agent-apis#two-edge-cases-worth-a-direct-answer" }, { "depth": 2, "text": "Sequencing discovery against the rest of the funnel", "anchor": "sequencing-discovery-against-the-rest-of-the-funnel", "url": "https://changegamer.ai/articles/discoverability-for-paid-agent-apis#sequencing-discovery-against-the-rest-of-the-funnel" } ], "faq": [ { "question": "What is the single best way to make a paid API discoverable to AI agents?", "answer": "A curated `/llms.txt` index at the site root plus a JSON API index such as `/api/resources.json`, both free and reachable in one hop with no authentication. They cost the least to build, work for any agent that fetches pages or JSON at all (not just tool-calling agents with an MCP client), and can link onward to an MCP server or an x402-payable endpoint if you build those later. Neither is a substitute for the other — llms.txt is the curated entry point a fetching agent reads first, the JSON index is what a script parses reliably once it is there." }, { "question": "Does registering an MCP server make my paid API more discoverable than publishing llms.txt?", "answer": "It reaches a different population, not a strictly larger one. An MCP listing puts your tools directly into a tool-calling agent's available-actions list with no crawling or parsing required, which is a stronger placement than a link an agent has to choose to follow — but it only reaches agents whose client has an MCP connector installed and configured, and the official registry (registry.modelcontextprotocol.io) was still in preview as of mid-2026, so it is not yet the single canonical index the way a search engine is. Publish both if you can; they are not competing investments." }, { "question": "Is there a .well-known path agents check to find pricing, like there is for robots.txt?", "answer": "No — not in any verified source as of August 2026. `.well-known` conventions exist for identity and authorization discovery (an A2A Agent Card at `/.well-known/agent-card.json`, MCP OAuth metadata at `/.well-known/oauth-protected-resource` and `/.well-known/oauth-authorization-server`), but none of them describe an offer, a price, or a checkout URL. Treat any claim of a `.well-known/pricing` or `.well-known/offers` convention as unverified; the closest thing that actually exists today is a machine-readable pricing catalog linked from your llms.txt index or your 402 body, not a well-known path an agent checks unprompted." }, { "question": "Can an agent discover a paid API by accident, without looking for it?", "answer": "Yes — this is reactive discovery, and it is common. An agent following a link, calling an endpoint named in documentation, or crawling a site for an unrelated task can hit a gated resource and receive an HTTP 402 response, learning the paid surface exists only at that moment, mid-task. That is a different design problem from proactive discovery: the 402 body has to be self-sufficient (price, a preview, exact retry instructions) because there was no prior index fetch to prime the agent with context." } ], "body": "The pillar names four discovery surfaces in one section — your own site's entry points, an MCP server, marketplaces, and the rail that lists you automatically. This is the deep dive on that stage of [selling to AI agents](/articles/selling-to-ai-agents): not the pricing an agent reads once it has found you, but the mechanics of it finding out you exist at all, and the honest limits of each surface as of August 2026.\n\n## Proactive vs. reactive discovery\n\nProactive discovery is an agent specifically shopping for a capability — it has a task, knows it needs an API or a dataset, and is resolving candidates before committing to any of them. Reactive discovery is an agent stumbling into a paid surface mid-task with no prior intent to shop: it follows a link or calls an endpoint named in a doc it was already reading, and only learns a paid surface exists when it hits the wall. These are different design problems. Proactive discovery rewards being *indexed* somewhere an agent already resolves candidates from — llms.txt, a JSON directory, an MCP registry. Reactive discovery rewards the wall itself being self-sufficient, since there was no earlier fetch to supply context — which is what makes the HTTP 402 response, covered below, a discovery surface in its own right, not just a payment gate.\n\n## Your own site's entry points: llms.txt and the JSON API index\n\nThe cheapest, most controllable discovery surface is the one you serve yourself. `/llms.txt`, proposed by Jeremy Howard (Answer.AI) on 3 September 2024, is a plain-Markdown file at the site root — an H1 title, an optional summary, and H2 link-list sections an agent fetches first and follows selectively (full format in [the llms.txt convention explained](/resources/llms-txt-explained)). The commercial rule that matters here: the index itself, and anything it links to that a buyer needs to evaluate an offer, has to be free and reachable in that first hop — an agent that cannot read your terms without paying to find them cannot decide to pay at all.\n\nThe JSON side follows the same discover-the-index-then-fetch-the-item pattern, one level more structured. `GET /api/resources.json` (or an equivalent corpus index) returns every item's slug, title, description, tags, and variant URLs with no body content — an agent fetches that once, then fetches `/api/resources/.json` only for the items it actually needs, rather than crawling HTML to reconstruct a catalog. The same pattern extends to an `/api/openapi.json` spec for a typed client (full shapes in [JSON API for agents](/resources/json-api)). Neither surface says anything about price beyond that a paid item exists — the fields that let an agent compare and act on an offer are a separate concern covered in [machine-readable pricing pages](/articles/machine-readable-pricing-pages). Discovery's job stops at \"this is reachable and this is what it is called.\"\n\n## MCP registry listing and community aggregators\n\nFor a tool-calling agent, an MCP server puts a catalog directly into its available-actions list — no crawling, no parsing, no guessing which slug maps to which capability. MCP's discovery mechanics are less settled than llms.txt's, though: the official MCP Registry (registry.modelcontextprotocol.io) launched in preview in September 2025 and was **still in preview as of mid-2026**, not yet the single canonical index a search engine is for its own ecosystem (details in [finding and evaluating MCP servers](/resources/mcp-server-discovery)). Beyond the registry, servers also reach agents through client-vendor marketplaces and community aggregators — PulseMCP, Smithery, Glama, and MCP.so among the larger ones as of 2026 — which vary in review rigor and are leads to evaluate, not endorsements to trust outright.\n\nPublishing an MCP server is therefore registry submission via the `mcp-publisher` CLI, plus whatever aggregators and client marketplaces happen to pick it up — not a single \"get listed\" action. That is not a reason to skip it: a paid tool exposed this way is *installed*, a stronger placement than a link an agent has to choose to follow. It is a reason not to treat MCP listing as a complete strategy on its own.\n\n## The HTTP 402 itself as an incidental discovery signal\n\nA 402 response is not only a payment gate — it is the moment an agent that was not shopping learns a paid surface exists at all. An agent calling an endpoint for an unrelated reason gets `402 Payment Required` back instead of the resource, and everything it now knows has to come from that one response, since there was no prior index fetch. ChangeGamer's own 402 contract returns `error`, `resource`, `price_usd`, `payment_url`, `how_to_pay`, `terms`, `license`, `pricing_catalog`, and a `preview` object (title, description, section outline) in one JSON response, with `Link` headers to the payment, license and pricing resources (documented in [paying for access: the HTTP 402 flow](/resources/paying-for-access-402)). An agent with zero prior context can still decide from that one document — self-sufficiency is what reactive discovery demands, distinct from what a proactive index has to do, which is being *findable* in the first place. A strong llms.txt/JSON index reduces how often an agent hits a 402 cold, but never eliminates it: plenty of traffic follows links it found elsewhere, not your index.\n\n## x402's auto-listing rail: the first sale as the listing event\n\nx402 has a distribution property none of the above have: it lists a seller automatically, with no submission step. Coinbase's developer platform runs the **x402 Bazaar**, a discovery layer indexing payable endpoints via a paginated catalog (`GET …/v2/x402/discovery/resources`) and hybrid full-text-plus-semantic search. Sellers do not register anywhere; the CDP facilitator **auto-catalogs an endpoint the first time it settles a payment for it** (grounded in [agentic payment protocols](/resources/agentic-payment-protocols) and [agent wallets and x402](/resources/agent-wallets-x402)). A seller's first successful x402 sale is thus simultaneously its listing event — an inversion of the usual marketing-precedes-revenue order. An endpoint that has never settled a payment is invisible on this surface regardless of how well documented it is; the Bazaar indexes proven payment activity, not published intent. This surface is also contingent on actually running x402 — a wallet, a signing library, a facilitator relationship — so it is a multiplier once running, not a starting point for a seller with no payment rails yet.\n\n## What .well-known does — and does not — cover\n\nWorth stating precisely, since it is easy to over-assume from adjacent conventions: **there is no established `.well-known` convention for pricing or offer discovery.** The `.well-known` conventions that do exist in the verified record are identity and authorization surfaces. A2A defines a self-published Agent Card at `/.well-known/agent-card.json` — identity discovery for one agent calling another, not a seller advertising a price (compared in full in [MCP vs A2A](/resources/mcp-vs-a2a)). MCP's OAuth 2.1 flow uses two `.well-known` fetches in sequence: `/.well-known/oauth-protected-resource` (RFC 9728 — which authorization servers are trusted) then `/.well-known/oauth-authorization-server` (RFC 8414 — the `authorization_endpoint`, `token_endpoint`, `registration_endpoint`) at the server the first document names (full flow in [MCP server authentication](/resources/mcp-server-authentication)). Both establish *who* is calling and *how to authenticate*, resolved before a protected-resource request is even attempted — neither is a mechanism to learn what something costs.\n\nIf a seller wants a stable, predictable pricing path, the pattern this cluster documents — a JSON offer catalog at a fixed path such as `/api/pricing.json`, linked from the llms.txt index and the 402 body's `pricing_catalog` field — achieves that without relying on a convention that does not yet exist for this purpose. Do not build against an assumed `.well-known/pricing` path; nothing in the verified corpus confirms agents check one.\n\n## Two edge cases worth a direct answer\n\nAn agent with a fixed, single-fetch discovery budget should spend it on `/llms.txt` or a JSON index, not an MCP connection attempt. That is a cost argument, not a preference: an index fetch is one unauthenticated `GET` with no handshake, and a well-formed response can itself point onward to an MCP server or a pricing catalog — it is not a dead end even as the only fetch spent. An MCP connection is a protocol handshake, and for a remote server usually an OAuth negotiation, before the agent has learned anything at all — a poor first move on a one-request budget, even though it is the stronger surface once a session is already open.\n\nA seller with neither an MCP server nor any x402 history is still discoverable, just through a narrower funnel. `/llms.txt` plus a JSON index reach every agent that crawls, fetches pages directly, or is pointed at the domain by a citation — a real, often majority, share of agent traffic in 2026, not a fallback for sellers who have not \"graduated\" to MCP or x402. What that seller misses is tool-calling agents that only resolve capabilities via an installed MCP connector, and x402-native agents shopping the Bazaar directly. The llms.txt/JSON-only path is weaker, not invalid, and the cheapest surface to stand up first.\n\n## Sequencing discovery against the rest of the funnel\n\nDiscovery only answers one question — does this paid thing exist, and where — before handing off to evaluation, a different job with a different field shape, covered in [machine-readable pricing pages](/articles/machine-readable-pricing-pages). If evaluation ends in a purchase, the credential the buyer receives is a separate concern again, covered in [issuing API keys to AI agents](/articles/api-key-issuance-for-agents). In order of cost to build: llms.txt and a JSON index first (cheapest, broadest reach, no external dependency), an MCP server second (stronger placement, narrower reach, dependent on a registry ecosystem still maturing), and x402 activity last (strongest automatic distribution, but contingent on payment infrastructure existing and being used before the Bazaar lists anything).", "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": "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" }, "next": { "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" } }, "resources": [ { "slug": "json-api", "html": "https://changegamer.ai/resources/json-api", "markdown": "https://changegamer.ai/resources/json-api.md", "json": "https://changegamer.ai/api/resources/json-api.json" }, { "slug": "llms-txt-explained", "html": "https://changegamer.ai/resources/llms-txt-explained", "markdown": "https://changegamer.ai/resources/llms-txt-explained.md", "json": "https://changegamer.ai/api/resources/llms-txt-explained.json" }, { "slug": "mcp-server-discovery", "html": "https://changegamer.ai/resources/mcp-server-discovery", "markdown": "https://changegamer.ai/resources/mcp-server-discovery.md", "json": "https://changegamer.ai/api/resources/mcp-server-discovery.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": "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" }, { "slug": "mcp-vs-a2a", "html": "https://changegamer.ai/resources/mcp-vs-a2a", "markdown": "https://changegamer.ai/resources/mcp-vs-a2a.md", "json": "https://changegamer.ai/api/resources/mcp-vs-a2a.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" } ] }