Build on KURV.
Bring collections to your site. Connect your agent. Create your own mint experience.
Your agent, your account.
Log in to your KURV account and approve permissions. Your agent prepares the work; you review and sign the launch.
Choose your agent clientRemote HTTP MCP with OAuth.
Public data. Your interface.
Read collection settings, mint counts and Vault figures. Public reads need no account or API key.
GET /api/v1/collections?limit=20GET /api/v1/collections/84532/{address}GET /api/v1/contracts/kurvdropMint inside your own site.
Connect the visitor's wallet, get a fresh quote, approve the coin the mint costs and confirm the transaction receipt.
Direct mint integrationYour collection, on your site.
This live example is Woof Pack. The widget fits desktop and mobile. Mint opens KURV in a new tab for wallet approval.
MCP reference.
Eleven tools, a builder guide and a collection prompt. No model training required.
Tools, limits and account permissions
kurv_accountCheck your connected wallet, permissions and invitation.
kurv_builder_specGet the generative layers schema and limits.
kurv_validate_collectionCheck collection settings and trait requirements.
kurv_create_collectionStore your collection draft with a stable retry key.
kurv_list_draftsFind drafts owned by your connected account.
kurv_upload_traitUpload a real PNG, JPEG or WebP trait image.
kurv_preview_collectionInspect trait recipes, rarity and required art.
kurv_prepare_launchGet the creator review and wallet approval link.
kurv_list_collectionsRead the public collection catalog.
kurv_get_collectionRead a collection, chain figures and contract links.
kurv_embed_codeGet a collection widget and integration links.
Up to 1,000 pieces, 12 layers and 120 traits. Still PNG, JPEG or WebP traits must match the canvas and stay within 2 MiB each. Fixed price, mystery and rising price sales are supported. Auctions and animated art are outside this connector version.
The KURV account flow creates or connects your wallet. Creating collections, uploading traits and preparing launches require an invitation. Access lasts one hour; the connection grant expires seven days after its initial authorization-code exchange.
Reuse the same idempotency key when retrying a draft request. Approve only the permissions you need, and revoke access when finished, from your MCP client or from My pieces under Connected agents.