The trust layer
for the autonomous
AI economy.
AI agents are gaining the ability to act. Certaion gives businesses the infrastructure to identify agents, control their permissions and verify their actions.
Identity
registered
Decision
server-side
Evidence
digest-checked
The gap
AI agents are moving fast. Trust infrastructure must catch up.
Unknown identity
Businesses may not have a consistent way to identify and track every agent operating across their systems.
No shared register · no owner record
Uncontrolled permissions
Agents may have access to resources and actions beyond what they actually need to complete the task.
Standing access · no per-action decision
Fragmented accountability
When something happens, organizations may struggle to reconstruct who authorized an action, which policy applied and what evidence exists.
Logs without authorization context
The platform
One trust layer. Three connected capabilities.
Identity, authorization and evidence share one record model, so an action can always be traced back to the agent, the policy and the person who approved it.
01 — Agent Identity
Know every agent. Understand who owns it.
Every agent gets a unique internal identifier, an accountable owner, a developer record and a full lifecycle history — so nothing operates anonymously inside your systems.
- Agent registration
- Unique internal identifiers
- Ownership records
- Developer information
- Lifecycle tracking
- Parent-child relationships
- Identity metadata
02 — Authorization & Governance
Define what agents can and cannot do.
Policies evaluate each requested action against explicit, versioned rules on the server, returning ALLOW, DENY or REQUIRE HUMAN APPROVAL before the action is recorded as authorized.
- Policy creation and versioning
- Allow, deny and approval decisions
- Resource and action restrictions
- Spending and usage limits
- Time-limited permissions
- Permission revocation
03 — Action Evidence
Create an accountable record of every action.
Each action carries the authorization reference, the policy version that governed it, the approval trail, the reported execution result and an integrity digest that can be re-checked.
- Action records
- Authorization references
- Policy decision history
- Human approval history
- Execution results
- Evidence integrity checks
- Audit exports
- Incident reconstruction
Customer refund authorization
policy v3 · priority 40 · server-evaluated
refund.process · $32.00
refund.process · $74.00
refund.process · $640.00
How it works
From registration to verifiable evidence.
- 01
Register
Register an AI agent and assign its internal identity.
- 02
Identify
Associate the agent with its owner, developer and operating context.
- 03
Authorize
Evaluate the requested action against the applicable policy version.
- 04
Execute
Record the execution result and any required human approval.
- 05
Verify
Check the evidence and whether the action matched its authorization record.
Architecture
Built to connect the autonomous AI ecosystem.
Certaion sits between your agents and the systems they act on. Each layer is independently inspectable, so a policy decision can be replayed and an action record can be verified long after the fact.
Enforcement note
Certaion records and evaluates decisions before an action is reported as authorized. Your agent runtime must respect the returned decision; Certaion does not intercept traffic inside third-party systems.
- 01
AI agents & applications
Your agents, copilots and automations
- 02
Certaion SDKs & connectors
HTTP API today · SDK wrappers on the roadmap
- 03
Identity service
Agent registry, ownership, lifecycle
- 04
Policy & authorization engine
Deterministic evaluation on the server
- 05
Human approval
Four-eyes review before high-risk actions
- 06
Action evidence
Immutable-style record with integrity digest
- 07
Audit & verification
Trace, export and reconstruct incidents
Developers
Build with trust from day one.
Integrate identity, authorization and evidence into your AI agent workflows with a single HTTP call before each action.
- Authorization endpoint with recorded decision inputs
- Action recording with integrity digests
- Approval state you can poll or receive on review
- Audit export in CSV and JSON
// Request authorization before the agent acts
const res = await fetch("https://api.certaion.com/v1/authorize", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.CERTAION_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
agent_id: "agt_1904",
action: "refund.process",
resource: "order_88213",
context: { amount: 74.0, currency: "USD" },
}),
});
const decision = await res.json();
// { effect: "require_approval", policy: "pol_refund", version: 3, approval_id: "apr_..." }
if (decision.effect === "allow") await processRefund();
else if (decision.effect === "require_approval") await queueForApproval(decision.approval_id);Reference pattern · SDK wrappers on the roadmap
Security & trust
Trust should be engineered, not assumed.
Certaion is built around explicit decisions and checkable records. We separate what is implemented today from what is planned, because a governance product should not overstate its own controls.
Least-privilege authorization
Policies start from deny and grant only the resources and actions an agent needs.
Explicit policy decisions
Every evaluation returns a recorded effect, the policy version and the inputs it used.
Human oversight
High-risk actions can require approval, with the requester separated from the approver where possible.
Tenant isolation
Records are scoped to the organization that created them, enforced by access rules on every read and write.
Evidence integrity
Each action record carries a SHA-256 digest over its canonical fields, re-checkable at any time.
Auditability
Policy changes, identity changes and approval decisions are kept as history, not overwritten.
Clear ownership
An agent without a named owner cannot be treated as governed.
Transparent verification status
Internal registration, integration-reported execution and integrity verification are shown as distinct states.
Capability status
last reviewed · today- Organization-scoped access rulesImplemented
- Server-side policy evaluationImplemented
- Approval separation and historyImplemented
- SHA-256 evidence digestsImplemented
- Audit export (CSV / JSON)Implemented
- External identity verificationPlanned
- Signed webhook deliveryPlanned
- SOC 2 / ISO 27001 certificationNot claimed
Pricing
Start small. Scale into governance.
Developer
For individual developers building their first governed agent.
- Limited agent registrations
- Basic identity management
- Basic policy management
- Limited action records
- Developer documentation
Developer Pro
For teams shipping agents into production workflows.
- Higher usage limits
- Expanded agent management
- Advanced policies and versioning
- Longer evidence retention
- Developer tools and exports
Initial commercial hypotheses, not validated market prices. Billing is not connected in this environment; no payment is collected.
FAQ
Questions worth asking.
Answers describe what the platform does today, and clearly mark what is planned.