Example 1HealthcareIllustrative scenario
Situation. A nurse reviewer asks a claims assistant to review a prior-authorization request. The assistant calls a formulary agent that reads clinical data.
1 · Delegate
KeelAuthA token names the nurse, both agents and the purpose: prior-auth review.
2 · Decide
Context GatewayFormulary and chart notes are allowed. The SSN and unrelated history are redacted.
3 · Act
AgentThe agent completes the review using only the data it needed.
4 · Record
Keel IntelligenceWhat was read, for whom and why is logged. Auditors can replay it.
Outcome. Minimum-necessary access enforced in software, and every read attributable to a person and a purpose.
Example 2Financial servicesIllustrative scenario
Situation. A bank lets a customer-support agent issue refunds on behalf of the support team.
1 · Limit
Keel GovernanceThe refund agent has authority up to $500 per refund, to known payees only.
2 · Signal
Keel IntelligenceRefunds jump to four times the learned baseline, near the limit, to new payees. Each refund is within policy; the pattern is not.
3 · Respond
Keel GovernanceThe risk score reaches Governance. New refunds now need human approval, and scope can be cut in one click.
Outcome. Policy catches what is clearly wrong. Behavior catches what is technically allowed but suspicious. Both share one identity.
Example 3Any enterpriseIllustrative scenario
Situation. An employee asks the company copilot to summarize a vendor contract. Hidden text tells it to email the HR salary file outside the company.
1 · Scope
KeelAuthThe token carries the employee, the copilot and the purpose: contract review.
2 · Deny
Context GatewayThe gateway refuses the HR salary file. It is outside the purpose, whatever the model now believes.
3 · Contain
Context GatewayData labels block confidential content from email and webhook tools.
4 · Alert
Keel IntelligenceThe attempt is flagged with the full chain and the source document.
Outcome. The model was fooled, but the agent could still only reach what its purpose allowed. Nothing left the company.
Example 4Any enterpriseIllustrative scenario
Situation. Someone on a data team spins up an autonomous agent in a notebook, gives it a personal API key and points it at member data.
1 · Found
Keel RegistryDiscovery spots an autonomous agent calling internal systems with a personal key and no owner in the Registry.
2 · Flagged
Keel IntelligenceIt read 18,000 records in nine minutes and tried an external webhook.
3 · Stopped
Keel GovernanceSecurity pulls the kill switch, approved by a 2-of-3 quorum. Tokens, credentials and context access are revoked everywhere.
Outcome. Today, stopping a rogue agent means hunting down every key it touched. With Keel it is one action. Full revocation in under 60 seconds is our design target.
Example 5B2B SaaSIllustrative scenario
Situation. A B2B SaaS company's enterprise customers want their own AI agents to use its API, safely and under their control.
1 · Add auth
KeelAuthLogin, SSO and SCIM: the enterprise checklist.
2 · Open to agents
KeelAuthKeelAuth becomes the authorization server for the company's API and MCP server.
3 · Scope
KeelAuthEach customer agent gets a delegated token: which customer, which user, which agent, which actions.
4 · Control
Keel RegistryCustomer admins see every agent on their account and can revoke any of them.
Outcome. Enterprise-ready and agent-ready access without building an identity team.