Skip to main content
Therius turns its orchestration data into something an AI can reason over: authorization rates, decline reasons, routing decisions, subscription health, dispute deadlines, and settlement matching. There are two ways to use it, and they share the same tools, the same permission model, and the same guardrails.

Thera

An AI assistant built into the Therius dashboard. Ask questions in plain language about the merchants you can access. Runs as you, scoped to your permissions.

Bring Your Own AI

Connect Claude, Cursor, ChatGPT, or any MCP client to Therius with a user-scoped AI key. Your AI subscription, your model — Therius hosts nothing for this path.
A third, separate capability — Agent keys — lets an autonomous agent conduct bounded commerce (create a real, spend-capped payment link) rather than read your data. It does not share the “read and draft only” guarantee below; see that page for its own guardrails.

​
Which one should I use?

​
Shared guarantees

Both paths are built on the same rules:
  • Your scope, never wider. An AI request can only reach the merchants you are assigned and can only call the tools your Therius role permits. Scope is enforced by Therius on every call — the model cannot widen it, and revoking a role immediately strips the matching capability from any AI key you issued.
  • Environment isolation. Production and sandbox data never mix. A sandbox AI key (ai_sandbox_…) reaches only sandbox data; Thera answers for the environment you have selected in the dashboard.
  • No card data, no secrets. Full card numbers, CVVs, and connection credentials are never sent to a model — they are masked at the tool layer regardless of which model you use.
  • Read and draft only. No AI tool captures money, issues a refund, changes a routing rule, or resolves a dispute on its own. Actions that change state are returned as drafts for a human to review and confirm through the normal dashboard flow.
  • Untrusted input is treated as data. Text inside tool results (customer names, dispute notes) and the prompt itself are treated as data, not instructions.
  • Full audit trail. Every AI tool call is recorded — who called it, which tool, with what arguments, and when.

​
What the AI can see and do

The same tool set backs Thera and the MCP/REST surface. Availability of each tool depends on the permissions behind your session or AI key. See the tool reference for the full list and the permission each one needs.
Some capabilities are still maturing. Draft routing rules and dispute-evidence context are gathered for you, but a human always composes and applies the final change. Sandbox scaffolding tools are limited in the current build. The tool reference marks what is fully live.