Skip to main content
vibe.market is an experimental protocol. APIs, deployments and behavior can change. Indexed data can lag the chain; quotes are not execution guarantees. Read the Terms before using the product or integrating it.
This reference describes the current vibe.market. Its HTTP namespace is /api/vibemarket2; the implementation’s “2” is an API identifier, not a different product. This reference covers the supported public vibe.market HTTP API.

​
Start with discovery

Agent integration

Start with the canonical skill.md, the single source of agent instructions. Re-fetch it each session; use this API reference for endpoint schemas.
Every consumer API request requires a registered API-KEY, including public-data reads and website discovery. See key registration and limits. Set VIBECHAIN_API_KEY locally to your own key for these examples.
Use a returned runtime ID in runtime URLs. Do not guess the newest deployment from its name or silently switch an existing pack to the current launch target. Match the chain, market, factory and schema; see integration guidance.

​
API hosts

The OpenAPI reference selects the correct host for each operation. Website proxies expose only a bounded public allowlist; use the backend host for runtime and creator operations.

​
Authentication

  • Every consumer JSON/API route: API-KEY, with separate read, write and stream budgets.
  • Creator release writes: an exact, action-specific wallet signature in addition to API-KEY.
Keys identify application quota; they never replace wallet authorization. Publicly renderable website NFT metadata and image URLs are deliberate exceptions; backend lookups remain keyed. Read authentication and limits before integrating.

​
What this API does not do

HTTP preparation, announcements and wishlists cannot buy packs, launch pools, approve allowances, transfer assets, open cards or collect outcomes. Those actions require separate, explicit wallet transactions against the correct contract graph. First-party account, chat, direct-message, social-follow, invite/access and moderation workflows are not supported third-party APIs and are intentionally excluded. Provider event-ingestion webhooks, keeper internals and operator controls are excluded too.

​
Next steps

Read wallet holdings

Cards, sealed positions, pending pulls, pagination and the correct replacement for the nonexistent /user/holdings path.

Read the market

Pagination, response shapes, caching, errors and live updates.

Create a pack

Signed drafts, artwork preparation and explicit launch boundaries.

Integrate safely

Discover contracts and keep catalog and runtime identities aligned.