s1 provides a listed 32,000-token context and text conversation methods. A practical research task is comparing several supplied source excerpts and returning a claim-by-claim evidence map, separating agreement, disagreement and unanswered questions.
The S1 deep-search name does not by itself establish automatic browsing, a search-control field or a special report object in the accepted methods. Choose it for a written conversation over supplied evidence; a workflow that must discover current sources needs explicit retrieval support. Chat Completions and Messages are listed, with max_tokens required for Messages. This record does not establish a quality or search-depth difference from S3.
", "aboutText": "s1 provides a listed 32,000-token context and text conversation methods. A practical research task is comparing several supplied source excerpts and returning a claim-by-claim evidence map, separating agreement, disagreement and unanswered questions. The S1 deep-search name does not by itself establish automatic browsing, a search-control field or a special report object in the accepted methods. Choose it for a written conversation over supplied evidence; a workflow that must discover current sources needs explicit retrieval support. Chat Completions and Messages are listed, with max_tokens required for Messages. This record does not establish a quality or search-depth difference from S3.", "editorialOverlay": { "copy_fields": { "about_html": "s1 provides a listed 32,000-token context and text conversation methods. A practical research task is comparing several supplied source excerpts and returning a claim-by-claim evidence map, separating agreement, disagreement and unanswered questions.
The S1 deep-search name does not by itself establish automatic browsing, a search-control field or a special report object in the accepted methods. Choose it for a written conversation over supplied evidence; a workflow that must discover current sources needs explicit retrieval support. Chat Completions and Messages are listed, with max_tokens required for Messages. This record does not establish a quality or search-depth difference from S3.
", "short_text": "A separately named 32,000-token text profile for a supplied-evidence research conversation." }, "copy_sha256": "8041bee02b664907726a8375a4bd466e8f45b4b8ca86671aa4c5e6a9b0910f9f", "copy_source": { "locale": "en", "pack_sha256": "0f56d90ba41881e1134accf82e57338f246f8753ca4c0cee929aaffada5d10e7", "record_model_id": "s1", "source_facts_sha256": "63c90dbd72832452a5a09ad51f1c940bcec047660019163421974f32c711936d", "validation_sha256": "a2ac2f28056280fc0b2ea34a501bf156d5ce155406e57e708edf30bfdf6bfdc6" }, "html_sha256": "1937d64a6b7318525805272a0eab597433f7aaddb23ac8d70a9bccdb242883e0", "module_sha256": "ee9dc1c50b1e6a8fb7fa062030fcb4646b9aaaeb08be513b723a5a92a7290f06", "raw_model_unchanged": true, "schema": "ailoot-native-model-editorial-v1" }, "locale": "en", "methods": [ { "html": "s1A separately named 32,000-token text profile for a supplied-evidence research conversation.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
s1 provides a listed 32,000-token context and text conversation methods. A practical research task is comparing several supplied source excerpts and returning a claim-by-claim evidence map, separating agreement, disagreement and unanswered questions.
The S1 deep-search name does not by itself establish automatic browsing, a search-control field or a special report object in the accepted methods. Choose it for a written conversation over supplied evidence; a workflow that must discover current sources needs explicit retrieval support. Chat Completions and Messages are listed, with max_tokens required for Messages. This record does not establish a quality or search-depth difference from S3.
POST /v1/chat/completionstextjson, sse| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits s1 | Default— |
Fieldmessages | Typemessage[] | RequirementRequired | Values & limits | Default— |
Fieldmessages[].role | Typestring | RequirementRequired | Values & limits | Default— |
Fieldmessages[].content | Typestring | RequirementRequired | Values & limits | Default— |
Fieldstream | Typeboolean | RequirementOptional | Values & limits | Defaultfalse |
owned_text_messages
| Parameter | Contract |
|---|---|
Parametercontent_type | Contractapplication/json |
Parameterrequired | Contractmodel, messages |
Parametermaterial_types | Contracttext |
Parametermessages | Contractmessage array with role and literal string content |
Parameterfile_material | ContractActual UTF-8 material may be inserted as literal string content; no file reference is inferred. |
Parameteroptional_controls | Contractstream |
Lifecycle: synchronous_json_or_sse
Tariff references do not add request options. Supported parameters are listed for the selected method.
| Configuration | Rate schedule | Charge |
|---|---|---|
| ConfigurationBase token rates | Rate scheduleBase rate | Charge Input · Input tokens $0.0006 / 1K tokens Output · Output tokens $0.0006 / 1K tokens Input · Cache read $0 / 1K tokens Input · Cache write $0 / 1K tokens Input · Cache write, 1 hour — / 1K tokens |
Ailoot reserves an estimated amount before a request. After the result, it settles the final charge from measured usage. Streaming settlement uses the final usage record. How reservation and settlement work →
set -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\npython3 - <<'PY_REQUEST'\nimport json,os\nfrom pathlib import Path\np=json.loads('{"model":"s1","messages":[{"role":"user","content":"hello"}],"stream":false}')\n\nPath("request.json").write_text(json.dumps(p,ensure_ascii=False))\nPY_REQUEST\ncurl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/chat/completions \\\n -H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \\\n --data-binary @request.json -D response-headers.txt -o result.json\npython3 - <<'PY_RESULT'\nfrom pathlib import Path\nprint(Path("result.json").read_text(encoding="utf-8"))\nPY_RESULT\nfrom openai import OpenAI\nimport os\n\nif not os.environ.get("AILOOT_API_KEY", "").strip(): raise SystemExit("Set AILOOT_API_KEY before making a request")\nclient=OpenAI(base_url="https://api.ailoot.ai/v1",api_key=os.environ["AILOOT_API_KEY"],max_retries=0)\nresult=client.chat.completions.create(model="s1", messages=[{"role":"user","content":"hello"}], stream=False)\nimport json\nfrom pathlib import Path\n\ndata = result.to_dict(mode="json")\nPath("result.json").write_text(json.dumps(data, ensure_ascii=False, indent=2), encoding="utf-8")\nprint(json.dumps(data, ensure_ascii=False, indent=2))\nset -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\npython3 - <<'PY_REQUEST'\nimport json,os\nfrom pathlib import Path\np=json.loads('{"model":"s1","messages":[{"role":"user","content":"hello"}],"stream":true}')\n\nPath("request.json").write_text(json.dumps(p,ensure_ascii=False))\nPY_REQUEST\ncurl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/chat/completions \\\n -H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \\\n --data-binary @request.json -D response-headers.txt -o result.sse\nJSON or text/event-stream
Keep every complete returned response, file and content part.
Retain the complete JSON or SSE bytes, response headers, returned usage and all supplied result fields. No model-specific output family is asserted.
Preserve the original response and attempt identity; no new job polling or resubmission is inferred.
| Field | Type | Meaning |
|---|---|---|
Fieldcomplete response JSON | Typeobject | MeaningPreserve every returned field without assuming a model-specific result family. |
FieldSSE data events | Typestream | MeaningPreserve every returned event and terminal marker without selecting only text fields. |
Ailoot Ultra s1
Use the method paths shown above.
s1A separately named 32,000-token text profile for a supplied-evidence research conversation.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
s1 provides a listed 32,000-token context and text conversation methods. A practical research task is comparing several supplied source excerpts and returning a claim-by-claim evidence map, separating agreement, disagreement and unanswered questions.
The S1 deep-search name does not by itself establish automatic browsing, a search-control field or a special report object in the accepted methods. Choose it for a written conversation over supplied evidence; a workflow that must discover current sources needs explicit retrieval support. Chat Completions and Messages are listed, with max_tokens required for Messages. This record does not establish a quality or search-depth difference from S3.
POST /v1/messagestextjson, sse| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits s1 | Default— |
Fieldmessages | Typemessage[] | RequirementRequired | Values & limits | Default— |
Fieldmessages[].role | Typestring | RequirementRequired | Values & limits user, assistant | Default— |
Fieldmessages[].content | Typestring | RequirementRequired | Values & limits | Default— |
Fieldmax_tokens | Typeinteger | RequirementRequired | Values & limits | Default— |
Fieldstream | Typeboolean | RequirementOptional | Values & limits | Defaultfalse |
Text · UTF-8 text
messages[].content string
| Parameter | Contract |
|---|---|
Parametercontent_type | Contractapplication/json |
Parameterrequired | Contractmodel, messages, max_tokens |
Parameteroptional_controls | Contractstream |
Parametermaterial_types | Contracttext |
Parametertext_file_material | ContractRead the actual UTF-8 document and put its text in the indicated input or message content string. |
Lifecycle: synchronous_or_streamed
Tariff references do not add request options. Supported parameters are listed for the selected method.
| Configuration | Rate schedule | Charge |
|---|---|---|
| ConfigurationBase token rates | Rate scheduleBase rate | Charge Input · Input tokens $0.0006 / 1K tokens Output · Output tokens $0.0006 / 1K tokens Input · Cache read $0 / 1K tokens Input · Cache write $0 / 1K tokens Input · Cache write, 1 hour — / 1K tokens |
Ailoot reserves an estimated amount before a request. After the result, it settles the final charge from measured usage. Streaming settlement uses the final usage record. How reservation and settlement work →
{\n "model": "s1",\n "max_tokens": 128,\n "messages": [\n {\n "role": "user",\n "content": "Summarize the incident report."\n }\n ],\n "stream": false\n}set -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\n: "${AILOOT_TEXT_FILE:?Set your actual UTF-8 document}"\nexport AILOOT_TEXT_FILE\npython3 - <<'PY_REQUEST'\nimport json, os\nfrom pathlib import Path\n\nsource_file = Path(os.environ['AILOOT_TEXT_FILE'])\nif not source_file.is_file():\n raise SystemExit('Set AILOOT_TEXT_FILE to your actual UTF-8 document')\ntext = source_file.read_text(encoding='utf-8')\nif not text.strip():\n raise SystemExit('Choose a document containing text')\npayload = {'model': 's1', 'max_tokens': 128, 'messages': [{'role': 'user', 'content': 'Summarize the incident report.'}]}\npayload['messages'][0]['content'] = 'Summarize this material and quote supporting source passages.\\n\\n' + text\nPath('request.json').write_text(json.dumps(payload, ensure_ascii=False), encoding='utf-8')\nPY_REQUEST\ncurl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/messages \\\n -H "x-api-key: $AILOOT_API_KEY" -H 'anthropic-version: 2023-06-01' -H 'Content-Type: application/json' \\\n --data-binary @request.json -D response-headers.txt -o result.json\npython3 - <<'PY_RESULT'\nimport json\nfrom pathlib import Path\n\nresult = json.loads(Path('result.json').read_text(encoding='utf-8'))\nprint(json.dumps(result, ensure_ascii=False, indent=2))\nPY_RESULT\nimport json, os\nfrom pathlib import Path\n\nsource_file = Path(os.environ['AILOOT_TEXT_FILE'])\nif not source_file.is_file():\n raise SystemExit('Set AILOOT_TEXT_FILE to your actual UTF-8 document')\ntext = source_file.read_text(encoding='utf-8')\nif not text.strip():\n raise SystemExit('Choose a document containing text')\npayload = {'model': 's1', 'max_tokens': 128, 'messages': [{'role': 'user', 'content': 'Summarize the incident report.'}]}\npayload['messages'][0]['content'] = 'Summarize this material and quote supporting source passages.\\n\\n' + text\nfrom urllib.request import Request, urlopen\nfrom urllib.error import HTTPError\n\napi_key = os.environ['AILOOT_API_KEY']\nif not api_key.strip():\n raise SystemExit('Set AILOOT_API_KEY before making a request')\nheaders = {'x-api-key': 'PLACEHOLDER_KEY', 'anthropic-version': '2023-06-01', 'Content-Type': 'application/json'}\nheaders['x-api-key'] = api_key\nrequest = Request('https://api.ailoot.ai/v1/messages', data=json.dumps(payload, ensure_ascii=False).encode('utf-8'), headers=headers, method='POST')\ntry:\n with urlopen(request, timeout=120) as response:\n raw = response.read()\n Path('response-headers.txt').write_text(str(response.headers), encoding='utf-8')\nexcept HTTPError as error:\n Path('result.json').write_bytes(error.read())\n Path('response-headers.txt').write_text(str(error.headers), encoding='utf-8')\n raise\nPath('result.json').write_bytes(raw)\nimport json\nfrom pathlib import Path\n\nresult = json.loads(Path('result.json').read_text(encoding='utf-8'))\nprint(json.dumps(result, ensure_ascii=False, indent=2))\nJSON or SSE
Keep every complete returned response, file and content part.
Keep all content blocks, thinking signatures and actual tool-use IDs. Assemble all SSE block deltas; a first text block is not the complete output.
Keep request/response IDs and headers. No generic text job retrieval URL is supplied.
| Field | Type |
|---|---|
Fieldid | Typestring |
Fieldmodel | Typestring |
Fieldcontent[] | Typetext|thinking|tool_use|other content block |
Fieldstop_reason | Typestring|null |
Fieldusage | Typeobject |
| Response | Condition | Next step |
|---|---|---|
Response400 · invalid_request_error | ConditionInvalid required fields, material representation or parameter value | Next stepCorrect the indicated fields before a new creation request. |
Ailoot Ultra s1
Use the method paths shown above.