> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vibechain.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Build with the vibe.market API

> Choose the right vibe.market endpoints, credentials, and integration flow

The vibe.market API covers the same production resources used by the web app:
games, packs, card metadata, creator drafts, allowlists, collection activity,
chat, price history, leaderboards, and platform analytics.

<Card title="Open the complete API reference" icon="brackets-curly" href="/api-reference/vibemarket-intro">
  Browse every operation, parameter, request body, response schema, auth rule,
  status code, and cache note.
</Card>

## Start with the resource you need

| Goal                          | Recommended operation                                       |
| ----------------------------- | ----------------------------------------------------------- |
| Discover launches             | `GET /featured`, `GET /games`, or `GET /search`             |
| Resolve one game              | `GET /contractAddress/{contractAddressOrSlug}`              |
| Read a wallet's packs         | `GET /owner/{address}`                                      |
| Read recent activity          | `GET /recent` or `GET /collection/{contractAddress}/events` |
| Read cards and odds           | `GET /contractAddress/{contractAddressOrSlug}/all-metadata` |
| Build a creator autosave flow | `POST /metadata/draft/poll`                                 |
| Manage a gated launch         | `/metadata/draft/whitelist/*`                               |
| Check post-deploy processing  | `GET /contractAddress/{contractAddressOrSlug}/ready`        |
| Recover a missed transaction  | `POST /events/{txHash}`                                     |
| Build analytics               | `/price-chart/*`, `/leaderboard*`, and `/platform-stats`    |

## Credentials

Most reads require `API-KEY`. Creator and recovery writes require both
`API-KEY` and `Authorization: Bearer <token>` because the server also checks
the account's linked wallets.

The public OpenSea metadata routes need no credential. Reports and platform
stats are Bearer-only. The reference marks these exceptions per operation.

## Production integration rules

* Preserve Wei values as decimal strings until converting with a big-integer or
  decimal library.
* Treat cursor values as opaque and follow the returned cursor until it is
  absent.
* Expect short server caches on feeds and longer caches on stable metadata.
* Back off with jitter after `429`; a missing or invalid API key deliberately
  uses the same status as an exhausted API-key quota.
* Inspect body states on HTTP `200`. Pending rarity, slug availability,
  readiness, refresh cooldowns, and missing receipts are not transport errors.
* Persist draft IDs and deployment transaction hashes so creator flows can be
  resumed safely.

The production base URL is:

```text theme={null}
https://build.vibechain.com/vibe/boosterbox
```

Create a free API key and see runnable examples in the
[API introduction](/api-reference/vibemarket-intro).