Partner Platform Agreement
For agent platforms deploying into enterprise tenants under Agentics governance. Last updated July 8, 2026.
This Partner Platform Agreement ("Agreement") is between Agentics Technologies LLC ("Agentics") and the third-party agent platform identified on an executed Partner Order Form ("Partner"). Partner builds and operates AI agents; Agentics operates the governance gateway, ledger, and runtime through which Partner's agents are deployed into enterprise customers' tenants ("Enterprises").
Architecture designation: for each deployment, the Enterprise is the data controller, the Partner is the deployer of its agent (responsible for the agent's behavior, disclosures, and fitness for purpose), and Agentics is the processor / infrastructure provider (policy enforcement, receipts, runtime). Each party signs data-processing terms consistent with this designation before production traffic flows.
- Agentics grants Partner a non-exclusive, non-transferable right during the term to integrate its agents with the Agentics gateway and deploy them into Enterprise tenants that have licensed them.
- Agentics Certification Suite (ACS) certification is required before any agent serves production traffic. Sandbox use is permitted pre-certification.
- Certification is per agent-version. A new version — any change to the agent's model, tools, prompts, or permissions envelope — requires re-certification before it replaces a certified version in production.
- Agentics may revoke a version's certification for material policy violations or security findings, with notice and, where practical, a cure window per Section 6.
For Partner agents sold through Agentics, or Agentics services sold through Partner, net revenue is shared as set out in the Partner Order Form:
| Stream | Partner share | Agentics share |
|---|---|---|
| Enterprise fees for Partner agents deployed via Agentics | [●]% | [●]% |
| Agentics platform fees originated by Partner referral | [●]% | [●]% |
| Hosted-runtime usage fees for Partner agents | [●]% | [●]% |
Statements and payouts are monthly, net 30 after the month's end, with 12 months of audit-relevant records retained by each party.
- Partner may set a default Bureau contribution tier for Enterprises it deploys into, declared at onboarding and shown to the Enterprise before activation.
- The Enterprise's own setting always overrides Partner's default. An Enterprise may change its tier or opt out entirely at any time, and neither Partner nor Agentics may penalize it for doing so.
- Only k-anonymized (k≥5), differentially private (ε=1) aggregates ever leave a tenant. Raw prompts, outputs, receipts, and identities never do. Enterprises are never publicly ranked.
- No cross-partner leakage: Partner receives no Bureau signal that identifies, or could reasonably be re-identified as, another partner's agents or another partner's enterprise customers.
- While a version holds ACS certification, Partner may display the "Agentics Certified" badge for that version, per the brand guidelines.
- The badge must always resolve to the Agentics verification page for that agent-version — including in white-labeled or embedded deployments. A badge that does not link to live Agentics verification is prohibited.
- Badge rights end immediately for a version when its certification lapses or is revoked; cached or printed uses must be removed within 10 business days.
- Partner must not state or imply that certification covers uncertified versions or non-agent products.
- Agentics may suspend an agent or Partner access immediately where reasonably necessary to prevent security incidents, legal violations, or material harm to an Enterprise, notifying Partner promptly with the reason and restoration criteria.
- Other breaches follow a 30-day written cure period before termination.
- On termination, production traffic is wound down over a schedule that protects affected Enterprises (up to 90 days at Enterprise election), Partner data is exportable for 60 days, and receipts already written to Enterprise ledgers remain with those Enterprises.
- Sections on Bureau restrictions, confidentiality, liability, and governing law survive.
Each party's total aggregate liability under this Agreement is capped at the fees paid or payable between the parties in the 12 months before the event giving rise to the claim. Neither party is liable for indirect, incidental, consequential, or punitive damages or lost profits. The cap does not limit payment obligations, indemnities for IP infringement or data misuse, or liability that cannot be limited by law.
Governing law: State of Delaware, exclusive venue in Delaware courts. Order of precedence: Partner Order Form, then applicable data-processing terms, then this Agreement. Neither party may use the other's marks beyond what this Agreement grants. Amendments must be written and signed. Questions: /contact/.
Terms · Privacy · MSA · DPA · Partner Platform Agreement · Hosting Addendum