GLiDE decisions

POST https://api.fastino.ai/v1/systemone

Send a state (the situation to evaluate) and one or more named questions, each typed noul, choice, or score. GLiDE returns calibrated probabilities directly — there’s no generated text to parse. See the Inference API overview for authentication and cold-start/retry behavior shared across Fastino’s inference interfaces. The full /v1/systemone request and response contract — Noul, Choice, and Score shapes, limits, and confidence — lives on Decision Models, with a dedicated page per primitive. This page covers the raw HTTP contract.

Example

curl -s https://api.fastino.ai/v1/systemone \
  -H "X-API-Key: $FASTINO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "fastino/glide",
    "state": "Refund request: the receipt is attached, the purchase was 10 days ago, and refunds are allowed within 30 days.",
    "questions": {
      "refund_allowed": {
        "type": "noul",
        "instructions": "Does this request qualify for a refund?",
        "criteria": { "true": "Qualifies", "false": "Does not qualify" }
      }
    }
  }'

Response

{
  "model": "glide",
  "answers": {
    "refund_allowed": {
      "type": "noul",
      "noul": 0.99767683794902,
      "confidence": 0.9953536758980399
    }
  },
  "usage": { "input_tokens": 89, "output_tokens": 1 },
  "token_usage": 90
}

Check which deployments currently support GLiDE decisions the same way you’d check for GLiNER encoder support, with task_type=systemone:

curl "https://api.fastino.ai/v1/base-models?supports_inference=true&task_type=systemone"

Decision Models

The full /v1/systemone contract — Noul, Choice, and Score request and response shapes, limits, and confidence — with worked examples for each question type.

Errors

Status	Likely cause	Action
`400`	Invalid request or schema	Correct the request fields or schema
`401`	Missing, malformed, or invalid API key	Export a valid `fast_sk_...` key
`402`	Insufficient credits, funding required, or an owner-set daily/monthly spend limit	Add credits or adjust the spend limit
`403`	Payment method, card verification, credit ceiling, or account policy denial	Resolve the billing or account requirement
`404`	Unknown or unsupported model	Use an inference-capable catalog ID
`422`	Request validation failed	Read and correct the field-level validation details
`425`	Deployment is warming	Retry after the indicated delay
`429`	Rate or capacity limit	Respect `Retry-After` and retry with backoff
`503`	Cold start or temporary provider capacity issue	Retry before treating it as terminal

GLiDE does not currently support fine-tuned deployments, so the 409 “fine-tuned model exists but is not deployed” case on /v1/chat/completions doesn’t apply here. See Cold starts and retries for the shared retry pattern.

Get Started

Decision Models

Inference API

Training API

Models

Account

Example

Response

Decision Models

Errors

​Example

​Response

Decision Models

​Errors

Example

Response

Errors