Agnes Sys1 1.0 is generally available through the Agnes AI API. Access and rate limits depend on your account and API key permissions. Responses below are format examples.
Overview
Agnes Sys1 1.0 is an Agnes AI decision model. Describe the current situation instate and define the questions in questions. The response returns structured results under matching keys in answers, rather than a chat completion.
The example in this guide routes a support request to a team and separately evaluates whether the user requests urgent handling. Other possible applications include workflow routing, intent classification, and business-rule screening.
Internal benchmark estimates
These figures come from the team’s internal evaluation summary, where all model results in the supplied column are marked as estimates. They are not independently verified measurements, official Artificial Analysis results, or a public leaderboard ranking. Benchmark versions, sample sizes, and detailed methods have not been published; real-world performance may differ.
The composite is a weighted calculation using the estimates above, rounded to one decimal place. It is not an official AA index score.
Request headers
Use your Agnes API key. Do not place keys in client-side code or public repositories.Input parameters
The following fields are used in the examples on this page. Required-field validation, defaults, and size or quantity limits are subject to the current service specification.Choice question
Usetype: "choice" and provide candidate options in criteria. In this example, the option keys are billing, technical, and sales. The selected key is returned in answers.route.choice.
Numeric question: noul
The example uses type: "noul" for an urgency question and receives a numeric value in answers.urgent.noul. Keep the type string exactly as noul.
Preserve the numeric
noul result returned by the service. Do not infer a calibrated probability, an allowed range, or a fixed business threshold from a single example; validate your decision rules against the production specification.Create a decision request
Use the dedicatedPOST /v1/systemone decision endpoint with the following request body. It is not the Chat Completions endpoint.
Response example
The following illustrates the response format. Decision results are returned underanswers; the response is not a Chat Completions choices object.
Response fields
Read each result using its question name:
answers.route.choice gives the selected team, while answers.urgent.noul gives the numeric result. Do not parse a prose answer or a message.content field.
The example selects billing, which corresponds to “Billing and payment support.” The confidence score is a separate returned field; do not substitute the largest option probability for it.
Pricing
All prices below are in USD.1M tokens means one million tokens.
Input charge = reported input tokens ÷ 1,000,000 ×
$0.03
Structured decision output is free. The zero output-token count in this sample is a reported usage value, not a reason to ignore the answers object.
The input-token counting scope, account availability, and final billing details are subject to the production service specification and account bill.
Integration checklist
- Use
agnes-sys1-1.0inmodel. - Send
stateandquestions; do not replace them with chat-model fields such asmessages. - Keep question names consistent with the result keys under
answers. - Preserve the type names
choiceandnoul. - Retain
usagewhen recording request usage. - Confirm your account permissions and validate your numeric decision rules against the current service specification.