---
search:
  tags:
    - Operations
    - POST
seo:
  description: >-
    A complete aityx model and matching state executes locally; no provider is
    called. Input… Reference for the POST /v1/systemone endpoint in the aityx
    API.
sidebar:
  label: Execute matching facts or Jev questions
  badge: POST
title: Execute matching facts or Jev questions
type: openapi-operation
---
A complete aityx model and matching state executes locally; no provider is called.
Input schema errors return 422; there is no automatic interpretation fallback.
Send decision + state for native execution. Jev's model is an inference alias,
never a native definition. Flat model? + questions + state is forwarded to Jev,
without creating an aityx decision. Add decision to that payload to chain both.
With both, Jev runs first. Model inputs may bind any response field with
from="jev:&lt;JSON Pointer>" (e.g. jev:/answers/category/confidence); jev: binds
the full response. Bound values are validated natively; required missing values
fail without falling back to caller data. Named Jev answers override overlapping original input
fields; the combined facts must satisfy the aityx schema. Noul becomes a number
in [0,1], choice a string and score a number, without thresholding or rounding.
After successful Jev execution, a model failure returns HTTP 200 with
decision_error and Jev answers. Successful execution has no decision_error. That completed
Jev execution is charged at execution prices. Upstream Jev failure does not run aityx.
All responses are synchronous. Jev latency is separate from local evaluation.

`POST /v1/systemone`
