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	SDK guide · Methods & types
A marketplace collection or activity view	GraveMarket quickstart	SDK guide · Methods & types
An integration with an AI coding agent	MCP installation	Available tools
Direct HTTP integration	GraveMint v1 · GraveMarket v1	Parameters, request snippets and response examples

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 before choosing a key for your browser or server.
2. Read the drop. Follow the quickstart, then understand phases, price display and capabilities. An unknown price is not zero.
3. Connect a signer. Follow wallets and signing. 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 as a starting point and read its limitations. It is not a complete application.
5. Handle failure. Use the error reference, SDK retries and troubleshooting guide.

Build with marketplace data

1. Install the client. Follow installation and the first request, including the SDK's current API-key guidance.
2. Choose identifiers. Read the marketplace model: 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. The current SDK is read-only.
4. Build a collection view. Start with the collection-page recipe. Keep pagination and not-listed states visible in your own UI.
5. Handle limits and errors. Check SDK API-key and rate-limit guidance, pagination and 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, retain session identifiers, and check the wallet before starting again.
• Connect through the hosted MCP server 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.

Continue with GraveMint, GraveMarket, or MCP.