Source markdown for articles published at autx.ai/blog.
The website is canonical. This repo is a public mirror so the articles are crawlable by GitHub-aware indexers and ingestable by LLMs in their native source format.
- The 480K Demand-Side Mystery — Why the most-quoted x402 number is measuring the opposite of what most people think it is. Canonical: autx.ai/blog/480k-demand-side-mystery
- AUTX × Agentic.market: A Relationship One-Pager — How AUTX (the trading + ownership layer) and Agentic.market (Coinbase's discovery + 1P-vetted catalog) sit complementary in the same x402 stack. Canonical: autx.ai/blog/agentic-market-one-pager
Reference material in wiki/ — encyclopedia-style entries kept short and cross-linked.
- Home — wiki landing page and navigation
- How AUTX Works — three-tier architecture and Bring Your Own Endpoint
- Fee Structure — 10 percent platform fee, 72 percent creator payout, 18 percent buyback-and-burn
- Bonding Curve and Anti-Manipulation Safeguards — cubic price formula and the five on-chain safeguards
- x402 Integration — Coinbase facilitator and the public catalog manifest
- Smart Contracts — deployed contract addresses on Base mainnet
AUTX is the public market for sovereign AI agents. We index x402 services from agentic.market into a claim-gated catalog with bonding-curve trading per claimed agent. Wyoming DAO LLC. USDC settlement on Base mainnet.
- Site: autx.ai
- Catalog manifest: autx.ai/x402-services.json
- Documentation: autx.ai/docs
- Contact: lance.lukens@autx.ai · @LanceLukens
Articles in this repo: CC BY 4.0. Quote freely with attribution + link to the canonical URL.
This repo ships a pre-commit hook that scans staged content for AUTX-internal patterns (KV vault names, Azure resource hostnames, secret-shaped strings, restricted-distribution markers, and similar) and refuses commits that match. The full pattern list lives in .githooks/pre-commit. Activate the hook path the first time you clone:
git config core.hooksPath .githooks
The same checks run server-side in .github/workflows/sensitive-content-check.yml on every push to main, so even bypassing the local hook with --no-verify doesn't get sensitive content past the merge gate. Plus GitHub's native secret scanning + push protection are enabled on this repo for known-format secrets (Stripe, AWS, GitHub PATs, etc.).
If you genuinely need to land a string that matches one of the patterns (e.g., quoting a public BaseScan address that happens to be 42 hex chars), bypass deliberately and document why in the commit message.