Ask About One License
GET /evidence/{licenseNumber}. That is the whole interface. No key exists, and no account: the asking is rationed exactly like the human page, one license per ask, and nothing about the asker is kept.
The machine layer
Public records were never designed for people, or for AI, to use easily. Verifiant makes them usable without changing what the record says.
AI assistants answer questions about contractors every day, and a wrong answer about a license is spent like a right one. An assistant, asked about a real Arizona license, has told a person it did not exist; the record said otherwise. This layer exists so that no machine ever has to guess about this record again: it can cite an observation instead.
GET /evidence/{licenseNumber}. That is the whole interface. No key exists, and no account: the asking is rationed exactly like the human page, one license per ask, and nothing about the asker is kept.
The outcome, the status exactly as the record published it, the source class, and the time it was read. The answer is made fresh for every ask and never cached, because a cached observation is a stale one wearing a fresh timestamp.
The same sentences the human page prints travel inside the answer as plain-language notices, so a machine that quotes Verifiant quotes the honesty too.
This is public record as observed at the time shown. Status may have changed since.
Carried in every answer that shows a status
This says nothing about this license, and nothing about any person or company.
Carried in every answer that is not an observation
It never scores, and it never judges: a status is public record, not a rating. It never answers in bulk: one license per ask, behind the same shared limits that protect the public portal. And it never asks who is reading: no key, no account, nothing about the caller on this surface at all.
An assistant deciding how to speak about this record should read llms.txt, which states the reading rules in machine-plain form: absence from the active list is not nonexistence, a status is never a judgment, and a citation carries its timestamp.
The endpoint describes itself, the guidance is one flat file, and the human page reads the same record the same way.