One backend action endpoint routed through Salus. issue_refund. update_appointment. send_sms. update_crm_record. collect_payment. create_claim. transfer_to_human.
One Salus decision on one proposed action. The decision can allow, clarify, repair, rewrite, escalate, or refuse.
We help you choose the first protected tool route, run it in shadow, and promote it live when the policy is ready. Most teams begin with the action where a mistake would hurt most — refunds, bookings, CRM writes, messages, payments, claims, or handoffs.
Do you charge per agent?
No. Agents are easy to create and expensive to trust. Salus charges by protected tool routes and action checks, not by the number of agents.
What is a protected tool route?
One backend action endpoint routed through Salus before execution. For example: refunds, appointment updates, CRM writes, SMS sends, payments, claims, handoffs, or account changes.
If one agent has five tools, is that five routes?
Only if you route all five through Salus. Most teams start with the one or two risky tools where a wrong action would hurt.
If ten agents use the same refund endpoint, is that ten routes?
No. If the same protected endpoint and policy are shared, that can count as one protected tool route.
Do we have to start in enforcement?
No. Most teams start in shadow first, see what Salus would have decided differently, then promote one route live. It is the right way to do it.
Can we add more routes later?
Yes. Start with one protected tool route. Add more as your agents touch more real systems.
Do pilots have a contract?
Month-to-month, cancel any time.
One protected tool route. One policy. One action path made safe.
We will pick one risky tool route, run it in shadow, and show what Salus would allow, clarify, repair, rewrite, or escalate before anything reaches your backend.
Book a demo →