Around your agents.
Not instead of them.
Keep the planner and runtime that work for you. Bring identity, policy, approvals and evidence to qualified interaction and effect boundaries.
Make intent explicit.
Keep authority current.
The model is the same whether a request starts in a coding client, a business agent or an unattended workload.
Exact actor, connection and resource
Material inputs bound to approval
A stable identity for the original effect
An attributable receipt and recovery path
{
"actor": "agent_example",
"action": "deploy.preview",
"resource": "project/staging",
"connection": "explicit_binding",
"policy": "current_at_point_of_use",
"approval": "bound_to_material_inputs",
"effect_identity": "stable_operation_id"
}This is a conceptual contract, not a released API schema or executable SDK example.
API & SDK
Integrate at a typed, qualified boundary. Use the published contract for the actual release.
ExploreMCP surface
Expose shared governance through authorized tool discovery and invocation—not a parallel policy engine.
ExploreAgent-readable facts
Retrieve the same product scope, limitations and pricing status as the human site.
Explore