cc0 agentic marketplace

Quick start

Three calls: discover the catalogue, pay-and-invoke a model, poll until the image is ready. Paste this into your agent runtime, replace the slug, and you have a working integration.

# 1) Discover what's available
curl https://cc0.company/api/store/agent-services

# 2) Invoke without payment — server replies 402 with the challenge
curl -i -X POST https://cc0.company/api/store/agent-services/hokusai-gen/invoke \
  -H "Content-Type: application/json" \
  -d '{"prompt":"crashing wave at sunrise with Mount Fuji on the horizon, three fishing boats riding the swell, polychrome woodblock print with deep Prussian blue sky and pale cloud bands at the top"}'

# 3) Sign the USDC authorization, retry with the PAYMENT-SIGNATURE header
curl -X POST https://cc0.company/api/store/agent-services/hokusai-gen/invoke \
  -H "PAYMENT-SIGNATURE: <base64-encoded-signed-payload>" \
  -H "Content-Type: application/json" \
  -d '{"prompt":"crashing wave at sunrise with Mount Fuji on the horizon, three fishing boats riding the swell, polychrome woodblock print with deep Prussian blue sky and pale cloud bands at the top"}'
# → 202 { "job_id": "agentservicejob_xxx", "poll_url": "https://..." }

# 4) Poll until done
curl https://cc0.company/api/store/agent-services/jobs/agentservicejob_xxx
# → { "job": { "status": "succeeded", "output_url": "https://replicate.delivery/..." } }

Need the x402 signing library? See skill.md for TypeScript / Python / Go examples using @x402/fetch and friends.

Per-model prompt guides

Every model in the catalogue ships its own prompt skill at /skill/<slug>.md — surfaced as prompt_guide_url on each catalogue entry. The skill documents the LoRA's training caption register and the canonical templates that produced it. Outputs are 2-3× better when prompts match.

# Discover the catalogue and pull every prompt guide up-front
CATALOGUE=$(curl -s https://cc0.company/api/store/agent-services)
echo "$CATALOGUE" | jq -r '.services[].prompt_guide_url' | while read url; do
  echo "=== $url ==="
  curl -s "$url"
done

# Then when you invoke a model, send a prompt that matches its register.

The current per-model guides: sartoshi-gen · darkfarms-gen · hokusai-gen · van-gogh-gen · monet-gen. New models added later will appear here automatically — agents should re-read the catalogue periodically.

Endpoints

All endpoints are served under https://cc0.company/api through the platform proxy. The base URL never changes between environments — your agent uses the same string in dev, staging, and production.

# Sign a 0.01 USDC authorization to /persist, just like /invoke
curl -X POST https://cc0.company/api/store/agent-services/jobs/agentservicejob_xxx/persist \
  -H "PAYMENT-SIGNATURE: <base64-encoded-signed-payload>"
# → 200 { "ipfs_url": "https://ipfs.io/ipfs/Qm...", "ipfs_hash": "Qm..." }

# 1) Send 0.069 USDC on Base to the service's creator_wallet_address
#    (read it from GET /store/agent-services/{slug}).
# 2) POST the prompt + the tx_hash:
curl -X POST https://cc0.company/api/store/agent-services/hokusai-gen/pay-and-invoke \
  -H "Content-Type: application/json" \
  -d '{"prompt":"<your prompt>","tx_hash":"0xabc...123"}'
# Returns 425 if the tx is still pending — retry with backoff. 202 once mined.

x402 v2 payment protocol

The first request to a paid endpoint returns 402 Payment Required with a JSON challenge. Sign a USDC ERC-3009 authorization for the requested amount and retry with the PAYMENT-SIGNATURE header. The Coinbase CDP facilitator verifies, settles on-chain, and your handler then runs as if it were authenticated.

Important: the agent never needs to know the price ahead of time. Always read maxAmountRequired and payTo from the live 402 challenge — they're the source of truth. Hard-coded values will desync when a service updates its pricing.

Discovery — agentic.market

Every paid endpoint here is automatically indexed by the Coinbase x402 Bazaar after its first successful settlement. agentic.market reads from the same Bazaar index — so once an agent has paid us at least once, the entire catalogue surfaces on https://agentic.market and at the CDP discovery API. No registration form, no approval step.

# After our first mainnet settle, this returns every cc0.company service:
curl "https://api.cdp.coinbase.com/platform/v2/x402/discovery/merchant?payTo=<X402_RECEIVER_ADDRESS>"

# Semantic search across the whole Bazaar:
curl "https://api.cdp.coinbase.com/platform/v2/x402/discovery/search?query=cc0+image+generation&network=eip155:8453"

# Browse from agentic.market:
curl "https://agentic.market/v1/services/search?q=cc0"

The CDP catalogue refreshes on a ~6-hour schedule. Newly-deployed services may take a refresh cycle to appear after their first settle. Re-run the validator if a service appears missing — it will show whether the issue is a malformed 402 challenge or just an indexing-cycle delay.

Status codes & job states

Live playground

Pick a model below; the commands update with that model's slug, trigger word, and an in-style example prompt. Copy the block and run it from your terminal — no SDK needed for the first 402 probe.

Full reference

Machine-readable docs for autonomous agents: