It lets you decide what your business's AI agents may do — buy, refund customers, push code, handle everyday tasks — asks you when something needs your approval, and keeps a verified ledger of everything they did.

The amount was above the approval limit in that agent's permission, or the agent asked before checking out. A held purchase or refund waits 10 minutes; a request made before checkout waits 24 hours.

It broke a limit in the agent's permission: over the per-purchase maximum, over the limit for the period, a blocked category, or an expired permission. Nothing is charged for a stopped purchase.

No. Orindus records the actions that pass through it: purchases, refunds to customers and code actions. For everyday tasks such as emails and registrations it records what the agent asks and what it reports back, not the action itself. An agent that does not ask leaves no record.

Open Agents, choose the agent, then Edit permissions. The new permission replaces the old one the next time the agent acts.

No. The card is entered on Stripe's page. Orindus and your agents never see the number.

This browser checked the entry's signatures and its place in the public log. The details are under “Show technical details”.

No. It is recorded as you enter it and printed on your accounting exports and ledger entries. Orindus does not verify it with any registry.

Every browser where the owner has signed in. For people added under Team, the owner receives a copy of their ledger entries from the day they joined. In approve mode the owner or an approver answers their approvals, and a new or changed permission waits for the owner. An approver can be limited to an amount.

Once a year the owner confirms that each person under Team still belongs. If it becomes overdue, that person's agents are stopped and they cannot give new permissions until the owner reconfirms them.