Skip to main content
vibe.market is an experimental protocol. Creating a pack involves smart-contract and market risks. Read the Terms; artwork preparation and announcements do not guarantee a launch, liquidity or returns.

​
Draft and announce

For agent-assisted creation, begin with the canonical skill.md, our single agent instruction file. This page remains the creator API reference. Send your registered API-KEY alongside the wallet signature described here. Creator writes and uploads share the write budget; a key does not confer creator permissions. See authentication and limits. Submit wallet-signed actions to POST /releases. Supported actions are mine, load, save, publish and wishlist; use the exact signed envelope and message in the operation schema. A release contains an ID, revision, name, symbol, cover image, color, description, artwork design, planned launch time and status. Announcements require a name, alphanumeric symbol and launch time. The time is a Unix-millisecond timestamp. Public and list responses can set cardsOmitted: true. Load the complete draft with {"kind":"load","id":"..."} before saving or publishing. Do not save a summary over the full artwork. Preserve revisions; reload and reconcile when another device has edited the draft. Publishing an announcement is offchain. It does not deploy a contract or launch a pool.

​
Prepare launch artwork

Discover the currently configured launchTarget first. POST /runtime/{version}/prepare accepts multipart form data: Odds must total 10000 basis points, multipliers must strictly increase, and the computed round-trip return after trading fees must not exceed 95%. Each file is PNG, JPEG, WebP or GIF and at most 4 MiB. The request is bounded to 12 MiB total, 512 KiB fields and nine files. Multipart overhead counts toward the request limit. The response contains baseURI, packArt, tierArt and createParams, including decimal-string ethPerPackWei. Preparation stores artwork; it does not execute the returned parameters onchain. The contract and current launch configuration can impose additional restrictions. An alternative creator workflow uses published release artwork. Do not mix its artwork format with the board-preparation format or reconstruct a metadata URL by guessing its hash.

​
Launch explicitly

Verify the current contract graph and contract-specific creation ABI. The contract ABI guide explains compact https://vibechain.com/abis/vibemarket/packs/<canonical-slug>.json documents and the full public pack ABI catalog; its listed packs do not make an older deployment the current launch target. Discover launchTarget independently and require an exact graph and contract match before using a creation interface. Obtain separate wallet consent for the launch transaction, verify its receipt and wait for the correct runtime to index it. Do not identify a launch solely by matching a pack name.