The Problem: Blind Agents
Agents are designed to be autonomous, but today they deploy blindly into opaque enterprise environments. They don’t know if they have the necessary Data Access, Authentication, or Compliance permissions to function. This leads to readiness gaps discovered mid-flight — stalled deployments, frozen capital, and implementation delays.The Solution: Protocol + Gateway
Interf sits between Agent Capabilities and Enterprise Context.Agent Onboarding Protocol (AOP)
Open standard for declaring agent requirements (data, auth, compliance) as a Capability Contract in
interf.yaml.Shared Context Gateway (MCP Server)
Resolves contracts against the enterprise environment. Exposes MCP endpoint for agents to query readiness and self-onboard.
The Mechanism
- Define: Vendors define requirements in an
interf.yamlcontract. - Resolve: Enterprise prepares dependencies. Gateway tracks resolution.
- Onboard: Agent connects via MCP, checks readiness, proceeds when ready.
Status: Protocol Specification and Gateway OSS publishing January 2026.
