Skip to main content
The Models API is OpenAI-compatible: point the official OpenAI client (or any compatible library) at H Company’s endpoint. You opt into Holo-specific behavior (structured outputs, reasoning, and the coordinate convention) through a few extra request fields and conventions documented here.

Endpoints

POST /chat/completions

The inference endpoint: parameters, response fields, streaming.

GET /v1/models

Discover served models, limits, pricing, and deprecation dates at runtime.

Endpoint and auth

Model IDs, per-model limits, pricing, and tiers live on the Models page.

The two response channels

Every call returns message.content (the action or answer) and message.reasoning (the thinking trace, read-only). Field-by-field details are in the chat completions reference; how to carry state across turns is in the Agent loop.

Conventions

Coordinates in [0, 1000]

Click positions are integers normalized to the image you sent, origin top-left. Scale back with the image’s own dimensions: Coordinates.
Keep at most the last 3 screenshots in context for best accuracy, even though a request accepts up to 5 images. See the trim helper in the agent loop.
Structured outputs work on both models. Native function calling (tools / tool_calls) is holo3-1-35b-a3b only. Pick one and stay in it: Agent loop.
structured_outputs and chat_template_kwargs are top-level body fields. Pass them via extra_body (Python) or an untyped spread (TypeScript): Chat completions.

Next steps

Chat completions

Full parameter and response reference.

Models

IDs, limits, pricing, lifecycle.

Agent loop

How to use Holo in your computer-use harness.
Last modified on September 11, 2026