Publisher Guide
Registering a listing also puts a payment check in front of your endpoint: the gateway returns402 to unpaid callers and only forwards paid requests to your
origin. If your goal is to gate a skill, download, or service behind payment,
see Payment Checks.
Signed wallet headers
Management routes use signed wallet headers:x-wallet-addressx-wallet-signaturex-wallet-timestampx-wallet-nonce
Register a listing
UsePOST /v1/apis/register to publish a community API.
pending.
Publishing is gated on operator review. A provider cannot put a listing straight into active: any provider-initiated transition to active is rewritten to pending, submitted_for_review_at is stamped, and the listing stays hidden from the catalog and serves no traffic until an Apiosk admin approves it. See Publisher Lifecycle.
Manage your listings
Use these routes after registration:GET /v1/apis/mine?wallet=<0x...>to list your APIs and earnings summaryPOST /v1/apis/:slugto update price, description, endpoint URL, activation state, or listing metadataDELETE /v1/apis/:slug?wallet=<0x...>to deactivate a listingPUT /v1/apis/:slug/endpoints/docsto attach public endpoint docs and schema hints
Listing metadata
Uselisting_metadata for agent-facing discovery fields such as:
- input and output schemas
- operation hints
- tags
- default operation
- price and latency metadata