Developers

Evidence binding

Last updated 18 September 2026

Hansala publishes confirmed work. Bind a record on its stable id (UUID) and confirmed_at. Do not treat generated_at as proof — that is when the JSON envelope was built, and it changes on every fetch.

What to store

id — partnerships.id or service_references.id. Stable across responses.
confirmed_at — ISO-8601 when both sides accepted. Empty string only if the timestamp was not stored (legacy).
Company slug — human lookup. The UUID is the bind key.

Public JSON never includes pending invites. If a relation is gone from the list, it is no longer public — absence is not a negative finding.

What not to hash

generated_at on the company payload — request time, not confirmation time.
JSON-RPC id on MCP frames — envelope, not evidence.
Widget HTML, Open Graph images, or directory rank.

Where to read it

REST: GET /api/v1/companies/{slug}/partners and /references.
Hosted MCP (no key): POST https://www.hansala.com/api/mcp/public — tool get_company_proof. Discovery: /.well-known/mcp and /server-card.