Contract API
When an AI agent asks “what is our churn rate?”, it should get the governed answer — not a stale warehouse artifact. The ClariLayer API is the formal interface between your AI strategy and your business logic.
Start FreeThree churn definitions in the warehouse. The Finance version, the Marketing version, and a draft someone forgot to delete. Which one does the agent use?
The agent uses the wrong definition. It auto-triggers win-back campaigns targeting customers who are still active. Fast, confident, and wrong.
The agent queries ClariLayer and gets the canonical, governed answer with full context: who approved it, when it was validated, which version is current.
An AI agent, BI tool, or internal app asks: “What is MRR?” The API returns the organization’s canonical definition.
The response includes the governed definition, SQL logic, business description, owner, approval status, validation date, tier, and version.
Each API lookup is grounded in a specific metric version, with lifecycle state, approval context, and validation evidence attached.
Integration Surface
AI agents are dangerous when they treat every table, YAML file, and dashboard query as equally authoritative. The Contract API gives those systems a governed lookup before execution: which definition is current, who owns it, what policy tier it sits in, and whether the release has validation and approval evidence attached.
The API is downstream of the full lifecycle. Definitions come from AI-assisted Metric Studio authoring, proof comes from warehouse validation checks, and trust state comes from governed release workflows. Consumers can then use the Metrics Contract API documentation to understand the public response shape.
Agents can ask for the approved business definition before drafting SQL, choosing an automation path, or explaining a KPI to a user. The response gives the agent policy and evidence, not just a label.
Dashboards, notebooks, and operating tools can display owner, lifecycle status, version, and validation recency beside the metric so business users understand whether the number is suitable for the decision at hand.
API consumers receive a particular metric version and lifecycle state. If a definition changes later, teams can compare consumers against the previous contract instead of guessing from warehouse query text.
Every API response includes the metric definition, business description, SQL logic, owner, approval chain, and governance tier — not just a number.
Last validated date, approval status, certification tier, and version history. Your AI agent knows whether to trust a metric before acting on it.
AI agents search by intent, not just name. Ask for “churn rate” and get the canonical, governed definition — not three competing versions.
Works with any AI framework, BI tool, or internal application. ClariLayer is the Switzerland of metric governance — no warehouse vendor lock-in.
Connect your AI agents to governed metric logic. Every agent decision is traceable to an approved definition.
Ensure dashboards and reports reference the same governed definitions. Eliminate the trust deficit.
Query the API from any internal tool. One source of truth for metric meaning across the organization.
Join the companies building a trusted context layer for their AI agents and business teams.
Start Free