Introduction

EBG Tokenizer is a tokenization system for EBG certificates on Ethereum: smart contracts on Arbitrum plus a hosted HTTP API at https://ebg-tokenizer.u3dev.deno.net/ so you can create ERC-721 certificate collections, mint NFTs with rich metadata, and expose standard token URI metadata to wallets and marketplaces.

What you can do

• Create a collection — Deploy a new certificate contract (one ERC-721 collection) through the onchain factory, or via POST /factory/certificates on the HTTP API.
• Mint certificates — Each token stores a structured certificate record (participant, course, institution, URLs, etc.). Mint through the factory onchain or through POST /certificates/:address/mint on the API.
• Read and update metadata — Query onchain data or use GET routes; updates go through the collection owner (onchain) or authenticated API writes, depending on your setup.
• Metadata for wallets — Align base_uri with GET /metadata/:chainId/:addressOrCertificateId/:tokenId so tokenURI resolves to ERC-721 metadata JSON.

How the pieces fit together

1. Factory — Registers certificate contracts, enforces a global mint cap, and exposes create_certificate and mint_certificate for addresses with MINTER_ROLE.
2. Certificate collection — Each deployed collection is an ERC-721 with per-token certificate structs, enumerable tokens, and permit support.
3. HTTP API — JSON endpoints under /factory, /certificates, and public /metadata for integration without wiring RPC in every client.

For diagrams and roles, see Architecture. For request and response details, start at HTTP API overview.

Where to go next

Topic	Page
System diagram, factory vs collection	Architecture
Wagmi / ABI snippets	Frontend integration
Roles, events, deployment concepts	Contracts overview
Struct fields (API + chain)	Certificate data model
curl examples, auth, base URL	API overview