Public pages and code examples are documentation, not live product data.
Agent safety and governance
An agent should know when to stop.
AgentLayer keeps the record, its sources, and the caller's access limits together. When evidence or permission is missing, the client gets a refusal or blocker instead of a polished guess.
Rules
The boundaries travel with the answer.
Responses keep their source trail, time, uncertainty, and access rules.
Missing state produces a blocker or abstention, not a plausible guess.
Scores explain their components and what a high value means.
Sensitive fields require the right scope and may be redacted or withheld.
Scenario results stay labeled and separate from observed records.
Agents cite the returned records and evidence.
Hosted use requires an approved deployment handoff.
Do not scrape the marketing site
Approved clients use their assigned interface. Public pages and examples are documentation, not live records.
No unsupported claims
Outputs should cite returned records, evidence, and decision context when used downstream.
No silent sensitivity handling
Restricted or sensitive fields should be redacted or withheld with a visible reason.
No scenario mixing
Scenario results stay labeled and separate from observed records.