Andamio Issuer
Low-code, verifiable credentials for the systems you already run
This is the enterprise-key path
These docs cover the Andamio Issuer, which uses an enterprise key: Andamio sponsors every transaction and your application is the only credential the API needs. Hold a developer key instead (you build on /api/v2 and fund your own transactions)? See the API docs.
Andamio Issuer is in active development. This section is a scaffold: the shape is settling, and detailed guides will land as the product firms up.
Andamio Issuer adds a verifiable credential layer on top of the programs your organization already runs. It is built on the Andamio API and abstracts the blockchain away entirely: no wallets, no tokens, nothing new for you or the people you credential to learn.
You get what a public ledger guarantees, a credential you control that anyone can verify, without anyone having to understand the chain underneath.
Who it's for
Organizations that issue credentials and need them to mean something to whoever relies on them: an employer, a partner, or their own team. If you run a certification program, a training track, or a partner program today, Issuer turns the badges you hand out into credentials your systems, and others, can act on.
Why it's different from a badge
A typical digital badge is a picture in a vendor's database. It can be changed, switched off, or lost, and most badges carry no data a system can read. An Andamio credential is the opposite:
Persistent
Immutable and on public infrastructure. It outlives whoever issued it.
Useful
Machine-readable. Your systems can verify it and act on it.
Private
Proof is public and verifiable; the work behind it stays private.
Owned by the earner
It belongs to the person who earned it, and travels with them.
How it works walks through the full credential model.