The governed execution layer
for AI agents.
Intent, policy, execution - Formael handles the full lifecycle of every outbound agent action, and makes the call protocols and gateways leave open: should this action, with these arguments, happen right now? One boundary, any external system, credentials the agent never sees.
Intake
Normalize an agent's intent into one governed transaction
Governance
Four-axis evaluation on the contents of the request - every action, every time
Execution
Credential-safe execution against the right system, fully traced
Platform capabilities
Governance infrastructure
built for the agentic era.
Not middleware. Not a proxy. Not an MCP gateway that checks who is at the door. A complete execution boundary that evaluates every action on its way out - policy, connectivity, fiscal control, and a dual-trace record, in one place.
Four-Axis Policy Engine
Every intent weighed across Identity, Semantic, Fiscal, and Risk - using the actual contents of the request, at the moment of the call. All four must pass. There is no bypass path.
Dual-Trace Audit Ledger
Every action carries two linked traces: the agent's reasoning (why it acted) and the platform's execution record (what exactly happened). Audit you emit on the way through, not audit you reconstruct after. Append-only, forever.
Intent-Shaped Connectivity
Agents act against capabilities - verbs like create an invoice or send for signature - never provider APIs. Swap DocuSign for PandaDoc, or Jira for Linear, without changing a line of agent code. Your surface grows with the business, not the catalog.
Human-in-the-Loop Approvals
High-risk actions pause for human review without blocking the agent. It receives a deferred receipt and keeps reasoning while the right team - routed by domain - resolves the request.
Dual-Ledger Fiscal Control
Two independent ledgers - platform spend in USD and action value in any currency - checked synchronously on every IEC. Define limits per org, per agent, or per domain.
MCP-Native Access
The front door, not the decision. Agents that speak MCP connect with zero Formael-specific code, presenting tokens from your own IdP and discovering only the capabilities their scope allows. Evaluating this action, with these arguments, right now is Formael's job - not the protocol's.
How it works
Intent in.
Authorized action out.
Every agent action runs one cycle: intent in, outcome out, recorded once and never altered. Policy decides on the contents of the request - so the same three steps govern a Slack message and a six-figure payment.
Intent Submission
The agent speaks intent. Never implementation.
The agent submits a structured IntentEnvelope - a three-part semantic tuple, typed parameters, and its own reasoning context. No credentials. No provider name. No API schema. The envelope has no field for secrets by design.
Intent Envelope
contracting·send·for-signature
“Finalize partnership agreement before Thursday's call”
Four-Axis Policy Evaluation
Governance happens here. Every time.
Before any action reaches an external system, the policy engine intercepts and evaluates it across four independent axes. Every axis must pass. The verdict is the conjunction - no axis compensates for another's failure. No exceptions. No fast paths.
Identity
Is this agent authorized for this capability in this context?
Semantic
What does this intent mean - and is that permitted?
Fiscal
Can the org and this agent afford the consequences?
Risk
If this goes wrong, how bad is it?
Authorized Execution
Approved. Executed. Permanently recorded.
Once approved, Formael resolves the organization's provider binding, injects credentials from the secure vault - exclusively, for this execution only - and executes against the external system. The result is normalized and written to the immutable ledger alongside the full dual trace.
Supported adapters
Resolves to the right connector for your configured provider - declarative specs, no agent changes.
Observability
Not just what happened.
Exactly why it was allowed.
Every action carries a dual trace - the agent's reasoning and the platform's execution record, linked by one ID. The “why” is gone the moment a request finishes, unless the system emits it on the way through. So Formael does - permanently, for every action.
Policy axis summary · sample data
pass rate
pass rate
pass rate
HITL triggered
“When an agent acts, two questions matter: why did it want to do this, and what exactly did the platform do about it? Formael answers both - permanently, for every single action.”
Formael · Dual-Trace Design Principle
Early Access
Build the AI agents
you actually want to ship.
Join the Formael early access program. Get the boundary your agent fleet needs - governed execution, an append-only audit trail, and a neutral control plane you own - before you have to build it yourself.
Your Agent
Semantic intent envelope
Formael
Govern · Execute · Trace
External APIs
DocuSign · Jira · Slack…