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 authorized 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
Put collection art and a Mint button on another site	Collection embeds
Build a mint experience using your own wallet connector	Mint from your site

Endpoints and network

These developer integrations use Base Sepolia, chain id 84532, and no other network.

Entry point	Address
Remote MCP endpoint	https://mcp.kurv.fun/mcp
Public API discovery	https://testnet.kurv.fun/api/v1
Collection catalog	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 authorize 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 PNG, JPEG or WebP trait images. The connector supports up to 1,000 pieces and 2 MiB per trait image. It returns trait recipes and rarity for inspection.
5. Prepare the launch and open the returned review URL yourself. Review and import the real art, render and publish through KURV, then approve wallet transactions.

The connector has eleven tools, the kurv://builder-guide resource and the build-kurv-collection prompt. These teach an agent the workflow without a new model training job. The agent creates and prepares drafts; the creator keeps wallet approval. A collection is deployed after its deployment transaction is confirmed, not when kurv_prepare_launch returns a link.

See Connect an agent with MCP for permissions, exact tool inputs, retry behavior 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 KURV in a separate tab for the buyer’s account and wallet approval. This handoff works without relying on account cookies inside an iframe.

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.