TAGBASE is trust infrastructure for physical objects. We give every item an uncopyable, easily verifiable digital identity, so anyone can confirm a product is genuine with a single tap of their phone — no app required.
This documentation is for developers building on top of that foundation. It covers the concepts you need, a quickstart to your first integration, the solutions you can assemble, and the API reference.
What you can build
The platform exposes one identity layer that many kinds of solution sit on top of:
- Verify — TAGBASE’s own anti-counterfeiting product, built on this very platform. It’s the reference for what you can build, and you can use it ready-made.
- Custom — your own solution, built directly against the API the same way. That’s what this documentation is for.
The same tap-to-prove identity underpins a lot of ground: presence checks that confirm someone or something was somewhere at a given time, cashless payments at festivals, NFC signature stickers for signing documents, event access control, supply-chain track & trace, and digital product passports. Each is a different way of reading the platform’s trust signals.
How verification works
Each item carries a dynamic NFC tag. Unlike a static tag, whose data never changes and can therefore be copied onto a blank tag, a dynamic tag produces fresh proof on every tap. The platform checks that proof and returns a trusted result in milliseconds.
A copied tag can only ever replay what it captured once, so it cannot keep producing fresh proof — which is what lets the platform tell a genuine item apart from a clone.
Where to start
- Two-scan liveness — why proving a tag is live is the strongest authenticity signal.
- Resource model — how accounts, tags, sessions, and verifications relate.
- Get started — your first verification in three API calls.
- Building a solution — an end-to-end walkthrough on top of the platform.