Skip to content
aityx
Esc
↑↓navigate↵open⌘Jpreview
On this page

The console

Edit Jev questions and a Decision, supply state, execute, and copy the current request as curl.

The console uses the same decision requests and rates as the API, with additional console-only timing and accounting details. Anyone can sign up and sign in with an email code; there is no approval step. Calls draw from your shared API/console credit balance.

Four panes, one case

Pane What you do
Jev questions Optional. Write Jev questions in Jev format; leave the pane empty to run the Decision alone.
Decision View or edit the native model: Decision, Visual, Fields and JSON Schema.
State Supply this case’s facts or evidence, and Execute.
Result Read Answers, Raw, Usage and the execution trace.

There is no AI assistant in the console. You write and edit the Decision directly. Native answers are inferred from the Decision model; you do not fill out a second output contract.

Use each pane’s expand icon for more space and the restore icon in the same position to return to quadrants.

Start from an example

Examples has seven decisions, grouped by shape:

  • Jev only: Support triage.
  • Decision only: Invoice payment, Expense claims, SLA outage credit.
  • Jev + Decision: Refund or store credit, Travel delay claim, Discount approval.

Choose one, Execute, and change a relevant fact to see its effect. The use-case guide provides their inputs and downloadable API requests. New starts a fresh decision.

The homepage’s subscription cancellation starts with an existing native model and matching facts, also available in the quickstart.

The shape is derived from your panes

There is no execution-mode selector. A read-only badge on the State pane shows which of the three POST /v1/systemone shapes will run, derived from what you have filled in:

Badge Runs when Result
Jev only Questions present, no Decision Jev’s answers are the result.
Decision only Decision present, questions empty The Decision runs locally on matching facts.
Jev + Decision Both present Jev runs first; the Decision returns the consolidated result.

Clear the questions to drop back to the Decision alone. Execution never creates or revises a model. The State pane previews the exact payload that will run.

Check, inspect and reuse

Check reports Ready to run or Cannot run. It is a free console operation; it is not a public API route. A failed check disables Execute until the definition is edited or passes a new check.

The trace shows computed values and executed table or conditional branches. Hover a node or expression header to see its result. Editing the model or state clears the previous result. Choose Edit, change the definition, Check, then Apply. The later homepage step changes the processing window from seven days to three; the same October 22 facts then return an October 25 deadline with the $30 refund unchanged.

Copy curl, beside Execute, copies the current model, state and questions — the derived shape included — with any unsaved edits. Set AITYX_API_KEY in your terminal; the copied command uses that environment variable instead of your session token.

Keep definitions and responses your application needs before leaving the session. Models, state and receipts are not durably stored by the service. The console has no saved-model library or receipt-history retrieval.

Balance and API keys

Usage shows spending and available credits; API keys manages keys for your server. The console shows tokens, settled charges and balance; the public execution response contains only answers, trace and token usage. Matching input values in the visual trace come from your locally retained state, not an echo in the receipt. Tiny charges can appear as less than $0.001. Jev calls require a positive balance and may settle below zero; Decision-only calls require sufficient funds for their reservation. See Pricing and limits.

Cancel aborts the browser request, but does not guarantee stopping backend/provider work or avoiding billing. See Pricing and limits.

Was this page helpful?