THE DOCS.
Build collections. Publish verifiable artwork. Connect on-chain culture to AI agents.
Overview
Mintbay is a playground for creating, launching and collecting fully on-chain generative pixel NFT collections.
CREATE
Make pixel artwork, layers and traits in Studio.
PUBLISH
Store a verifiable configuration and artwork build.
DEPLOY
Prepare agent-assisted on-chain deployment with explicit approval.
Every eligible CC0 collection can become a creative reference for future remixes. We are building toward AI-assisted generation, not claiming it is already available.
Quickstart
Go from pixels to an immutable build manifest in three moves.
- 01 / Create
Visit Studio ↗. Draw artwork, create layers, adjust rarity, and preview combinations.
- 02 / Publish
Publish through Studio to create a build manifest with file URLs and SHA-256 hashes. Publishing a build is not deploying a contract.
- 03 / Verify
Read the manifest and its referenced config, artwork and compiled artwork. Verify hashes before any code generation or deployment.
curl https://api.mintbay.fun/v1/builds/YOUR_BUILD_IDArchitecture
Mintbay separates creative data, verification and blockchain execution.
Studio creates artwork and settings. Mintbay API validates and stores immutable build artifacts in Cloudflare R2. A compatible agent can retrieve and check the data. A collection deployer, once implemented and tested, will compile and deploy Solidity after a human approves the transaction.
A stored build manifest is not a verified Solidity compilation and does not prove that an NFT has been deployed.
Studio Builds
An immutable build is a snapshot of the artwork and the collection's proposed configuration.
The manifest records a build ID, selected chain, draft status, template information and three file references. Each artifact has a SHA-256 hash.
{
"schemaVersion": 1,
"status": "draft",
"chainId": 4663,
"template": { "name": "mintbay-net-collection-template", "version": "v5", "verified": false },
"files": {
"config": { "url": ".../config", "sha256": "..." },
"artwork": { "url": ".../artwork", "sha256": "..." },
"compiledArtwork": { "url": ".../compiled-artwork", "sha256": "..." }
}
}Old build manifests may reference api.mintbay.xyz. Keep those references valid and do not rewrite already-published artifacts.
API Reference
Read published builds and discover registered collections through the public Mintbay API.
/healthService status/v1/builds/:idBuild manifest/v1/builds/:id/configCollection settings/v1/builds/:id/artworkOriginal art data/v1/builds/:id/compiled-artworkCompiled pixel traits/v1/collectionsDiscovered collections after first mint/v1/buildsAuthenticated publish endpoint/v1/deploymentsAuthenticated receipt-based registrationconst res = await fetch("https://api.mintbay.fun/v1/builds/YOUR_BUILD_ID");
const manifest = await res.json();
console.log(manifest.files);Uploads and deployment registration require server-side credentials. Never expose upload tokens or private API keys in a client-side app.
Smart Contracts
Mintbay's V5 design centers on lifetime supply, transparent mint economics and optional collection mechanics.
Planned protocol rules include ERC-721A lifetime supply accounting, public minting, creator allowance, optional holder claim, Burn & Claim, One Shot and supply reduction. A 5% platform fee is intended for paid primary mints; free mints are not charged that fee.
Mintbay also plans integration with Net Protocol for app-indexed on-chain collection activity. Deployment, bytecode verification and royalty-validator availability must be checked per chain.
The current /v1/builds/:id/bundle route returns HTTP 501. Do not treat a draft manifest as deployable source or ask an agent to execute an unverified contract.
Built on Net Protocol
Net Protocol is a decentralized on-chain messaging layer. It gives applications a public, queryable activity stream anchored to the blockchain.
Mintbay's Net-integrated collection design uses the collection contract as the Net app. Mint and transfer activity can be published as messages indexed under that contract address, creating an open record other apps can query or build on.
Application messaging
Net exposes sendMessageViaApp so a smart contract can publish a message attributed to an app and sender, with a text body, topic and bytes payload. The protocol indexes by app, sender and topic. Mintbay's precise emitted topics and chain deployments depend on its final collection contract.
interface INet {
function sendMessageViaApp(
address sender,
string calldata text,
string calldata topic,
bytes calldata data
) external;
}Net's official docs list deployed networks and contract addresses. Do not assume Net is available on every Mintbay Studio chain without confirming its deployment first.
Bankr Agents
Bankr provides an AI agent runtime with wallets, tool access and smart-contract execution capabilities.
The intended Mintbay workflow is simple: publish a build, hand its URL to an agent equipped with the Mintbay skill, verify the source artifacts, review the proposed contract and approve any transaction explicitly.
Example agent request
Hey @bankrbot, review my Mintbay build:
https://api.mintbay.fun/v1/builds/YOUR_BUILD_ID
Use the Mintbay skill. Verify the files and hashes,
check the chain, fees and ownership settings.
Prepare the deployment plan but do not deploy
until I explicitly approve the final transaction.The prompt is a target workflow, not a claim that V5 deploys are currently automated end-to-end. Never share wallet private keys or approval credentials in public posts.
CC0 & Remix
Creative reuse is part of the design — and provenance still matters.
Mintbay aims to let eligible CC0 pixel collections become reference material for remixing palettes, traits and compositions. Future Studio AI tools may help turn a prompt into editable collection JSON and support experimentation with styles.
Artwork created and published through Mintbay is intended to be dedicated under CC0 only when the creator has the necessary rights and makes that commitment. Third-party works are not automatically CC0.
READ THE MANUALSupported Chains
Studio currently allows six EVM chain selections for draft configuration.
46638453113713042161Chain selection does not guarantee that the V5 template, Net Protocol contract or a royalty enforcement validator is deployed and supported there. Check individual integrations before execution.
What’s Next
The docs will grow alongside the working protocol.
Pixel art editing, draft publishing, hashes and build retrieval.
Solidity generation, reproducible builds, tests and agent review.
Community CC0 references, palette transformations and editable agent-generated artwork.
Docs are evolving. Verify critical behavior against live contracts and published source.