Skip to content

Beta: these docs are still being updated. The next full update is on 18 November at 8 PM UTC. Docs in beta. Full update 18 Nov, 8 PM UTC.

Hoody.com

Lookup tables for Hoody Decide.

POST https://ai.hoody.com/api/v1/systemone or POST https://ai.hoody.com/api/v1/decisions, with a JSON body.

FieldRule
modelhoody-ai/hoody-decide, or the accepted aliases hoody/hoody-decide and hoody-decide. Responses always name it hoody-ai/hoody-decide. A request naming it is answered by a decision model Hoody chooses
stateWhat the questions are about. A string, a JSON object, or a JSON array
questionsAn object mapping each question name (1 to 256 characters) to a question. Every name comes back as a key of answers. A request carries 1 to 64 questions
type (per question)noul, choice or score (question types). The box type is not supported
instructions (per question)Required on every question. A string, object or array that says what to decide
criteria (per question)Depends on the type (question types)
Other top-level fieldsOmit them: they do not control the decision, and some names are still validated and can cause a 400 response
Repeated top-level fieldsDo not repeat top-level field names (duplicate_root_key and invalid_decision_request)

hoody-decide is not a catalog entry, so /api/v1/ai/models does not list it.

How to choose a type: Write the questions.

typecriteriaAnswer fields
noulOptional: an object with exactly "true" and "false", each a string, object or arraytype: "noul" and noul, the probability of yes from 0 to 1
choiceRequired: an object of 1 to 255 non-empty labels, each mapped to a string, object, array or null descriptiontype: "choice", choice (a label with the highest probability), confidence from 0 to 1, and a probabilities object covering every label
scoreRequired: an array of 2 to 10 level descriptions (string, object or array, never null), lowest firsttype: "score", score from 0 to the number of levels minus 1 (it may be fractional), confidence from 0 to 1, and probabilities and legend objects keyed "0", "1", and so on
  • Every probability is between 0 and 1.
  • For choice and score, the probabilities may sum to anything within 0.02 of 1, because of rounding.
  • A score approximates the probability-weighted level index; it need not equal the weighted sum of the returned probabilities exactly.
  • legend maps each index back to its level description after image normalization. Image parts retain only type: "image_url" and image_url: { "url": "..." }.

How to send an image, the accepted formats and the size limits: Send images in the state.

RuleDetail
What is read as an image partAny object in state, at any depth, with a key named image, image_url, input_image, file or file_data (case-sensitive), or a type of image, image_url, input_image, file or input_file (case-insensitive)
If it is not a valid image partThe request fails with 400 invalid_decision_request, so a plain object such as { "file": "app.log" } is refused. Rename such keys, or send the state as a string (for example the JSON text of the object)
Strings that begin with data:Strings beginning with data: after leading whitespace (case-insensitive) are accepted only as the URL inside a valid image part. Elsewhere in state, instructions or criteria descriptions, they cause 400 invalid_decision_request
Where else the rule appliesQuestion instructions and criteria descriptions (the noul and choice description values and the score levels)
Where it does not applychoice label names can be any non-empty string, including file or image
WhatLimit
Questions per request64
Labels per choice question255
Levels per score question2 to 10
Text in state (images not counted)128 KiB
Images per request4, 1 MiB each, inline only
Estimated input tokens per request32,000
Whole request body8 MiB
  • Token estimate: it covers the state, the questions and the images, and the state can count more than once when you ask several questions, so a request can fit every byte limit and still be over the token limit.
  • Over a limit: a body over 8 MiB gets 413; the response may be plain text without a JSON error code. Exceeding the other request limits, or using a shape the decision models cannot answer, gets 400 invalid_decision_request.
  • The reason: read error.message; it does not always name a field or the exact excess.

When a decision limit runs out, the request is refused with 429 decision_limit_reached until it frees up. The body has this shape, with <text> and <seconds> standing for the message and the wait:

{
"error": {
"type": "rate_limit_exceeded",
"code": "decision_limit_reached",
"message": "<text>",
"limit": "per_day_tokens",
"retry_after_seconds": <seconds>,
"reset_at": "2026-10-19T09:41:07Z"
}
}
FieldMeaning
limitThe kind of limit reached: per_minute_requests, per_day_requests, per_day_questions, per_day_tokens or concurrent
messageText for people; branch on code and limit
retry_after_secondsThe wait. The Retry-After header carries the same wait
reset_atThat time in UTC

The status and code say whether to change the request or wait and retry.

StatuscodeMeaning
400invalid_bodyThe body could not be accepted as a JSON request. Check its encoding, JSON syntax and field types, and omit extra top-level fields.
400duplicate_root_keyA model-selection field (model, models, fallbacks or preset) appears more than once. Remove the duplicate.
400invalid_decision_requestDecision validation failed, another top-level field is duplicated, a request limit was exceeded, or the AI service refused the request. Read error.message and revise the request.
400decision_requires_computerCall it from inside a computer with the computer token.
400decision_model_endpoint_unsupportedThe model was named on another endpoint. Use POST /api/v1/systemone or POST /api/v1/decisions.
413invalid_decision_request or no JSON code (plain-text response)The body is over 8 MiB.
429decision_limit_reachedA decision limit of the computer’s server is used up. Retry after Retry-After.
503decision_capacity_exhaustedDecisions are at capacity right now. Retry after Retry-After.
503decision_routing_unavailableDecisions are unavailable right now. Retry after Retry-After.
503free_owner_identity_missingHoody could not tell which account owns the computer. Contact support if it persists.