How do you check a refund or order before an AI agent carries it out?
You write the limits, such as a refund cap or an approved-vendor list. Your agent submits each action and its message to Vindex before it runs, and an independent model rules on it, naming any rule it did not pass. The agent never grades its own work: it fixes the action or hands it to a person.
You write the rules
Owner, Bookkeeper, and Head of Support
Your agent does the work
Refunds, credits, purchase orders, and the customer messages that go with them.
Vindex rules on it
An independent model checks each output against the rule version in force and names any rule it did not pass.
Each branch checks the others. The agent never reviews its own output.
The rules you write
These are examples to adapt. Your company drafts, versions, and owns every rule, in plain language or from public rules. An agent can draft a rule. Only a person makes it law.
Refund limit
The refund is no more than the original charge and no more than the limit your policy sets for agents.
Allowed offers
Any discount, credit, or date offered is on the list of offers your policy allows.
Reason recorded
The action names the ticket or order it belongs to and the reason for it.
Approved vendors
Purchase orders go only to vendors on your approved list and stay within the stated budget.
Opt-out line
Any text message includes the opt-out line your policy requires.
Have your agent check the action before it runs it. Repeat actions, such as a second refund for the same order, need history Vindex does not see, so guard those in the system that carries them out.
