Technology / OEM
Embed AgentOS inside your own product, under your own brand.
What you do
You build your own product on top of AgentOS — Workflow, the AI Assistant, the Orchestrator, and the rest of the platform — and ship it under your own brand. This is the OEM pattern: a partner product built on AgentOS is already running a major enterprise's day-to-day operations, described here rather than named, per the program's own claims discipline. Interactor never touches your end-customer relationship.
What you earn
- Platform usage rate
- set at agreement
What you need
- A technical review of your integration
- A signed OEM Agreement
- A production reference before launch
- AgentOS Builder for the team building on the platform
How a deal flows
Technical review
Interactor reviews how you intend to embed the platform before any agreement is signed.
OEM Agreement
Terms are set per agreement, including your production reference and go-to-market plan.
Embed & ship
You build and ship your own product on AgentOS, under your own brand — Interactor stays out of your customer relationship entirely.
Usage economics
Usage economics: set at agreement. Co-marketing included where it fits both brands.
One partner type per registered deal. Pick the type that matches how you're working this specific opportunity — you can hold more than one type over time.
Frequently asked questions
What does "embed" actually mean here?
You build your own branded product on top of AgentOS's platform services, the same way an existing partner has already built a product now running a major enterprise's operations — described here, not named, per the program's claims discipline.
Can you name the reference deployment?
No. Per the program's claims discipline, any customer reference is described, never named.
What do we earn from this?
Usage-based platform economics negotiated per agreement, plus co-marketing — see the table above.
Is this the same as being a reseller?
No — a reseller sells Interactor's own products as-is under their own paper. A Technology/OEM partner embeds the platform inside a different product entirely, under a different brand.
What do we need before we can start building?
A technical review of the integration, a signed OEM Agreement, and a production reference before launch.
Do we need AgentOS certification?
Yes — AgentOS Builder certification for the team doing the platform work, plus sales certification program-wide.