AUTX × Agentic.market: A Relationship One-Pager

For Coinbase BD, the x402 standards group, VCs, and crypto press who've asked: "wait, aren't you competing with Agentic.market?" Short answer: no. We're the trading + ownership layer on top of the discovery layer Coinbase just shipped. Posture: symbiotic, positive-sum. We want Agentic.market to grow.

The stack

Two products. Complementary seats in the same stack. If you're picturing a retail analogy: Agentic.market is Shopify (where you set up the store and find products). AUTX is NYSE (where you buy a share of the store itself).

What AUTX does with Agentic.market's catalog

1. Crawls the public `/v1/services` endpoint with proper pagination. As of 2026-04-26: 573 services / ~29K endpoints / ~24K distinct URLs. Page-1-only fetches return ~50/1,200, so most early third-party catalog estimates undercount by ~10×.
2. Filters by integrationType. v1 is 1P-only. If Coinbase hasn't vetted it, AUTX doesn't list it. This is a deliberate legal and quality gate. We defer to Coinbase's curation.
3. Runs safety passes. Trademark blocklist (Unicode confusables, leet-speak, homoglyphs, zero-width chars), 696-entry reserved-ticker list (NYSE/NASDAQ top 500, crypto top 100, platform internals), Azure Content Safety moderation.
4. Persists as shadow listings owned by a platform custody user ([email protected]). Status: discovery-only. No bonding curve. No token. No trading. No AUTX revenue. A GET or POST to /proxy/<ticker> returns HTTP 302 Location: <source endpoint>. We route discovery traffic to the merchant; we don't intercept it.
5. Waits for the real developer to claim. Free. Cryptographic proof (EOA signature from the x402 merchant wallet) or domain control (/.well-known/autx-claim.txt). No DKIM path in v1.
6. On claim, the dev signs one on-chain `AgentFactory.launchAgent()` tx from their own wallet. AUTX never deploys contracts on an unaffiliated developer's behalf. Bonding curve opens, status flips to active, ownership transfers. Post-claim economics are the same as every other native AUTX agent: 10% platform fee, 72% to the dev in USDC, 18% auto-buyback-and-burn on the dev's own agent token (supply compression, not a platform take). Plus 1% trading fee on bonding-curve trades, split 70% platform / 30% to token holders. For comparison: Virtuals charges 5–10% on tokenless ACP, same ballpark on the platform fee.

Why this strengthens Agentic.market (not the other way around)

1. AUTX sends real usage through to their endpoints. Traders who arrive at AUTX for speculation on $CATS need to actually use the agent to see what it does. POST /proxy/CATS → 302 → source endpoint. That's a CDP-facilitator-settled x402 payment to the merchant Coinbase already vetted. Coinbase keeps the facilitator fee. The merchant keeps their revenue.
2. Claimed devs opt into richer discovery. On claim, the dev can opt their /402 responses into the x402 bazaar extension so Agentic.market's crawlers pick them up with richer metadata (pricing, category, verified ownership proof). Discovery improves for Coinbase's catalog specifically because AUTX finished the verification step.
3. SEO tailwind. AUTX's sitemap.xml enumerates every shadow listing as autx.ai/agents/<ticker>, Google-indexable. Search traffic to those pages routes users into the Agentic.market endpoint via the 302. We do the SEO work; Coinbase gets the traffic tail.

Why AUTX won't become Agentic.market (and vice versa)

The domains don't overlap. Growing either product grows the other.

What AUTX will never do

1. Intercept unconsented merchant revenue. Pre-claim is a 302 redirect. Zero escrow. Zero accrued creator balance. Full stop.
2. Deploy on-chain contracts on a developer's behalf without their signature. The bonding curve only exists after the dev signs launchAgent() themselves. The wallet that triggers the launch is the wallet we record as deployer_address.
3. Rename a ticker without the owner's consent. Pre-claim, the auto-derived ticker is a descriptor (e.g., DOCSANTHRO for an Anthropic-docs-reader endpoint). On claim, the dev picks their own symbol, subject to uniqueness, trademark, and reserved-list checks. Free.
4. Index 3P services as tradable in v1. They go behind the admin review queue until a real vetting process is built.
5. Accept commercial payment to approve a ticker or listing. That would turn our neutral-crawler defense into an editorial decision. Regulatory-analyst closed this door. Revisit only if M3 claim rate tells us to.

Regulatory posture (brief)

• Wyoming DAO LLC (filed 2026-03-08, W.S. 17-31). Smart-contract governance with a legal wrapper.
• Claim-gated architecture explicitly eliminates the Howey exposure that "pre-claim speculation on unaffiliated-dev revenue" would create. No tradable instrument pre-claim → no investment contract.
• 1P-only v1 defers brand-vetting to Coinbase. We're not making independent trademark determinations.
• Free ticker rename (no paid tiers, no token-burn-to-unlock). Any commercial gate on rename would puncture the neutral-crawler framing per Y.Y.G.M. v. Redbubble (2025). Four independent analyst reviews converged on free.
• DMCA + opt-out registry (autx.ai/opt-out.json) shipping next. 48h takedown SLA. Merchant-address and domain-level blocklist.

If Coinbase reaches out

Three questions we want to get on the table quickly:

1. Is there a coordination channel? A standards-group thread in the x402 Discord, a shared Slack for catalog signalling, anything where catalog operators can align on edge cases.
2. Is there appetite for a mutual reference page? AUTX links to Agentic.market as the discovery layer; Agentic.market points tradable / claimed agents at AUTX.
3. Any concerns with the 302-redirect posture or the 1P-only gate? We'd rather learn about a concern before a blog post than after.

None of this is urgent. None of this requires a formal partnership. We're happy running parallel tracks and letting the shared x402 stack speak for itself.

Contact

Lance Lukens · [email protected] · @LanceLukens · autx.ai