# Choose your integration

Start with the experience you want to build. Each path connects a working example to the concepts, method reference and troubleshooting you will need as the integration grows.

## Pick your path

| Build this | Start here | Go deeper |
| --- | --- | --- |
| A mint experience on your own website | [GraveMint quickstart](https://docs.deads.io/guides/quickstart.md) | [SDK guide](https://docs.deads.io/sdk/gravemint.md) · [Methods & types](https://docs.deads.io/sdk/gravemint-reference.md) |
| A marketplace collection or activity view | [GraveMarket quickstart](https://docs.deads.io/sdk/gravemarket.md#quick-start) | [SDK guide](https://docs.deads.io/sdk/gravemarket.md) · [Methods & types](https://docs.deads.io/sdk/gravemarket-reference.md) |
| An integration with an AI coding agent | [MCP installation](https://docs.deads.io/tools/mcp.md#install) | [Available tools](https://docs.deads.io/tools/mcp.md#tools) |
| Direct HTTP integration | [GraveMint v1](https://docs.deads.io/api/gravemint-v1.md) · [GraveMarket v1](https://docs.deads.io/api/gravemarket-v1.md) | Parameters, request snippets and response examples |

> **TIP: JavaScript or TypeScript?**
Start with the SDK. The API consoles provide SDK calls in both languages; cURL is available when you need to inspect the HTTP request. The SDK guides document runtime requirements and configuration.

## Build a mint experience

1. **Get access.** GraveMint partner keys are invite-only. Read [key classes, origins and collection scope](https://docs.deads.io/guides/keys.md) before choosing a key for your browser or server.
2. **Read the drop.** Follow the [quickstart](https://docs.deads.io/guides/quickstart.md#read-a-drop), then understand [phases, price display and capabilities](https://docs.deads.io/concepts/read-model.md). An unknown price is not zero.
3. **Connect a signer.** Follow [wallets and signing](https://docs.deads.io/guides/signing.md). Your wallet signs; the server validates and broadcasts. Check the batch and session-expiry sections before handling more than one mint.
4. **Build the UI.** Use the [React mint panel](https://docs.deads.io/recipes/react.md) as a starting point and read its limitations. It is not a complete application.
5. **Handle failure.** Use the [error reference](https://docs.deads.io/guides/errors.md), [SDK retries](https://docs.deads.io/sdk/gravemint.md#errors-and-retries) and [troubleshooting guide](https://docs.deads.io/guides/troubleshooting.md).

## Build with marketplace data

1. **Install the client.** Follow [installation and the first request](https://docs.deads.io/sdk/gravemarket.md#install), including the SDK's current API-key guidance.
2. **Choose identifiers.** Read the [marketplace model](https://docs.deads.io/concepts/marketplace-model.md): collection identifiers, item identifiers, nullable prices and chain-specific data matter.
3. **Read the data you need.** Use [collections, items, activity and the other namespaces](https://docs.deads.io/sdk/gravemarket-reference.md). The current SDK is read-only.
4. **Build a collection view.** Start with the [collection-page recipe](https://docs.deads.io/recipes/collection-page.md). Keep pagination and not-listed states visible in your own UI.
5. **Handle limits and errors.** Check [SDK API-key and rate-limit guidance](https://docs.deads.io/sdk/gravemarket.md#api-keys), [pagination](https://docs.deads.io/sdk/gravemarket.md#pagination) and [error handling](https://docs.deads.io/sdk/gravemarket.md#error-handling).

## Know what each page gives you

| Documentation | Use it when you need… |
| --- | --- |
| Quickstarts | A first request and the order to build in |
| Concepts | Meaning of fields, units, prices, phases and pagination |
| SDK guides | Installation, configuration and practical usage |
| Method references | Public signatures and types for the documented package version |
| API references | Paths, parameters, HTTP examples and request/response inspection |
| Recipes | A larger starting example, with its limitations explained |
| Errors and troubleshooting | A specific failure and what to check next |

## Version and deployment compatibility

The reference pages describe the **published packages**, not the deployment state of every API environment. Check your lockfile and target API before adopting a new field or behavior.

These docs cover GraveMint **1.3.0**, GraveMarket **0.3.1** and MCP **0.3.1**. Check the target environment when upgrading: package and API releases can happen separately.

- Check server support for public identifiers in mint preparation, minted-history pagination, unknown-outcome handling and the updated supply fields before relying on them.
- Preserve `available: null` as unknown/open-ended supply, and keep burned counts distinct in your presentation.
- An uncertain mint outcome is not permission to retry. Follow the [SDK mint flow](https://docs.deads.io/sdk/gravemint.md#minting), retain session identifiers, and check the wallet before starting again.
- Connect through the [hosted MCP server](https://docs.deads.io/tools/mcp.md#connect-remotely) at `https://mcp.deads.io/mcp`, or run the published package locally over stdio. Both options use the same documented tool contract.

## Before you ship

- Confirm the package version shown on the SDK page matches your integration.
- Test loading, empty, error and paginated states rather than only a populated response.
- Preserve chain and currency information; do not display a missing price as free.
- For mint flows, check origins, key scope, signing, session expiry and unsupported capabilities.
- Keep private keys and server credentials out of browser bundles. See [keys and origins](https://docs.deads.io/guides/keys.md).

Continue with [GraveMint](https://docs.deads.io/guides/quickstart.md), [GraveMarket](https://docs.deads.io/sdk/gravemarket.md#quick-start), or [MCP](https://docs.deads.io/tools/mcp.md).

---
Source: https://docs.deads.io/guides/overview
Markdown: https://docs.deads.io/guides/overview.md