Home
Andamio is a credentialing solution: a way for groups of people to issue, earn, and verify proof of real work. Credentials live on public infrastructure, the Cardano blockchain, which keeps them permanent and independently verifiable, and lets them outlast the apps that issue them.
There are two ways to build with Andamio, plus a live app to see it in action.
API
The developer product. Read, mint, and gate credentials in your own app or system.
Issuer
Low-code credentialing for organizations. Add verifiable credentials to programs you already run, with no wallets or tokens to manage.
Explore the app
Take a course, complete work, and earn a credential. Built entirely on the Andamio API.
Two products, one protocol
Andamio API wraps the on-chain protocol into endpoints you build on. Most developers work at this level; you can also transact against the smart contracts directly. See Building on Andamio.
Andamio Issuer is built on the API and abstracts the chain away entirely. It adds a verifiable credential layer to the systems an organization already runs, with no wallets or tokens for anyone to learn.
The app at app.andamio.io is a reference implementation on the API, open to anyone who wants to explore.
Two keys, two paths
Andamio API and Andamio Issuer are two products with two different API keys, and the key you hold decides which one you build against.
Andamio API uses a developer key. You build directly on the protocol under /api/v2: read, mint, and gate credentials in your own app. Your users sign in and act on their own behalf, and you fund the transactions you submit.
Andamio Issuer uses an enterprise key. You issue credentials under /issuer/v1, and Andamio sponsors every transaction, covering the on-chain fees. Your application is the only credential the API needs, so there are no end-user wallets or tokens to manage.
The two keys aren't interchangeable. A developer key calling an Issuer route, or an enterprise key calling a developer route, is rejected (HTTP 403). So follow the section that matches your key: the API docs for a developer key, the Issuer docs for an enterprise key.
What makes an Andamio credential different
Persistent. Immutable and stored on public infrastructure no single company owns. A credential outlives whoever issued it.
Composable. One credential can be required before someone earns the next, so credentials build on each other instead of piling up.
Useful. Machine-readable. Software can verify that someone holds a credential and act on it: gate access, unlock the next step, or drive what an app does.
Private. The proof is public and verifiable; the evidence behind it stays with the person who earned it.
Open. Anyone can issue. A credential makes no claim about its own value; value comes from use.
Owned by the earner. It lives with the person who earned it, not in the issuer's system, and they can carry it anywhere it is useful.
To see what others are building, join Andamio Pioneers.