Agent Onboarding Protocol
An open standard for declaring what vendors need from enterprise environments to deliver value. The onboarding contract makes enterprise dependencies explicit, previewable, and verifiable — so enterprises self-prepare and vendors stop waiting.
Vendors declare it. Enterprises resolve it. No more mid-flight surprises.
Contract Specification
See spec.md for:
- The interf.yaml schema (requirements , optional , what
- ready )
-
Field definitions and validation rules
-
Design principles
Canonical Dependency Types
Dependencies can be anything in plain English. Canonical types enable deterministic matching across vendors and enterprises.
Start here: types/index.md — quick-scan index with match table. Read this first to identify which category applies, then dive into the detail file.
Category File What it covers
integration types/integration.md CRM, ERP, HRIS, email, webhooks, ticketing, analytics
auth types/auth.md SSO (SAML/OIDC), API credentials, service accounts, certificates
data types/data.md Historical exports, field mapping, sample data, PII, real-time feeds
infrastructure types/infrastructure.md Test environments, network/firewall, compute, DNS
stakeholder types/stakeholder.md Data team, security, IT admin, executive sponsor, business owner
process types/process.md Security review, legal/DPA, procurement, change management, training
No match? Leave canonical empty — the contract works with plain English alone.
Examples
See examples.md for realistic contracts across different rollout types (CRM automation, document processing, customer support).
How It Works
-
Declare — Vendor teams declare what they need in an interf.yaml contract. Use the declare skill to extract from a codebase, or write manually.
-
Deliver — Contract is sent to enterprise (via Interf platform, email, or however you work today).
-
Resolve — Enterprise works through each dependency. Each item has ready criteria so there's no ambiguity.
-
Verify — When all requirements are resolved, rollout can proceed.