New from WispAyr · early access

One QR code.
Read by people and AI agents.

Tag gives every physical thing (a van, a rack, a receiver, a camera sign) one printed code. A phone camera gets a clean page. Your crew get live status and safety rules. An AI agent gets structured data it can act on. It's the same code every time, and who's asking is worked out when it's scanned.

No app and no login for the public. Demo tags on this site use placeholder data.

Phone cameraHuman
WispAyr · DEMO
CSU van
Mobile comms unit · placeholder
Status● Operating
OperatorWispAyr
Emergency999
Report a problem
Same URL, as JSONAgent
{ "id": "wispayr/csu-01", "tier": "public", "object": { "type": "vehicle", "name": "CSU van" }, "public": { "status": { "state": "ok" } }, "agent": { "rules": ["read-only"], "contact": "…" }, "actions": ["report_problem"] }
← for people
for agents →
How it works

Print once. Answer everyone properly.

The code only carries a web address with an ID in it, so there are no secrets on the sticker. Everything else is decided by our server when the code is scanned.

1

Tag it

Add the object in the admin, fill in what the public may see and what crew need, then download a print-ready label as PNG or SVG, e.g. "CSU-01 · scan for info".

2

Scan it

Any phone camera opens a fast mobile page. An agent fetches the same URL and asks for JSON, or reads the JSON-LD embedded in the page. Nobody needs an app.

3

Right answer, right person

The public get the safe basics. Signed-in crew see live status, how-tos and safety rules. Every scan is logged as a time and device type, which gives you a free "someone was here" signal.

Dual purpose

One code, three audiences

Most QR codes are a dead link to a brochure. A Tag gives each person the answer they're allowed to see.

Anyone with a phone

Public page

Clean, fast and accessible, and it works on any camera app.

  • What it is and who runs it
  • A safe public status
  • Report a problem in a few taps
  • Emergency guidance
  • CCTV privacy notice where it applies
Signed-in crew

Crew tier

The same page, with more on it once you're signed in.

  • Live status from your systems
  • How-tos and checklists
  • Safety rules before anyone touches anything
  • Previous scan time
  • Edit in place (owners)
AI agents & scripts

Machine-readable

The same URL, read as structured data.

  • Content negotiation or a .json URL
  • JSON-LD embedded in the page
  • Feed endpoints and rules of engagement
  • Which agent or team to talk to
  • A typed "report a problem" action
Use cases

Anything with an owner and a reason to be asked about

Fleet & vans

Scan at the door to see what the vehicle is, who to call, and what's running inside before you open a cabinet.

  • Operator and callout contact
  • Crew checklist and safety rules
  • Live systems for crew

Broadcast studios

Every screen, desk and rack says what it's showing and why, so a relief operator isn't guessing at 6am.

  • "What is this screen?" in one scan
  • Fault reporting that lands with the right team

Server racks & comms cabinets

What is it, what depends on it, and what breaks if you unplug it.

  • Dependencies for crew only
  • Site visit log from scans

CCTV signage

The sign becomes the privacy notice: who operates the camera, why, how long footage is kept and how to ask about it.

  • Plain-English notice for the public
  • Health and firmware for engineers

Events & venues

Gates, generators, first-aid points and radio kit, all tagged, with fault reports and incident-ready info for stewards.

  • Short-lived tags per event
  • Steward-only safety briefings

Field kit & receivers

Sensors, masts and receive-only radios that explain themselves, with nothing sensitive on the public page.

  • Public: what it is, who to contact
  • Crew: health and live feeds
For agents

Built so an AI can understand the physical world

Hand an agent a photo of a Tag, or the URL, and it gets a typed description of the object, its owner, its public facts, the feeds it may read, the rules it must follow and who to talk to. The answer is the same data a person sees, without any scraping.

  • Accept: application/json on the tag URL, or add .json
  • schema.org JSON-LD in every page
  • /llms.txt describes the platform for models
  • Rate limited and read-only, so agents can look but not change anything
TerminalDemo tag
$ curl -H "Accept: application/json" \ https://tag.wispayr.online/t/wispayr/csu-01 { "id": "wispayr/csu-01", "demo": true, "tier": "public", "tenant": { "slug": "wispayr" }, "agent": { "rules": [ … ], "feeds": [ … ] }, "actions": [ { "name": "report_problem", "method": "POST" } ] }
Multi-tenant · white-label

Your brand, your namespace, your people

Each organisation gets its own space at /t/your-org/… with its own logo and colours, its own objects, and its own owners and crew. Queries are strictly separated by organisation, so one tenant can never see another's tags, scans or reports.

  • Owners manage branding, tags and people
  • Crew see the extra tier on every tag in their organisation
  • Printable labels carry your colours

Privacy & safety by design

  • The code is an ID, never a password or a secret
  • Scan log keeps time, tier and device type only. No IP addresses and no identities
  • Crew details only after sign-in, decided at scan time
  • A leaked or photographed code still only shows the public page
  • Public pages never show sensitive specifics such as frequencies or network details
  • Scan and report endpoints are rate limited
Try it

Demo tags

These are live tags in the wispayr demo tenant. Everything on them is placeholder data. Scan them from your phone or open them here. Add .json to see what an agent sees.

Questions

Good to know

Do people need an app?

No. Any phone camera opens the tag as a normal web page.

What if someone copies or photographs a code?

They get the public page, the same as anyone. Crew information only appears for someone signed in to that organisation at the time they scan.

What do you record when someone scans?

A timestamp, which tier was served (public or crew), the format (page or JSON) and a coarse device type such as "mobile" or "ai-agent". We don't store IP addresses or raw browser details.

Can it show live data?

Yes, for crew. Tags can list live feeds from your systems. WispAyr's own tags point at Crosspoint feeds.

How much does it cost?

We haven't set pricing yet. We're working with early users first. Get in touch and tell us what you'd tag.

Get in touch

Tell us what you'd tag

Vans, studios, racks, signs, a whole venue? Leave your details and we'll get back to you. We only use them to reply.

WispAyr · Ayr, Scotland