Introduction

Create rules you can inspect. Send your model with each case and receive an answer you can trace.

aityx is a decision API for AI applications and agents. Turn your business rules into a model you can inspect and test. Send that model with a case to get an answer, calculated amounts and dates, and a receipt showing the inputs and rules behind the result.

You control the rules your application runs. Keep the reviewed model in your own code or storage, test a revision against the same cases, and switch when the results meet your expectations.

Create the rules. Send them with every case.

Start with what you have

• Questions and a sample case. Get a model, answers and a receipt in your first call.
• A prompt or policy document. Draft a model, then inspect and test it before your application uses it.
• Rules you write yourself. Define the JSON or edit a generated model, and validate it before execution.

Already using Jev? Keep the questions-and-state request format as your starting point. See Coming from Jev for response, confidence and pricing differences.

Run the model you reviewed

Keep the complete returned model: content contains the executable rules; questions defines the answers to return. Every execution submits that object with state, the facts for the current case. See Models for the distinction.

With matching JSON inputs, the engine executes directly, with no AI reader or generator. Text or other data may need the reader to establish typed facts first. The receipt separates supplied facts from extracted ones; unresolved required facts stop execution. See State.

Supplying the full model selects System One execution pricing. Questions-based calls use System Two pricing, including cache hits. Input extraction is an additional System Two charge. The endpoint name does not determine the rate; Pricing and limits explains the details.

Keep the evidence. Check a change.

Save the model, original input and receipt together. The receipt identifies the rules that fired; your application keeps the original case for later tests. Run saved inputs against the original and revised models to see what changes before replacing the file your application uses.

The console holds decision data during the current session. Download your work before refreshing or leaving. Temporary model caches speed up repeated requests, but are not a saved-model library or receipt history. Accounts and billing records are retained separately.

Go deeper