---
title: Introduction
description: Get choices, calculated amounts and dates from one decision API.
icon: book-open
---

aityx is a **decision API for AI applications**. Return choices, calculated amounts and dates your application can use directly.

For example, a subscription cancellation returns **cancel + refund**, a **$20 refund** and an **October 28 processing deadline**. Your application supplies the customer message and account facts; aityx returns the answers together.

**[Run your first decision](/docs/quickstart)**

Get the refund amount and deadline from the homepage example.

**[Try the console examples](/docs/guides/use-cases)**

Invoices, expenses, service credits, returns, travel, discounts and support triage.

## One endpoint, three shapes

`POST /v1/systemone` is the only public operation. What you include decides what runs:

| You want to | Send | Shape |
|---|---|---|
| Execute a Decision with matching facts | `decision` + `state` | **Decision only** |
| Ask Jev questions about your data | `questions` + `state` | **Jev only** |
| Read evidence with Jev, then apply your rules | `decision` + `questions` + `state` | **Jev + Decision** |

In the combined shape, Jev runs first and the Decision returns the consolidated result. There is no separate authoring or input-interpretation endpoint: you write the Decision JSON and send it with each case. See [One endpoint, three shapes](/docs/concepts/execution-paths) and [Using Jev with aityx](/docs/coming-from-jev).

<figure className="aityx-diagram">
  <picture className="aityx-diagram-light">
    <source media="(max-width: 640px)" srcSet="/docs/diagrams/how-aityx-works-mobile.svg" width="520" height="768" />
    <img src="/docs/diagrams/how-aityx-works.svg" alt="One endpoint, three shapes: POST /v1/systemone runs a Decision alone, Jev questions alone, or Jev questions feeding a Decision. Each shape returns answers with a receipt." width="960" height="636" decoding="async" />
  </picture>
  <picture className="aityx-diagram-dark">
    <source media="(max-width: 640px)" srcSet="/docs/diagrams/how-aityx-works-mobile-dark.svg" width="520" height="768" />
    <img src="/docs/diagrams/how-aityx-works-dark.svg" alt="One endpoint, three shapes: POST /v1/systemone runs a Decision alone, Jev questions alone, or Jev questions feeding a Decision. Each shape returns answers with a receipt." width="960" height="636" decoding="async" />
  </picture>
  <figcaption>Every shape returns answers and a receipt from the same endpoint.</figcaption>
</figure>

## One model. One state. Typed answers.

A native model is the JSON definition itself: `name`, `inputs`, `decisions`, and optional `types` and `functions`. Send it with `state`, the data for this case. Answer names and types come from the model; you do not repeat them in `questions`.

Selected answers from the recorded refund example, shortened for readability:

```json
{
  "request_type": "cancel_refund",
  "refund_eligible": 1,
  "refund_amount": 20,
  "processing_deadline": "2026-10-28"
}
```

The example prorates a $60 plan over 30 days with 10 days unused, and adds seven calendar days to October 21. Boolean decisions return `noul`: `1` for true and `0` for false. The response also includes helper decisions, a receipt and token usage. Settled charges are available in the console.

Every shape costs **$0.042 per 1M input tokens, with output free**. See [Pricing and limits](/docs/resources/pricing-and-limits).

## Use it from your application

Keep the model in your application and send it with each case. Receipts return inline; retain them with the original state when needed. There is no stored-model or receipt-history lookup. aityx returns the decision; your application performs any refund or other action.

**[Call it from code](/docs/guides/call-from-code)**

JavaScript and Python clients for matching facts and customer messages.

**[Build your own model](/docs/guides/define-by-hand)**

Write the native Decision JSON yourself.

**[Answer types](/docs/concepts/questions)**

Read choices, booleans, numbers and dates.

**[API reference](/docs/reference)**

Request and response schemas for the one public operation.
