v0 1.5 Medium is a named composite model profile in Vercel’s v0 family. It is designed around generating and editing code for web applications. The maker’s architecture combines a base language model with relevant retrieved context, a Quick Edit path for smaller changes and an AutoFix component that checks and refines generated output.
Give the page or feature to build, the actions its controls should support and the data it should display. A useful brief also states the existing framework, relevant code and the artifact to return. For an interface change, identify the current behavior and what should happen after the correction.
When a task starts from existing code, provide the parts needed to understand the change and explain which behavior to preserve. A focused request can ask for a component, a page or a patch whose relationship with the existing application is clear.
The maker describes a preparation stage that includes the conversation’s relevant context and retrieves specialized material such as documentation, UI examples and project sources. The base model handles new generations or larger changes. Narrow edits, such as updating text, correcting syntax or reordering components, can use the Quick Edit path.
AutoFix checks output while it streams and applies a further pass after generation. The maker also describes a linting step for style inconsistencies and simple errors. These components help prepare the returned code; the application still needs to save and run the artifact in its actual environment to inspect the behavior.
Compare the generated interface with the requested controls, states and data relationships. Provide the observed error or rendering when asking for a follow-up, and name the affected component. This keeps an iteration tied to a concrete part of the application.
The published profile lists a 128,000-token working context. Use that space for relevant sources and requirements, with room for the response. The v0 family’s composite architecture can update its base component without replacing the surrounding workflow, so its profile identity does not itself name immutable base-model weights.
This entry retains the 1.5 Medium profile. The Large profile and the earlier 1.0 Medium have their own identities. A returned code artifact and a running or deployed application remain separate stages that the surrounding development environment completes.
", "aboutText": "v0 1.5 Medium is a named composite model profile in Vercel’s v0 family. It is designed around generating and editing code for web applications. The maker’s architecture combines a base language model with relevant retrieved context, a Quick Edit path for smaller changes and an AutoFix component that checks and refines generated output.\n\n### Describe the application behavior\n\nGive the page or feature to build, the actions its controls should support and the data it should display. A useful brief also states the existing framework, relevant code and the artifact to return. For an interface change, identify the current behavior and what should happen after the correction.\n\nWhen a task starts from existing code, provide the parts needed to understand the change and explain which behavior to preserve. A focused request can ask for a component, a page or a patch whose relationship with the existing application is clear.\n\n### Understand the composite workflow\n\nThe maker describes a preparation stage that includes the conversation’s relevant context and retrieves specialized material such as documentation, UI examples and project sources. The base model handles new generations or larger changes. Narrow edits, such as updating text, correcting syntax or reordering components, can use the Quick Edit path.\n\nAutoFix checks output while it streams and applies a further pass after generation. The maker also describes a linting step for style inconsistencies and simple errors. These components help prepare the returned code; the application still needs to save and run the artifact in its actual environment to inspect the behavior.\n\n### Review and refine the result\n\nCompare the generated interface with the requested controls, states and data relationships. Provide the observed error or rendering when asking for a follow-up, and name the affected component. This keeps an iteration tied to a concrete part of the application.\n\nThe published profile lists a 128,000-token working context. Use that space for relevant sources and requirements, with room for the response. The v0 family’s composite architecture can update its base component without replacing the surrounding workflow, so its profile identity does not itself name immutable base-model weights.\n\nThis entry retains the 1.5 Medium profile. The Large profile and the earlier 1.0 Medium have their own identities. A returned code artifact and a running or deployed application remain separate stages that the surrounding development environment completes.", "editorialOverlay": { "copy_fields": { "practical_html": "Technical example in English
Build an accessible filter control\n\nCreate a vanilla HTML, CSS and JavaScript inventory filter using these rows: Pencil, stock 12; Notebook, stock 0; Eraser, stock 4. Add a labeled 'In stock only' checkbox and a visible result count. Toggling it must update the list and count; an empty result needs a text message. Return editable code and checks for both checkbox states.An editable web-interface artifact with the labeled control, dynamic list/count and behavior checks.Check the stock filter uses quantity greater than zero and the result count matches visible rows.v0-1.5-mdv0 1.5 Medium is Vercel’s composite model profile for web-app code and iterative interface changes. Its maker combines a base language model with specialized retrieval, Quick Edit and AutoFix to prepare and refine generated code.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
v0 1.5 Medium is a named composite model profile in Vercel’s v0 family. It is designed around generating and editing code for web applications. The maker’s architecture combines a base language model with relevant retrieved context, a Quick Edit path for smaller changes and an AutoFix component that checks and refines generated output.
Give the page or feature to build, the actions its controls should support and the data it should display. A useful brief also states the existing framework, relevant code and the artifact to return. For an interface change, identify the current behavior and what should happen after the correction.
When a task starts from existing code, provide the parts needed to understand the change and explain which behavior to preserve. A focused request can ask for a component, a page or a patch whose relationship with the existing application is clear.
The maker describes a preparation stage that includes the conversation’s relevant context and retrieves specialized material such as documentation, UI examples and project sources. The base model handles new generations or larger changes. Narrow edits, such as updating text, correcting syntax or reordering components, can use the Quick Edit path.
AutoFix checks output while it streams and applies a further pass after generation. The maker also describes a linting step for style inconsistencies and simple errors. These components help prepare the returned code; the application still needs to save and run the artifact in its actual environment to inspect the behavior.
Compare the generated interface with the requested controls, states and data relationships. Provide the observed error or rendering when asking for a follow-up, and name the affected component. This keeps an iteration tied to a concrete part of the application.
The published profile lists a 128,000-token working context. Use that space for relevant sources and requirements, with room for the response. The v0 family’s composite architecture can update its base component without replacing the surrounding workflow, so its profile identity does not itself name immutable base-model weights.
This entry retains the 1.5 Medium profile. The Large profile and the earlier 1.0 Medium have their own identities. A returned code artifact and a running or deployed application remain separate stages that the surrounding development environment completes.
POST /v1/chat/completionstexttext| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits v0-1.5-md | Default— |
Fieldmessages | Typemessage[] | RequirementRequired | Values & limits Minimum items: 1 | Default— |
Fieldmessages[].role | Typestring | RequirementRequired | Values & limits Examples: system, user, assistant, tool, function Conditions: These roles are explicitly represented by Source compatibility types; the exact model role set remains model-specific. Model-specific | Default— |
Fieldmessages[].content | Typestring|content_part[]|null | RequirementOptional | Values & limits | Default— |
Fieldmessages[].tool_calls | Typetool_call[] | RequirementOptional | Values & limits | Default— |
Fieldmessages[].tool_call_id | Typestring | RequirementOptional | Values & limits Applies when: role=tool; use actual returned ID | Default— |
Fieldmessages[].name | Typestring | RequirementOptional | Values & limits | Default— |
Fieldmessages[].reasoning_content | Typestring | RequirementOptional | Values & limits Applies when: Round-trip actual returned reasoning where this model uses it | Default— |
Fieldmessages[].reasoning_details | Typeobject|array | RequirementOptional | Values & limits Model-specific | Default— |
Fieldmax_tokens | Typeinteger | RequirementOptional | Values & limits Minimum: 1 Model-specific | Default— |
Fieldmax_completion_tokens | Typeinteger | RequirementOptional | Values & limits Minimum: 1 Model-specific | Default— |
Fieldstream | Typeboolean | RequirementOptional | Values & limits | Defaultfalse |
Fieldstream_options.include_usage | Typeboolean | RequirementOptional | Values & limits Model-specific | Default— |
Fieldtemperature | Typenumber | RequirementOptional | Values & limits Model-specific | Default— |
Fieldtop_p | Typenumber | RequirementOptional | Values & limits Model-specific | Default— |
Fieldstop | Typestring|string[] | RequirementOptional | Values & limits Model-specific | Default— |
Fieldtools | Typefunction_tool[] | RequirementOptional | Values & limits Model-specific | Default— |
Fieldtools[].type | Typestring | RequirementOptional | Values & limits function Model-specific | Default— |
Fieldtools[].function.name | Typestring | RequirementRequired | Values & limits Applies when: function tool supplied | Default— |
Fieldtools[].function.description | Typestring | RequirementOptional | Values & limits | Default— |
Fieldtools[].function.parameters | TypeJSON_schema | RequirementOptional | Values & limits | Default— |
Fieldtool_choice | Typestring|object | RequirementOptional | Values & limits Model-specific | Default— |
Fieldparallel_tool_calls | Typeboolean | RequirementOptional | Values & limits Model-specific | Default— |
Fieldresponse_format | Typeobject | RequirementOptional | Values & limits Model-specific | Default— |
Fieldreasoning_effort | Typestring | RequirementOptional | Values & limits Model-specific | Default— |
Fieldreasoning | Typeobject | RequirementOptional | Values & limits Model-specific | Default— |
Fieldservice_tier | Typestring | RequirementOptional | Values & limits Model-specific | Default— |
Fieldinstructions | Typestring | RequirementOptional | Values & limits Compatibility field | Default— |
Fieldfunctions | Typefunction[] | RequirementOptional | Values & limits Model-specific | Default— |
Fieldfunction_call | Typestring|object | RequirementOptional | Values & limits Model-specific | Default— |
Fieldprompt_cache_options | Typeobject | RequirementOptional | Values & limits Model-specific | Default— |
Fieldmodalities | Typestring[] | RequirementOptional | Values & limits text | Default— |
Fieldprovider | Typeobject | RequirementOptional | Values & limits Conditions: provider.options is rejected on this Ultra text route | Default— |
Fieldcache_control.ttl | Typestring | RequirementOptional | Values & limits Conditions: 1h is rejected in actual prompt-cache locations | Default— |
Text · UTF8 text
messages[].content
| Parameter | Contract |
|---|---|
Parametercontent_type | Contractapplication/json |
Parameterrequired | Contractmodel, messages |
Parametermaterial_types | Contracttext |
Parametermessages | Contractmessage array with role/content shape |
Parameterfile_material | Contractactual UTF-8 document inserted as literal text; no file ID inferred |
Parameteroptional_controls | Contractstream, temperature, top_p, stop, max_tokens, max_completion_tokens, reasoning, response_format, tools, tool_choice |
Parametercontrol_scope | Contractmodel-specific; user function tools differ from hosted tools |
Parameteroutput_modalities | Contracttext |
Parameterhosted_operations | Contractfalse |
Parametermultimodal_input_binding | Contractnull |
Lifecycle: synchronous_or_streamed
Send exact model ID with messages.
Context length is not an output cap.
A text file may supply literal text; image/audio/file-object inputs need exact binding.
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.0066 / 1K tokens Output · Output tokens $0.033 / 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": "v0-1.5-md", "messages": [{"role": "user", "content": "Explain the difference between an observation and a hypothesis in three sentences."}]}')\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'\nimport json\nfrom pathlib import Path\nr=json.loads(Path("result.json").read_text())\nfor x in r.get("choices",[]):\n if x.get("message",{}).get("content"): print(x["message"]["content"])\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='v0-1.5-md',messages=[{"role":"user","content":"Explain observations and hypotheses in three sentences."}])\nimport base64, json\nfrom pathlib import Path\n\ndef save_result(data, stem="result"):\n # Keep every field, including usage, IDs, reasoning and tool requests.\n Path(stem + ".json").write_text(json.dumps(data, ensure_ascii=False, indent=2), encoding="utf-8")\n print(json.dumps(data, ensure_ascii=False, indent=2))\n def save_blob(encoded, suffix, label):\n raw = base64.b64decode(encoded, altchars=b"-_", validate=True)\n ext = "png" if raw.startswith(b"\\x89PNG\\r\\n\\x1a\\n") else "jpg" if raw.startswith(b"\\xff\\xd8") else "webp" if raw[:4] == b"RIFF" and raw[8:12] == b"WEBP" else suffix\n file = Path(stem + "-" + label + "." + ext)\n file.write_bytes(raw)\n print("Saved", file)\n for index, block in enumerate(data.get("content") or []):\n print("Content", index, json.dumps(block, ensure_ascii=False))\n for choice in data.get("choices") or []:\n print("Choice", choice.get("index"), json.dumps(choice.get("message", choice.get("delta", {})), ensure_ascii=False))\n for index, item in enumerate(data.get("output") or []):\n print("Output", index, json.dumps(item, ensure_ascii=False))\n if item.get("type") == "image_generation_call" and item.get("result"):\n save_blob(item["result"], item.get("output_format") or "bin", "output-" + str(index))\n for ci, candidate in enumerate(data.get("candidates") or []):\n for pi, part in enumerate((candidate.get("content") or {}).get("parts") or []):\n print("Candidate/part", ci, pi, json.dumps(part, ensure_ascii=False))\n blob = part.get("inlineData") or part.get("inline_data")\n if blob and blob.get("data"):\n mime = blob.get("mimeType") or blob.get("mime_type")\n suffix = {"image/png":"png", "image/jpeg":"jpg", "image/webp":"webp", "audio/wav":"wav", "audio/mpeg":"mp3", "video/mp4":"mp4"}.get(mime, "bin")\n save_blob(blob["data"], suffix, "candidate-" + str(ci) + "-part-" + str(pi))\n\nsave_result(result.to_dict(mode="json"))\nfrom openai import OpenAI\nimport os\nfrom pathlib import Path\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)\nimport base64, json\nfrom pathlib import Path\n\ndef save_result(data, stem="result"):\n # Keep every field, including usage, IDs, reasoning and tool requests.\n Path(stem + ".json").write_text(json.dumps(data, ensure_ascii=False, indent=2), encoding="utf-8")\n print(json.dumps(data, ensure_ascii=False, indent=2))\n def save_blob(encoded, suffix, label):\n raw = base64.b64decode(encoded, altchars=b"-_", validate=True)\n ext = "png" if raw.startswith(b"\\x89PNG\\r\\n\\x1a\\n") else "jpg" if raw.startswith(b"\\xff\\xd8") else "webp" if raw[:4] == b"RIFF" and raw[8:12] == b"WEBP" else suffix\n file = Path(stem + "-" + label + "." + ext)\n file.write_bytes(raw)\n print("Saved", file)\n for index, block in enumerate(data.get("content") or []):\n print("Content", index, json.dumps(block, ensure_ascii=False))\n for choice in data.get("choices") or []:\n print("Choice", choice.get("index"), json.dumps(choice.get("message", choice.get("delta", {})), ensure_ascii=False))\n for index, item in enumerate(data.get("output") or []):\n print("Output", index, json.dumps(item, ensure_ascii=False))\n if item.get("type") == "image_generation_call" and item.get("result"):\n save_blob(item["result"], item.get("output_format") or "bin", "output-" + str(index))\n for ci, candidate in enumerate(data.get("candidates") or []):\n for pi, part in enumerate((candidate.get("content") or {}).get("parts") or []):\n print("Candidate/part", ci, pi, json.dumps(part, ensure_ascii=False))\n blob = part.get("inlineData") or part.get("inline_data")\n if blob and blob.get("data"):\n mime = blob.get("mimeType") or blob.get("mime_type")\n suffix = {"image/png":"png", "image/jpeg":"jpg", "image/webp":"webp", "audio/wav":"wav", "audio/mpeg":"mp3", "video/mp4":"mp4"}.get(mime, "bin")\n save_blob(blob["data"], suffix, "candidate-" + str(ci) + "-part-" + str(pi))\n\nwith client.chat.completions.stream(model='v0-1.5-md',messages=[{"role":"user","content":"Explain observations and hypotheses in three sentences."}]) as stream:\n with Path("stream-events.jsonl").open("w",encoding="utf-8") as log:\n for event in stream:\n payload=event.to_dict(mode="json")\n log.write(json.dumps(payload,ensure_ascii=False)+"\\n"); log.flush()\n print(json.dumps(payload,ensure_ascii=False))\n final=stream.get_final_completion()\n save_result(final.to_dict(mode="json"),"stream-result")\njson or SSE
Keep every complete returned response, file and content part.
Keep every choice and its content/tool calls/reasoning. In SSE assemble deltas by choice/tool index, retain the final finish reason and usage.
Keep request/response IDs and headers. No generic text job retrieval URL is supplied.
| Field | Type |
|---|---|
Fieldchoices[].index | Typeinteger |
Fieldchoices[].message.content | Typestring|null |
Fieldchoices[].message.tool_calls | Typetool_call[] |
Fieldchoices[].message.reasoning_content | Typestring |
Fieldchoices[].message.reasoning_details | Typeobject|array |
Fieldchoices[].finish_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 v0-1.5-md
Use the method paths shown above.
v0-1.5-mdv0 1.5 Medium is Vercel’s composite model profile for web-app code and iterative interface changes. Its maker combines a base language model with specialized retrieval, Quick Edit and AutoFix to prepare and refine generated code.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
v0 1.5 Medium is a named composite model profile in Vercel’s v0 family. It is designed around generating and editing code for web applications. The maker’s architecture combines a base language model with relevant retrieved context, a Quick Edit path for smaller changes and an AutoFix component that checks and refines generated output.
Give the page or feature to build, the actions its controls should support and the data it should display. A useful brief also states the existing framework, relevant code and the artifact to return. For an interface change, identify the current behavior and what should happen after the correction.
When a task starts from existing code, provide the parts needed to understand the change and explain which behavior to preserve. A focused request can ask for a component, a page or a patch whose relationship with the existing application is clear.
The maker describes a preparation stage that includes the conversation’s relevant context and retrieves specialized material such as documentation, UI examples and project sources. The base model handles new generations or larger changes. Narrow edits, such as updating text, correcting syntax or reordering components, can use the Quick Edit path.
AutoFix checks output while it streams and applies a further pass after generation. The maker also describes a linting step for style inconsistencies and simple errors. These components help prepare the returned code; the application still needs to save and run the artifact in its actual environment to inspect the behavior.
Compare the generated interface with the requested controls, states and data relationships. Provide the observed error or rendering when asking for a follow-up, and name the affected component. This keeps an iteration tied to a concrete part of the application.
The published profile lists a 128,000-token working context. Use that space for relevant sources and requirements, with room for the response. The v0 family’s composite architecture can update its base component without replacing the surrounding workflow, so its profile identity does not itself name immutable base-model weights.
This entry retains the 1.5 Medium profile. The Large profile and the earlier 1.0 Medium have their own identities. A returned code artifact and a running or deployed application remain separate stages that the surrounding development environment completes.
POST /v1/messagestextjson, sse| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits v0-1.5-md | 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.0066 / 1K tokens Output · Output tokens $0.033 / 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": "v0-1.5-md",\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': 'v0-1.5-md', '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': 'v0-1.5-md', '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 v0-1.5-md
Use the method paths shown above.
Technical example in English
Build an accessible filter control\n\nCreate a vanilla HTML, CSS and JavaScript inventory filter using these rows: Pencil, stock 12; Notebook, stock 0; Eraser, stock 4. Add a labeled 'In stock only' checkbox and a visible result count. Toggling it must update the list and count; an empty result needs a text message. Return editable code and checks for both checkbox states.An editable web-interface artifact with the labeled control, dynamic list/count and behavior checks.Check the stock filter uses quantity greater than zero and the result count matches visible rows.