Skip to main content

​
Quick Start

claude mcp add interf-gateway -e OPENROUTER_API_KEY=sk-or-... -- npx -y @interf/gateway
Then in any project: 
> Use interf to generate an agent readiness spec for this project
> Run a simulation for a Fortune 500 bank
Your coding agent analyzes the project, generates an interf.yaml manifest declaring every dependency your agent needs from an enterprise, and runs a deployment simulation against real enterprise profiles.
@interf/gateway is live on npm. Get your OpenRouter API key at openrouter.ai.

​
What You Get

Define your agent’s enterprise requirements once in interf.yaml — APIs, auth, compliance, approvals — then simulate what deployment looks like at any enterprise profile. Each simulation returns per-dependency analysis:
  • Resolution flow — ordered steps with owners, timelines, and blockers
  • Stakeholders — roles, involvement level, time commitment
  • Risks — likelihood, impact, and mitigations
  • Critical path — total days to production readiness
# interf.yaml
name: crm-automation-agent
version: 0.1.0
description: Automates CRM data entry and follow-up scheduling

dependencies:
  - type: api
    name: Salesforce API
    description: Read/write contacts and opportunities
    required: true
    config:
      endpoint: https://api.salesforce.com
      auth_type: oauth2
      scopes: [api, refresh_token]

  - type: auth
    name: SSO Integration
    description: Enterprise SSO for agent authentication
    required: true
    config:
      provider: okta
      protocol: saml

  - type: compliance
    name: SOC2 Compliance
    description: Required for handling customer PII
    required: true
    config:
      frameworks: [SOC2]
      controls: [data_encryption, audit_logging, access_review]

  - type: approval
    name: Security Review
    description: InfoSec team must approve API access
    required: true
    config:
      approver_role: security_engineer
      justification: Agent accesses customer PII via Salesforce

capabilities:
  - read_contacts
  - write_contacts
  - read_opportunities
  - schedule_followups

risk_level: high

​
The Vision: Agents That Know They’re Not Ready

Today, agents deploy blindly into enterprise environments. They don’t know if they have the necessary data access, authentication, or compliance permissions to function. Readiness gaps are discovered mid-flight — stalling deployments and freezing capital. Interf changes this. We’re building the protocol and infrastructure for agent self-awareness in enterprise environments.

​
Agent Readiness Protocol

An open standard for declaring what agents need from enterprises to be ready. Dependencies are specified in interf.yaml — a machine-readable contract between vendor and enterprise. Vendors define it. Enterprises resolve it. Agents verify it.

​
Agent Readiness Gateway

The runtime layer where agents and enterprises communicate readiness.

For Vendors

Define your agent’s requirements in interf.yaml. Simulate deployments against enterprise profiles. Publish to the Interf registry so enterprises can self-prepare.

For Enterprises

Pull vendor manifests from the registry. Run pre-flight checks against your environment. Resolve dependencies before the agent arrives — not after.

​
How It Works in Production

  1. Enterprise loads a vendor’s interf.yaml into the gateway, creating a readiness workspace.
  2. Gateway exposes readiness state as an MCP endpoint — each dependency tracked from unresolved to verified.
  3. Enterprise IT resolves dependencies (provisions API access, configures SSO, completes security reviews).
  4. Vendor agent connects to the gateway, queries its readiness state, and self-verifies each dependency.
  5. Agent confirms 10/10 dependencies verified — ready for production.
The gateway is the communication layer between “enterprise prepared this” and “agent confirms it works.” Resolution happens on the enterprise side. Verification happens on the agent side. Interf connects the two.

​
What’s Available Today

The simulation toolkit is the first step. Create your interf.yaml, simulate enterprise deployments, and publish to the registry. The full agent self-onboarding experience — where your agent connects to the gateway, queries its readiness, and verifies dependencies in real time — is what we’re building toward.

Get Started

Install the MCP server and create your first agent readiness manifest.