Most location APIs return fields: a normalized address, a latitude and longitude, a flood-zone code, a census tract, a delivery score. Those fields are useful, but they leave the decision to the caller.
A verdict is one step further. It is a structured, decision-ready output derived from one or more location signals. The verdict is the answer the calling system can act on.
Signals → verdict → receipt
The pipeline is consistent for every GeoClear call:
- Input, an address, a coordinate, or a structured query.
- Signals, address validation, geocoding, rooftop precision, parcel + census context, flood and climate signals, risk scoring, compliance fields.
- Verdict, a deterministic, decision-ready object: validated, scored, classified, and ready for the calling system to act on.
- Receipt, a cryptographic record of the verdict: what input, what signals, what result, at what time, signed.
The verdict is not just a bundle of fields. It says:
Given this input, at this time, using these signals, GeoClear returned this result.
Field vs verdict vs signed verdict
- A field is data:
flood_zone: "X". - A verdict is something a system can act on:
{ flood_zone: "X", sfha: false, deliverable: true, fraud_score: 0.04 }. - A signed verdict is something a system can act on and later verify, the same object, plus an
X-GeoClear-Receiptheader binding the response to a public-key signature.
Why this matters in practice
For human-in-the-loop systems, fields are usually enough, a person reviews the data and makes the call.
For agentic systems, fields force the agent to interpret. Different agents may reach different conclusions from the same fields. The verdict removes that variance: the API decided, the agent acts on the verdict, and the receipt records what the verdict was.
For audit-heavy workflows, mortgage compliance, insurance underwriting, drone dispatch, fraud review, the verdict + receipt becomes the durable record of what the system relied on at the moment of decision.
What a verdict does not mean
A verdict is not a guarantee that the underlying ground truth is perfect. If FEMA updates a flood-zone boundary six months from now, an old verdict is still valid, it accurately records what GeoClear returned on the day you asked. The receipt attests to the API's response, not to absolute physical reality.
That distinction is deliberate. It is the right boundary for auditability without overclaiming what cryptography can prove about the world.
Try it
, Shailesh, founder at GeoClear
More: All resources · Architecture whitepaper · Why agents need signed verdicts