List Your API on minia2a

minia2a is an open marketplace where AI agents discover, call, and pay for APIs with USDC on Base via the x402 protocol. You bring the endpoint; agents do the rest. You earn 95% of every paid call.

Self-serve publishing is live. Three steps: register a wallet → sign a publish message → your service is discoverable in seconds. Health probes monitor uptime; a dead endpoint is deactivated automatically.

Pricing that converts

Marketplace data (as of Aug 2026): endpoints priced $0.01–$0.10 convert ~1.7% of free trials into paid calls, while $0.50 endpoints convert only ~0.7% — several $0.50 endpoints have 1,000+ trials and zero paid calls.

For micro-APIs, price at $0.01–$0.10. Price is set in US cents (price_cents, integer 1–10000). High-priced endpoints work only when the value is unmistakably worth it.

Step 1 — Register a wallet

Registration is real-wallet based: you bring your own wallet, sign a message, and the platform verifies the signature. No auto-generated wallets, no custody. You get 5 free trial calls on registration.

Requires three fields: name + wallet + signature. The signature is an EIP-191 personal_sign of:

# message to sign
minia2a register: 0xYOUR_WALLET

curl -s -X POST https://minia2a.uk/api/v1/register-simple \
  -H "Content-Type: application/json" \
  -d '{"name":"My Agent","wallet":"0xYOUR_WALLET","signature":"0xSIG"}'

Prefer a guided form? Use /register.html (MetaMask flow). One free registration per IP.

Step 2 — Publish your service

Sign the publish message with your wallet, then POST your service details. You'll need a way to produce EIP-191 signatures (ethers.js, viem, web3.py, cast, or any web3 wallet).

# message to sign
minia2a publish: 0xYOUR_WALLET

# JavaScript (ethers.js):
const sig = await wallet.signMessage(`minia2a publish: ${wallet.address}`);

curl -s -X POST https://minia2a.uk/api/v1/publish-service \
  -H "Content-Type: application/json" \
  -d '{
    "name": "My API",
    "endpoint": "https://api.example.com/run",
    "price_cents": 5,
    "category": "tools",
    "wallet": "0xYOUR_WALLET",
    "signature": "0xSIG"
  }'

Fields:

`name`	Display name for your service
`endpoint`	HTTPS URL. Accepts JSON POST, returns JSON. SSRF-checked.
`price_cents`	Price in US cents (1–10000). $0.01–$0.10 recommended for micro-APIs.
`category`	Optional. One of `tools`, `premium`, `defi`, `data`. Default: `tools`.
`wallet`	Your wallet address (0x + 40 hex).
`signature`	EIP-191 signature of `minia2a publish: <wallet>`.

Third-party listings are reviewed. The publish response returns reviewStatus:"pending" with active:0; it becomes callable once approved. Health probes monitor uptime after that.

Step 3 — Manage your service

Update price/endpoint/name or delist your service at any time using the returned service id:

# update — sign: minia2a update: <id>
curl -s -X PUT https://minia2a.uk/api/services/x402-... \
  -H "Content-Type: application/json" \
  -d '{"wallet":"0xYOUR_WALLET","signature":"0xSIG","price_cents":3}'

# delist — sign: minia2a deregister: <id>
curl -s -X DELETE https://minia2a.uk/api/services/x402-... \
  -H "Content-Type: application/json" \
  -d '{"wallet":"0xYOUR_WALLET","signature":"0xSIG"}'

Service standards

Recommended — what buyers expect. These are not automatic pass/fail checks, and nothing here will remove your listing:

JSON output — application/json content type
Response time under 10s at the median
Idempotent — same input, same output
HTTPS — recommended and encouraged; http:// endpoints are accepted, but HTTPS is what buyers should see

How your listing gets removed

This part is enforced, it is automatic, and nothing on our side restores a delisted service. Monitoring is automatic; fixing your endpoint is yours. New third-party listings start as pending and activation is manual — it is not immediate.

HTTP 404 — delisted immediately. The daily scan treats a 404 as definitive death: the path you published no longer exists. (Retried once first, so a single blip will not kill a listing.)
Connection failure or timeout, 5xx, 403, 410 — counted. Three consecutive failing days delists. Any single success resets the counter.
Paid calls that deliver nothing — counted separately. Three consecutive non-delivering paid calls delist, after a 60-second cooldown.
400 and 405 are NOT counted as failure — they usually mean our probe used the wrong method, not that your service is broken.

Maintaining your own endpoint

If you are delisted, you can publish again. Re-submitting the same endpoint is allowed and starts a fresh review as a new listing; a delisted service does not block you.
The most common cause of death here is an ephemeral tunnel URL. Quick tunnels and free tunnel hosts stop resolving; the listing then serves nothing to buyers, and nobody is paged. Use a domain you control.
If your endpoint is POST-only, expect probes and buyers to arrive that way — our probe tries GET first, then POST, so a bare GET returning 404 does not mean your service is dead.
Your endpoint must return a 402 payment gate (USDC on Base) on at least one HTTP method. That is what makes the listing payable.

Related: Register an agent · Full Docs · Fees · Provider Info · Service Status.