Skip to main content

Models

Three ways to use Holo

Agent loop

Multi-turn. Conversation and screenshots in, the next action out. Holo as the brain of your own agent.

Element localization

Single-turn. A screenshot and a target description in, click coordinates out.

Document OCR

Single-turn. A page image in, its full text out.
Prefer to try Holo without writing code? HoloTab runs it in your browser with no setup.

Run Holo on your own GPU

The API is the fastest way to start, but you do not need it. Holo3.1 is open weights under Apache 2.0. The Holo3.1 collection on Hugging Face has four sizes, from 0.8B for on-device to the 35B served by this API, plus FP8, GGUF, and NVFP4 checkpoints of the 35B for smaller GPUs. See Hosted or local models for llama.cpp and vLLM setups.

Benchmarks

Holo3.1 35B-A3B against the previous generation and comparable open models. Best score per row in bold.
Overall averages the four H Corporate benchmarks (E-Commerce, Business Software, Collaboration, Multi-Apps) first, then takes the mean across OSWorld, Android World, H Corporate, ScreenSpot-Pro, and OSWorld-G. Baselines are evaluated by H; starred numbers are reported from the original source. OSWorld runs on H’s internal implementation of the benchmark, so numbers differ slightly from the official OSWorld-Verified leaderboard.

FAQ

Start with holo3-1-35b-a3b. It is on the free tier, has native function calling, and its latency suits interactive loops. Move to holo3-122b-a10b for complex multi-step tasks and novel environments. Switching is a model ID change.
The credit dashboard shows your balance and usage.
By a few cents, yes. The balance is checked before a request runs, so a large request on a low balance can overshoot. If it keeps growing, contact support@hcompany.ai.
Unused credits may expire one year after purchase and are not refundable by default. Regional obligations may apply. See the terms of use.
Request time, model, and token counts. Prompts and responses are not stored: the API uses zero data retention by default. H runs its own models, so inputs and outputs are never shared with third parties. See the privacy policy.
No. IDs are stable. Before a model is removed, its deprecation_date is set in GET /v1/models and a notice appears on this page. After removal, requests to the old ID fail with model_not_found. Pin an ID in production and check deprecation_date when you upgrade.
Last modified on September 11, 2026