Get source evidence

Source evidence validates opaque references from prior factual responses and expands them into safe, display-ready official verification routes for people.

Start free

When to use it

Validate fact source references, then return official human-facing D.C. sources with exact lookup inputs and a safe fallback. Present sources to users; evidence is internal audit data. Does not return ArcGIS REST, JSON, or session-bound URLs.

Pass one to 50 source references exactly as returned. The example token below is schematic; replace it with an unmodified source_ref from a factual tool response.

Input contract

These inputs and limits are pinned to the production v0.4.6 server contract. Omitted optional values use the documented defaults.

Input contract table
Input	Contract
source_refs	required; array; min items 1; max items 50; item: string; min length 1; max length 192

{
  "source_refs": [
    "SOURCE_REF_FROM_A_PRIOR_RESPONSE"
  ]
}

Response and verification

Successful sourced responses preserve effective dates, typed null meaning, source references, quality flags, and exact-versus-contextual property-link scope.

Use the display-ready sources for a visible Source or Verify action. Responses return each field with a source reference that can be checked against the official portal. See Source citations and verification for the evidence format.

Limits

Edited, malformed, stale, or mismatched references reject the request.
Do not expose machine-facing evidence as the end-user verification view.
ArcGIS REST, JSON, raw download, and session-bound URLs are excluded.