> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zerogpu.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# gliner2.5-decide-v1

> Model details for gliner2.5-decide-v1. Zero-shot decision and classification with caller-supplied labels.

> Fastino's GLiNER2.5 Decide is a 486M-parameter zero-shot decision and classification model built for operational AI workflows. You supply the labels or decision options at request time to classify intent, route agents and tools, triage support requests, make moderation decisions, detect completion, and determine when a request needs human handoff. It handles single-label, multi-label, and several decision heads in one call, which suits high-volume routing and decision workloads where speed and structured outputs matter.

**References:** [Model docs](https://huggingface.co/fastino/GLiNER2.5-Decide) • [Terms](https://github.com/fastino-ai/GLiNER2/blob/main/LICENSE) • [Privacy](https://github.com/fastino-ai/GLiNER2/blob/main/LICENSE)


## OpenAPI

````yaml api-reference/openapi/playgrounds/gliner2_5-decide-v1.openapi.json POST /responses
openapi: 3.1.0
info:
  title: gliner2.5-decide-v1 playground
  version: '1.0'
  description: >-
    Interactive playground for **gliner2.5-decide-v1**.

    Model is always `gliner2.5-decide-v1` on this page (shown in the form, not
    editable).

    Use the **request example** selector to switch use cases (decide,
    classification).

    Authentication: `x-api-key` (required) and `x-project-id` (optional).
servers:
  - url: https://api.zerogpu.ai/v1
    description: Production
security:
  - ApiKey: []
paths:
  /responses:
    post:
      tags:
        - gliner2.5-decide-v1
      summary: 'gliner2.5-decide-v1: Responses'
      operationId: createResponse_gliner2_5-decide-v1
      parameters:
        - name: x-project-id
          in: header
          required: false
          schema:
            type: string
          description: >-
            Optional project identifier. Scopes the request to a specific
            project when provided.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              allOf:
                - $ref: '#/components/schemas/CreateResponseRequest'
                - type: object
                  properties:
                    model:
                      type: string
                      const: gliner2.5-decide-v1
                      default: gliner2.5-decide-v1
                      example: gliner2.5-decide-v1
                      description: >-
                        Model identifier (fixed for this playground). Use
                        request examples to change use cases.
            examples:
              decide:
                summary: Decision / Routing
                value:
                  input: >-
                    The customer says their payment failed and they want someone
                    to call them.
                  model: gliner2.5-decide-v1
                  metadata:
                    labels:
                      intent:
                        - payment_issue
                        - refund
                        - account_access
                        - general_question
                      handoff:
                        - 'yes'
                        - 'no'
                    usecase: decide
              classification:
                summary: Text Classification
                value:
                  input: >-
                    I absolutely love this product! The quality is outstanding
                    and the customer service was incredibly helpful.
                  model: gliner2.5-decide-v1
                  metadata:
                    schema:
                      sentiment:
                        - positive
                        - negative
                        - neutral
                    usecase: classification
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Response'
        '400':
          description: Bad request
        '401':
          description: Unauthorized
        '403':
          description: Forbidden
        '420':
          description: Insufficient quota
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: Internal server error
components:
  schemas:
    CreateResponseRequest:
      type: object
      required:
        - model
        - input
      properties:
        model:
          type: string
          const: gliner2.5-base-v1
          default: gliner2.5-base-v1
          example: gliner2.5-base-v1
          description: >-
            Model identifier (fixed for this playground). Use request examples
            to change use cases.
        input:
          type: string
          minLength: 1
          format: textarea
          maxLength: 131072
          description: Multi-line text or document content to send to the model.
        metadata:
          type: object
          description: >-
            Use-case options for the model. Three use cases are supported:

            - `ner` — extract entities for the given `labels`.

            - `json` — extract structured fields defined by a `schema`.

            - `classification` — assign labels from candidate sets defined by a
            `schema`.
          additionalProperties: true
          properties:
            usecase:
              type: string
              enum:
                - ner
                - json
                - classification
              default: ner
              description: >-
                Which operation to run and which other fields apply: `ner` uses
                `labels`; `json` and `classification` use `schema`.
            labels:
              type: array
              items:
                type: string
              example:
                - programming language
                - database
                - technology
                - protocol
              description: >-
                Entity types to extract, used when `usecase` is `ner`. Each
                label becomes a key in the returned `entities` object.
            threshold:
              type: number
              minimum: 0
              maximum: 1
              default: 0.5
              description: >-
                Minimum confidence score (0–1) an entity must reach to be
                returned (used with `ner`). Lower values surface more,
                lower-confidence matches.
            schema:
              type: object
              additionalProperties:
                type: array
                items:
                  type: string
              description: >-
                Extraction/classification definition, used when `usecase` is
                `json` or `classification`. For `json`, each group maps to field
                definitions in `name::type::description` form (e.g.
                `"email::str::Email address"`). For `classification`, each group
                maps to a list of candidate labels (e.g. `["positive",
                "negative", "neutral"]`).
              example:
                contact:
                  - name::str::Full name
                  - email::str::Email address
                  - phone::str::Phone number
    Response:
      type: object
      additionalProperties: true
    ErrorResponse:
      type: object
      additionalProperties: true
  securitySchemes:
    ApiKey:
      type: apiKey
      in: header
      name: x-api-key

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.