# Caib verification UI (`verify.caib.io`)

This host renders **human-friendly verification pages** for Registry entities (typically linked as `verify_url` from API responses when configured).

## Source of truth

The **authoritative, machine-readable record** is always on the **Registry**:

- **Single entity:** `GET https://registry.caib.io/v1/entities/{id}`
- **Tenant scope / related rows:** `GET https://registry.caib.io/v1/entities?domain=<tenant_domain>` — add **`type=`** or other filters per **`openapi.json`**; **omit `type`** for all types in scope.
- **OpenAPI:** https://registry.caib.io/openapi.json

Treat HTML on `verify.caib.io` as a **presentation layer**; merge answers and tool outputs from **Registry JSON**.

## When to use this host

- Showing a **readable** verification surface to end users.
- Explaining **what** was published without forcing raw JSON in chat UIs.

## When to use the Registry instead

- Programmatic **fact lookup**, bulk discovery, integrations, codegen, MCP tools, or any task requiring **stable fields** and **filters**.

## More context

- Cross-host overview: https://caib.io/llms.txt  
- Registry-focused detail: https://registry.caib.io/llms.txt  
- **Caib.org full published catalogue (all unit types):**  
  `GET https://caib.caib.io/v1/entities?domain=caib.io`  
  (Orientation: https://caib.io/llms.txt — contract: **`openapi.json`**.)