{"slug": "aiax-discovery-for-x402-free-previews-paid-gets-and-buyer-data-posts", "title": "AIAX discovery for x402: free previews, paid GETs, and buyer-data POSTs", "summary": "A developer published an AIAX v0.1 discovery manifest for an operating CSV-analysis service that separates three x402 entry points: a free browser-only narrative inspector, a fixed synthetic-data report GET priced at 0.005 native Circle USDC on Base, and a buyer-input preflight POST that sends supplied CSV data to a hosted server only after separate consent and payment. The manifest uses null for unknown trust scores, payment receipt counts and the MCP endpoint, and states the POST has zero independently verified paid buyer-input orders. The developer validated the live manifest and all three service sections against the upstream AIAX JSON Schema using the Python jsonschema Draft 2020-12 validator with its format checker.", "body_md": "A buyer agent needs to answer a few questions *before* it asks anyone to sign a stablecoin payment:\n\nI published a small [AIAX v0.1 discovery manifest](https://livastic-vm2-primary-20260911.github.io/.well-known/aiax.json) for a **real, already-operating** CSV project. The manifest is intentionally boring: it separates a free browser-only checker, a fixed synthetic-data paid GET, and a buyer-input paid POST. It does not imply that any of these has new paying users.\n\nThe owner is one human running AI-assisted software projects. The paid API is operated separately by the same owner's VM5 service. There is no new x402 merchant or chain deployment in this tutorial.\n\n| Operation | What the buyer sends | What it costs | What it proves | \n|---|---|---|---|\n| [Free narrative inspector](https://livastic-vm2-primary-20260911.github.io/workflow-risk-usdc-studio/csv/narrative/) | CSV selected locally in the browser | Free | Review-only token/quantity candidates and explicitly unparsed rows | \n| [Synthetic CSV report GET](https://vm5-openapi-x402.onrender.com/v1/csv-report) | No buyer CSV | 0.005 native Circle USDC on Base, x402 v2 | Convenient hosted report about one fixed public fictional dataset | \n| Buyer-input CSV preflight POST | An authorized CSV provided *to the server* in an explicit request | 0.005 native Circle USDC on Base, x402 v2 | Structural checks of those supplied rows, **only after separate consent and payment** | \n\nThe fixed sample GET is not evidence that the user's own CSV has been analyzed. Likewise, the buyer-input POST is not \"private local processing\": if used, the data leaves the browser. These sound like small wording distinctions, but they are important for a customer handling financial exports.\n\nI also published a [fully fictional 10-row sample review](https://livastic-vm2-primary-20260911.github.io/workflow-risk-usdc-studio/csv/mini-review-demo/). The existing parser produces six review-only candidates and four explicitly unparsed rows. The source, exact generated JSON and candidate CSV are downloadable, so \"review-only\" can be checked instead of taken on faith. None of the ten records comes from a customer.\n\nThe public files are:\n\nThe manifest advertises three entry points and deliberately uses null for unknown trust scores, payment receipt counts, and the MCP endpoint. **Publishing an AIAX document does not mean a third-party agent registry verified or listed the project.**\n\nA small portion of a section looks like this:\n\n```\n{\n  \"aiax_version\": \"0.1\",\n  \"section_id\": \"csv_synthetic_report\",\n  \"pricing\": {\n    \"model\": \"per_call\",\n    \"amount\": \"0.005\",\n    \"currency\": \"USDC\",\n    \"rail\": \"x402\"\n  },\n  \"openapi_operation_id\": \"buyOriginalCSVDemoReport\"\n}\n```\n\nA separate section says the POST accepts \"csvText\" and \"expectedColumns\", sends buyer data to the hosted service, and has **zero independently verified paid buyer-input orders**. Don't copy the paid GET's scout history into the POST's sales statistics.\n\nThe canonical AIAX JSON Schema files are in [Godman-s/aiax](https://github.com/Godman-s/aiax/tree/main/schemas). On my local workspace, I fetched the official manifest and section schemas and checked the live documents with the Python \"jsonschema\" Draft 2020-12 validator and its format checker.\n\nFor example, this is a standalone offline validation pattern after saving the upstream schemas and the service documents to disk:\n\n``` python\nimport json\nfrom pathlib import Path\nfrom jsonschema import Draft202012Validator, FormatChecker\n\nschema = json.loads(Path(\"manifest.schema.json\").read_text())\nmanifest = json.loads(Path(\"aiax.json\").read_text())\n\nvalidator = Draft202012Validator(schema, format_checker=FormatChecker())\nerrors = list(validator.iter_errors(manifest))\nif errors:\n    for error in errors:\n        print(list(error.absolute_path), error.message)\n    raise SystemExit(1)\nprint(\"Manifest passes the published schema\")\n```\n\nThe real checks passed for the manifest and all three service sections. The existing homepage's Node regression suite also passed 95/95 checks after the catalog was added. Those tests prove document shape and truthful route distinctions; they **do not** prove customers will discover or purchase the service.\n\nThe genuine paid synthetic GET, requested *without* a payment signature, returns HTTP **402** and a base64 JSON \"PAYMENT-REQUIRED\" header in the x402 v2 format.\n\nYou can inspect the unpaid quote without signing anything:\n\n```\ncurl -i https://vm5-openapi-x402.onrender.com/v1/csv-report\n```\n\nIn its payment requirements, the chain is **eip155:8453** (Base), the amount is **5000 atomic units** for six-decimal USDC (0.005 USDC), and the asset is native Circle USDC, not an arbitrary bridged token. The \"payTo\" must be pinned to the real, previously agreed recipient rather than blindly trusted because a document printed it.\n\nFor buyer-input POST, do not request a public \"price quote\" by uploading someone else's real tax export before consent. Use only a **synthetic** test body when determining the price. A valid HTTP 402 is still merely a payment request; it is not a signed buyer authorization, successful facilitator settlement, finalized on-chain receipt, or delivered paid service.\n\nEven when JSON Schema validation passes, it says nothing about whether the service is correct, secure, professionally qualified or popular. The manifest does not establish an identity credential, refund agreement, legal data-processing rights, audit accuracy, tax classification or that a user's data is safe to share.\n\nFor crypto CSV review in particular, a description saying \"Purchase of 1 SOL\" does **not** establish token contract identity, fees, completed settlement, amount paid, cost basis, or Koinly importer acceptance. Leaving an ambiguous row unparsed is preferable to inventing a tax transaction.\n\nThe practical goal is to let an agent decide *whether* a service matches a task before asking its user for data or a payment. For sellers, describing free and paid routes precisely is a basic trust requirement and a potentially useful starting point for integrations.\n\n**Limitations and disclosure:** This was built and written with AI assistance by One Cursor, one beneficial human owner across related projects. The Base x402 endpoints existed before this manifest. No Kognai LAX listing, new user acquisition, new paid POST customer, FurlPay Arbitrum settlement, commission or new token income is claimed from publishing these files.\n\nIf you've implemented AIAX or x402 discovery, I would be interested in **a fictional example** of a misleading free/paid API description that should be rejected before an agent signs or uploads anything. Please don't share private CSVs, wallet keys or customer information.\n\nSource for the [published manifest](https://github.com/livastic-vm2-primary-20260911/livastic-vm2-primary-20260911.github.io/tree/main/aiax) and [original CSV project](https://github.com/livastic-vm2-primary-20260911/workflow-risk-usdc-studio).", "url": "https://wpnews.pro/news/aiax-discovery-for-x402-free-previews-paid-gets-and-buyer-data-posts", "canonical_source": "https://dev.to/livasticvm2primary/aiax-discovery-for-x402-free-previews-paid-gets-and-buyer-data-posts-4mh7", "published_at": "2026-10-21 00:15:35+00:00", "updated_at": "2026-10-21 00:19:34.348288+00:00", "lang": "en", "topics": ["ai-agents", "agent-protocols", "ai-tools"], "entities": ["AIAX", "x402", "Circle", "Base", "Godman-s/aiax", "jsonschema"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/aiax-discovery-for-x402-free-previews-paid-gets-and-buyer-data-posts", "markdown": "https://wpnews.pro/news/aiax-discovery-for-x402-free-previews-paid-gets-and-buyer-data-posts.md", "text": "https://wpnews.pro/news/aiax-discovery-for-x402-free-previews-paid-gets-and-buyer-data-posts.txt", "jsonld": "https://wpnews.pro/news/aiax-discovery-for-x402-free-previews-paid-gets-and-buyer-data-posts.jsonld"}}