Embedded Agentic Risk
Available through: your AI vendor's product, sold by Auxilium's licensed agency
Who it is for
For developers
Companies that build agentic software: support agents, finance and operations agents, coding and IT agents, sales agents. You offer cover as part of deployment rather than leaving your customer to find it.
Who is insured
Your customer, the business deploying the agent inside its own operations. The policy is issued in the customer's name and they are the policyholder.
What is insured
The losses the agent's actions cause the deploying business and the people it owes duties to. Not the agent, and not you.
How it works
Integrate
Add the Auxilium API: a quote endpoint, a bind endpoint and a webhook for policy events.
Deploy
When a customer deploys an agent, your product passes the deployment configuration with the customer's consent: what the agent can do, which systems it can reach, spending and action limits, and where a human approves.
Offer and bind
The customer sees a quote inside the deployment flow and can bind it in a few clicks. Cover is sold by Auxilium's licensed agency, and the customer is the policyholder.
Covered from day one
The policy is bound on the configuration at deployment, so there is no uncovered waiting period.
Adjust on real activity
After the first 30 days, read-only activity logs from your platform feed a rate adjustment. After that, rates are reviewed at set intervals, for example quarterly, rather than changed continuously.
Claims
Customers report claims directly to Auxilium.
What it covers
Cover answers to the deployer, the business that turned the agent on inside its own operations.
| Coverage | What it covers | Basis |
|---|---|---|
| Third-party liability | A claim arising from an agent's action: wrong or harmful communications to customers, unauthorized commitments, mishandled personal data, or erroneous transactions affecting a third party. | Third party |
| First-party loss | The deployer's own loss from an agent's unauthorized or erroneous action, including funds sent in error and the cost to reverse or remediate the action. | First party |
| Incident response | Investigation, notification and remediation costs after an agent-caused incident. | First party |
| Regulatory defense | Defense costs in a regulatory proceeding arising from an agent's action. | Regulatory |
What it does not cover
We do not insure the agent. Three exclusions follow from that and they are the ones worth stating plainly.
The agent itself
Its performance, accuracy or uptime, and the cost to fix or replace it. If the agent is simply bad at its job, that is a product question between you and your customer.
The developer's own liability
Your product liability and your errors and omissions are not covered here. This policy belongs to your customer, not to you.
Approved actions outside permissions
Loss from an action a human approved outside the agent's configured permissions. The configuration is what was underwritten.
For developers: what you get
A differentiator in the sale
Cover offered at deployment is a reason to choose you, and a faster path through your customer's security and risk review.
No insurance operations
Auxilium handles licensing, underwriting, policy issuance and claims. You ship an integration, not a carrier relationship.
Compensation
A marketing fee that is not tied to whether a customer buys, unless you hold a producer license.
In development. Nothing here is an offer of insurance or a commitment to quote, and the policy wording governs in every respect.