Build with AI

AI app builders can write a TAGBASE integration from these docs. The builder needs three things from you: a sandbox key, a public URL for the app, and a brief that says where the key goes. This page covers all three.

Before you start

1. Sign up for a sandbox team. It is free, and its tags are virtual.
2. Create an API key on the team. Copy it once. The dashboard does not show it again.
3. Create a tag in the dashboard. Leave its URL blank, or enter the public URL of your app with {id} in it, such as https://your-app.example/t/{id}.
4. Emulate a scan on that tag from the dashboard to test the flow end to end. See Sandbox.

The brief

Paste this into Lovable, Cursor or Claude Code. Replace the bracketed values.

Build a TAGBASE scan flow in this app. Read these pages first:

https://platform.tagbase.io/docs/api/verifications
https://platform.tagbase.io/docs/guides/building-a-solution

Rules:
- The TAGBASE API key lives on the server only. Store it as a secret, for
  example a Supabase edge function secret. Never put it in browser code.
- Base URL: https://platform.tagbase.io/api/v1
- A tag opens a URL on this app that contains the tag id. Read the id from
  the path. Do not invent, hard-code or guess a tag id.
- A tag id starts with tag_. Check the prefix before you call the API.
- Forward the query string of the tap, unchanged, as the attributes of
  POST /api/v1/tags/:tag_id/verifications.
- If the API returns 404 or 422, show a clear message. Do not retry.
- Do not add a field where a user types a tag id. A tap is the only way to
  get a valid scan.

API key: [paste the sandbox key into the secret store, not into the prompt]

The brief tells the builder where the key goes. Keep the key out of the prompt text itself.

Test the sandbox flow

1. Open the app’s public URL from a tag’s URL on the dashboard, or emulate a scan from the tag’s row.
2. Check that the page shows the verdict. A first scan shows pending. A second scan completes with valid.
3. Check the dashboard. The verification appears there as it happens.

Go live

Only the key changes between sandbox and production. The base URL stays the same.

1. Ask TAGBASE for a production team. Contact TAGBASE.
2. Create a production API key and replace the key in your secret store.
3. Create new tags on the live team and write them to chips with the Writer app. Sandbox tag ids do not exist on a live team.
4. Test with a real chip before you hand the app to customers.

Common mistakes

• A made-up tag id. The API answers with 404. Use a tag id from the tap URL, GET /api/v1/tags, or the dashboard.
• Filling in {id} yourself. Leave {id} in the url when you create or update a tag. The platform fills it in. Don’t build your own links from the template either. Read the tag id from the path your scan handler receives.
• The key in browser code. Anyone who opens the page can copy it. Move the call to the server.