01
Supply a bounded reason
The AI or user states the intended action, business reason, relevant reference, expected effect, and uncertainty needed for the enterprise’s policy.
For AI, agent, and tool providers
Help your AI act through a path the customer controls.
When your AI needs to change a customer system, Matten is the governed route. Your AI or user supplies the business reason. The enterprise keeps control of the endpoint, credentials, policy, and record.
The provider moment
Your customer wants the workflow. The write path is the blocker.
The enterprise may trust the value of your AI and still refuse a direct path into a business system. Matten lets the enterprise own that path while your product stays the caller.
That is one product for one enterprise buyer. The provider helps the action reach the right boundary; it does not become a second owner of the customer’s controls or record.
The governed provider path
Keep your agent. Give the customer the boundary.
The AI interaction stays in your product. The enterprise owns the route that reaches its system and the history that remains.
- 01
AI or user supplies the reason
A short business-facing reason travels with the requested action.
- 02
Matten checks the enterprise path
Caller, source, profile, tool, elevation, quota, and revocation rules apply.
- 03
The native tool call moves forward
Matten forwards the admitted tool request without becoming the agent runtime.
- 04
The result stays tied to the reason
Attempt, response, observed effect, and unknown outcome remain distinct.
- 05
The company owns the record
The enterprise keeps the action history under its own policy.
The provider keeps
Your product, your agent, and your customer experience.
- The conversation and product experience
- Planning, model behavior, and agent orchestration
- The native tool request your product prepares
- The customer relationship you already own
The enterprise owns
The action boundary and the record that remains.
- The endpoint and credential route
- Approved callers, sources, and tool policy
- Upstream business authorization
- Retention and the company-owned Judgment Ledger
Integration boundary
A small contract, not a second agent stack.
Matten asks the caller for bounded business context and keeps Matten-only fields out of the native tool request. It does not need your full transcript or hidden model reasoning.
02
Recover from missing context
If the governed path needs more context, the contract returns a structured response the caller can act on.
03
Keep native tool meaning
Matten removes its own context envelope and forwards the native tool arguments without changing their meaning.
Provider questions
What changes—and what stays yours.
Does Matten replace our agent or runtime?
No. Your product keeps planning, conversation, and agent behavior. Matten governs the enterprise-owned route into admitted tools and preserves the business reason with the resulting action record.
Who writes the business reason?
Your AI client—or the user it represents—supplies a bounded business-facing reason. Matten does not independently explain your model or infer hidden reasoning.
Do we have to send the whole conversation?
No. Matten uses a small, explicit context contract rather than full prompts, transcripts, or chain of thought.
Does the reason give our AI permission to act?
No. The reason only supplies context. Matten Access and the customer’s upstream application permissions still decide whether the action may be attempted.
Who owns the route and record?
The enterprise customer owns the tenant, endpoint, credential policy, approved callers, tool scope, retention rules, and Judgment Ledger. The provider remains the caller and integrator, not the owner of company policy or history.
Keep the provider and enterprise roles clear
Help your AI use a path the customer can own.
Talk with Matten about the enterprise action, the caller, and the path the customer needs to control.