KURV for Developers

Bring KURV collections into your own apps, websites and agent workflows. Public contracts hold the collection state. The HTTP API exposes collection configuration and chain readings, the widget shows a collection wherever you embed it, and MCP lets an authorised agent prepare a generative collection for its creator.

Choose your integration

You want to	Start here
Connect an agent and prepare collections	Connect an agent with MCP
Read collections, mint counts and contract information	Public APIs
Read KURV’s numbers with an API key: launches, mints, volume, fees, sign-ups	KURV data API
Put collection art and a Mint button on another site	Collection embeds
Put a Mint button of your own on any page, on Base or Solana	Mint from your page
Build a mint experience using your own wallet connector	Mint from your site

Endpoints and network

Base Sepolia (chain ID 84532) is the default. Explicit version: 2 and network drafts also support verified Solana Devnet and localnet deployments. Read kurv_builder_spec for the selected network before preparing a draft. The connector never holds the creator’s private key.

Entry point	Address
Remote MCP endpoint	https://mcp.kurv.fun/mcp
Public API discovery	https://testnet.kurv.fun/api/v1
Collection catalogue	https://testnet.kurv.fun/api/v1/collections
KurvDrop ABI	https://testnet.kurv.fun/api/v1/contracts/kurvdrop
Integration playground	KURV for Developers

mcp.kurv.fun is the machine service endpoint. This documentation is where the connection instructions, tool guide and integration examples live. API and iframe reads are public and need no account or API key. The agent connector uses OAuth to authorise a specific KURV account.

Create with an agent

1. Add https://mcp.kurv.fun/mcp in a remote MCP client that supports OAuth.
2. Log in on KURV and approve the client’s requested permissions. An existing invitation is required for collection writes and launch preparation.
3. Ask the agent to check the builder schema, validate the collection and create an owned draft with a stable retry key.
4. Upload actual aligned trait art: at most 240 source images including unique-only art, 20 MiB per ZIP source image, or 2 MiB per individual inline upload. Layered generation supports 1,000 pieces including uniques. Finished artwork uses kurv_finished_art_limits for current web/provider limits.
5. Open review_url as the owner, inspect the exact art and sale terms, then explicitly choose Publish and launch before any public upload. Approve the wallet signature for that immutable published snapshot. Opening a link never publishes or signs; later draft edits require fresh review. studio_url opens the editor only.

The connector has 21 tools, the kurv://builder-guide resource and the build-kurv-collection prompt. A cached client showing 11 tools needs reconnection or refreshed discovery. The agent prepares drafts; the owner approves publishing and wallet signing. A link from kurv_prepare_launch is not a confirmed deployment.

See Connect an agent with MCP for permissions, exact tool inputs, retry behaviour and supported art and sale methods.

Display and mint elsewhere

The collection widget shows real art or its public teaser and updates confirmed mint counts. Its Mint button opens a KURV window for the buyer’s account and wallet approval. This handoff works without relying on account cookies inside an iframe. The Mint button does the same from any page and tells that page when a mint is through.

For minting inline in your own site, use the collection’s contract address and the public ABI with your own wallet connector. Read a fresh quote, approve the required collection coin and any additional coin, simulate the mint and wait for its transaction receipt. Mint from your site shows the exact call and how it handles public phases, cost ceilings and auction modules.

Collection figures carry a reading timestamp. A stale figure is a previously confirmed snapshot. An unrevealed collection’s private metadata and art roots remain withheld. Contract rules, fees and the collection’s terms apply to every integration; read Fees and Risks and disclaimer.