AgentOnRails stays a provider-neutral policy, identity, privacy, and audit layer — it doesn't compete with your rail, your framework, or your agent runtime. A partnership plugs that shared layer into what you already run, so your users get budgets, approvals, identity, and audit without you building it yourselves.
Different partner types prove different parts of the platform — not six variations of the same demo.
| Priority | Partner type | What to propose | Why it matters |
|---|---|---|---|
| 1 | Agent framework (e.g. Hermes) | An approved, opt-in AgentOnRails integration with a joint demo | Distribution and default workflow access |
| 2 | Founder-controlled store + browser agent | Physical-product discovery and scoped-checkout proof | Fastest merchant and payment-rail proof |
| 3 | Paid API or data provider | Agent purchases one useful resource through x402 | Real digital commerce and repeat usage |
| 4 | AI automation agency | Multi-client budgets, identity, approvals, white-label dashboard | Paying B2B customer with downstream distribution |
| 5 | Multi-agent platform | Organization policy and reporting across multiple agents | Enterprise use case and embedded API |
| 6 | MCP tool or API seller | Accept per-call payments and verify buyer identity | Seller-side proof |
| 7 | Travel or procurement agent | Approved vendors, spend windows, restrictions, human escalation | High-value real-world workflow |
| 8 | Franchise or multi-location merchant | Agent-ready catalog and checkout across locations | Commerce enterprise pathway |
Warm, technically accessible teams willing to run a real production workflow — a smaller partner who ships is worth more here than a well-known name that only takes an introductory call.
Most partnerships start as a design partner pilot — an eight-week scope, one production use case, direct founder support.
Become a partnerOr go straight to the program terms: Design Partners