# Tokenizer Solutions

> Tokenizer Solutions lets users deploy and manage ERC20 tokens, ERC20 crowdsales, ERC721, ERC1404 and ERC1155 tokens and ERC4626 vaults on Ethereum networks through audited generator contracts, from a web dashboard (humans) or an API (AI agents). The server never holds private keys: every state change is a transaction the user or agent signs with their own wallet.

Supported networks: Sepolia and Hoodi testnets (mainnet pending). Fees: a per-network 30-day subscription paid to a SubscriptionsManager contract, plus a per-deploy fee charged by each generator contract.

## For AI agents

- [OpenAPI 3.1 document](/api/openapi.json): the full HTTP contract. Every response uses the envelope `{ success, code, message, result }`.
- [MCP endpoint](/mcp): Model Context Protocol, streamable HTTP, stateless. Without a token only the sign-in tools are exposed; reconnect with `Authorization: Bearer <jwt>` for the full tool set.
- [API catalog](/.well-known/api-catalog): RFC 9727 linkset pointing at the above.
- [Agents API guide](/agents): human-readable walkthrough, public (no login).

Sign-in: `POST /api/agents/challenge { walletAddress }` returns a message; sign it with the wallet (EIP-191 personal_sign); `POST /api/agents/login { walletAddress, nonce, signature }` returns a one-hour bearer token and creates the account on first use. No email, no captcha.

Flow: `GET /api/agents/networks` (generators, fees, subscriptions manager per network) -> `GET /api/agents/subscriptions` -> pay with the transaction from `POST /api/agents/subscriptions/{networkType}/tx` -> `GET /api/agents/tx` (families, deploy variants, operations) -> `POST /api/agents/tx/{family}/generate` -> sign and broadcast -> `POST /api/agents/tx/{family}/confirm` (the server reads the deployed contract from chain and records it) -> `POST /api/agents/tx/{family}/{address}/{networkId}/operations/{operation}` for mint, transfer, collect, terminate and the rest.

Any network-scoped request without a valid subscription answers HTTP 402 with the unsigned payment transaction in `result.transaction`.

Nothing an agent needs is behind the human login page: this file, the OpenAPI document, the API catalog, the guide and the MCP sign-in tools are public; every other endpoint takes the bearer token from the wallet sign-in above.

## For humans

- [Dashboard login](/login) and [registration](/register)
- [Generators API and contract addresses](/api)
- [FAQ](/faq), [Terms](/terms), [Privacy](/privacy)