Agentize

Go agent-ready. Publish once. Any agent can shop you.

Open registry and search, not locked inside ChatGPT or Claude. Settle USDC in chat via x402.

SellShop

Sellers

Log in as seller

Bind a wallet, publish to the open registry. Shoppable by every agent.

Continue to Sell

Buyers

Log in as buyer

Shop in chat, or drop the registry skill into any agent and buy over public HTTP.

Continue to Shop

01 — Problem

Agent commerce is real. Open catalogs are not.

Merchants list where two chat apps can reach them. Every other agent — procurement, local, personal, custom — hits a wall.

Impact

1→0.1

For every shopping agent, roughly a tenth of an open catalog.

2

Chat apps get the closed path. Everyone else is locked out.

∞

Procurement bots, local LLMs, Cursor runners — demand without HTTP-shoppable supply.

02 — Solved

Same problems. Explicit fixes.

  • Problem 01

    Catalogs locked inside two chat apps

    Solution

    Open registry.json + /api/search — any HTTP agent

  • Problem 02

    Agents scrape HTML and hope

    Solution

    Machine catalog + llms.txt per store

  • Problem 03

    Checkout leaves the conversation

    Solution

    Authorize in chat → settle USDC via x402

  • Problem 04

    Merchant admin marathon to go live

    Solution

    Talk, CSV, or URL → live endpoints

  • Problem 05

    Every buyer agent rebuilds checkout

    Solution

    Drop agentize-registry-shop and purchase

03 — Competitive

Where Agentize wins on paper.

Named surfaces. Features as ticks and crosses — no soft labels.

FeatureChatGPT Instant CheckoutStripe ACPShopifyAmazonCloudflare AgentsAgentize
Open to any HTTP agent
Machine-readable merchant catalog
Merchant publishes once, owns endpoints
Intent search across independent stores
In-chat settle (x402 / authorize)
No app / marketplace / runtime gate
Drop-in buyer skill (any agent)

Cloudflare Agents run agents — not a merchant catalog protocol; included as adjacent infrastructure. Stripe ACP / Instant Checkout class flows gate reach through partner surfaces.

04 — Protocol

How it works. What it runs on.

  1. Publish

    World ID · registry · llms.txt

    Merchant verifies with World, then talks inventory live onto the open index.

  2. Search

    skill · GET /api/search

    Buyer agents drop the skill, then rank via the same path humans use.

  3. Authorize

    preview · locked quote

    Item, payee, amount visible. Agent does not move money yet.

  4. Settle

    Intercepta · USDC · x402

    Screen payTo + payer, then HTTP 402 → signature → 200 on Base.

Any agent can call

No ChatGPT or Claude gate

agent — bash

Stack

  • World ID
  • Intercepta
  • Base · USDC
  • x402
  • registry.json
  • /api/search
  • llms.txt
  • Agent skill

05 — Buyer skill

Any buyer. One skill. The whole registry.

Drop agentize-registry-shop into Cursor, Claude Code, or any agent runner. No API key. No HTML scrape. Discover and pay over public HTTP.

You convert the shop. They bring their agent.

Merchants publish once. Buyer agents do not rebuild a custom integration. They load the skill and shop every listed store on the network.

  • Public protocol

    registry.json, llms.txt, /api/search, POST /buy. Payment proof is the gate.

  • Locked quotes

    Settle tools only see store, SKU, price, and merchant address. Catalog copy cannot rewrite the payee.

  • Same security as our buyer

    World-listed merchants. Intercepta at the x402 handshake. Confirm spend before sign.

Open SKILL.md

.agents/skills/agentize-registry-shop/SKILL.md

protocol · no API key · MIT

Drop-in
name: agentize-registry-shop
triggers: buy from Agentize · registry.json
rail: USDC x402 on Base

Discover then buy

  1. 01GET /registry.jsonopen store index
  2. 02GET /api/search?q=same ranker as the buyer UI
  3. 03GET /s/{slug}/catalog.jsonfull SKUs, lock the quote
  4. 04POST /s/{slug}/buyHTTP 402 → USDC x402 → 200

Hard rules

Do not scrape HTML. Lock the quote before pay. Confirm spend. Verify 402 payTo and amount match.

Drop at .agents/skills/agentize-registry-shop

06 — Sponsors in the flow

Where the stack protects the market.

World gates who can sell. Intercepta gates who can settle. Base carries the USDC rail. Not logo wallpaper — wired into the path.

Protocol path

  1. 01

    Merchant

    Talk / CSV / URL

  2. World ID

    One human → one storefront

    Sponsor
  3. 03

    Publish

    registry · llms.txt

  4. 04

    Buyer agent

    Skill · search · authorize

  5. Intercepta

    Screen payTo + payer

    Sponsor

  6. x402 settle

    USDC on Base

Intercepta · buyer side

Screens merchant payTo before the agent signs — refuse dirty receive wallets.

Intercepta · seller side

Screens payer address on settle — refuse / hold toxic buyers before USDC moves.

World — merchant onboarding

World — merchant onboarding

Onboarding / listing gate

Proof of personhood before a storefront lists. One World ID nullifier maps to one merchant account — bots and farmed shops cannot flood the open registry.

Intercepta — x402 trust layer

Intercepta — x402 trust layer

Inside POST /buy · 402 handshake

Live AML / risk screen inside the payment path. Buyers are protected from dirty payTo wallets; merchants are protected from toxic payers — allow, hold, or refuse before settle.

07 — Go to market

How we actually go live.

Merchant supply first. Agent demand via skill. Proof in the protocol. Then the loop.

01

Supply

Onboard fashion and specialty merchants via chat + CSV — fastest path to live SKUs on the registry.

02

Demand

Ship the public registry-shop skill so Cursor, Claude, and local agents can discover and buy without a partnership.

03

Proof

Protocol demo (402 → 200) plus open docs — /llms.txt and the skill — for hackathons and agent builders.

04

Loop

More merchants → denser /api/search → more agent buys → more merchants. Network, not a walled app deal.

Agentize

Publish once for every agent. Sell first. Shoppers follow.

SellShop