# Horizon Robotics

> Horizon Robotics (Hong Kong Stock Exchange: 9660.HK, founded 2015) designs the Journey (征程)
> family of automotive AI processors around its own BPU (Brain Processing Unit) architecture and
> ships the smart-driving software stack that runs on them — Horizon Mono ADAS, Horizon SuperDrive,
> TogetheROS, Matrix, QoHo and AIDI. It is not an API business: there is no hosted REST or GraphQL
> product, no OpenAPI document, no pricing page and no self-serve signup. Its developer contract is
> the OpenExplorer (OE) toolchain — a CLI and a set of Python/C++ libraries that take a floating-point
> model to on-board inference — and, on top of that toolchain, two genuine agent surfaces: a live
> unauthenticated remote MCP server and an Apache-2.0 pack of 29 indexed Agent Skills.

This file was GENERATED by API Evangelist from artifacts in this repository on 2026-08-22.
Horizon Robotics does not publish an llms.txt of its own (probed /llms.txt on www.horizon.auto,
developer.horizon.auto, doc.oe.horizon.auto, oe.horizon.auto and mcp.oe.horizon.auto — 404 or SPA
shell on every host). Every URL below was fetched and its status recorded.

## Agent surfaces

- [Open Explorer MCP Server](https://mcp.oe.horizon.auto/mcp): Live remote MCP server, protocol
  2025-06-18, serverInfo "Open Explorer MCP Server" 3.9.0. NO AUTHENTICATION REQUIRED — anonymous
  JSON-RPC POSTs succeed. Four read-only tools: `list_codebases` (list indexed Milvus collections),
  `search_code` (semantic search over indexed Horizon codebases, optional `scope`, `limit` max 50),
  `search_doc` (semantic search over the Horizon document library, default path `oe_doc`, `limit`
  max 20), `get_doc` (read a document by `path` + `docId`, `maxTokens` default 10000). Three
  resources: openexplorer://mcp/overview, /tools, /agent-guide. Install:
  `claude mcp add --transport http oe-mcp https://mcp.oe.horizon.auto/mcp`
- [OE-Skills](https://github.com/HorizonRobotics/OE-Skills): Horizon's own Apache-2.0 Agent Skill
  pack (v0.2.0), 37 SKILL.md files indexed as 29 skills across six modules — HBDK, Horizon Plugin,
  HMCT/quantization, UCP/runtime, horizon_tc_ui and LLM compression. `horizon-router` is the entry
  point and dispatches on each skill's description. Targets Claude Code, Codex and Cursor.

## Developer surface

- [Developer portal](https://developer.horizon.auto/): documentation, forum, blog, training,
  competitions. Chinese-language. An account is needed to download packages, not to read docs.
- [Documentation index](https://developer.horizon.auto/docs): per-generation toolchain and chip
  documentation — Journey 6, Journey 5 (toolchain 1.1.77, microchipVIP 2.02), Journey 3 (1.16.6).
- [OpenExplorer manual](https://doc.oe.horizon.auto/): the canonical toolchain manual (3.0.31).
  WARNING: this host served an EXPIRED TLS CERTIFICATE on 2026-08-22 — a client that verifies
  certificates cannot fetch it.
- [OE package download](https://oe.horizon.auto/): the OpenExplorer release package.
- [Forum](https://developer.horizon.auto/forum): community Q&A, the only support channel found.
- [GitHub](https://github.com/HorizonRobotics): 44 public repositories — ALF, Sparse4D, HoloMotion,
  HoloAgent, EmbodiedGen, RoboOrchard, BIP3D, GUMP and OE-Skills.

## Command-line toolchain (there is no HTTP API for this)

`hb_config_generator` (YAML template), `hb_compile` (compile + PTQ quantize ONNX/Caffe to HBIR/HBM),
`hb_model_info` (inspect .onnx/.bc/.hbm), `hb_verifier` (accuracy + on-board verification),
`hb_eval_preprocess` (evaluation data prep), `hb_analyzer` (latency/bandwidth/BPU-utilisation
analysis). BPU marches: nash-b-lite, nash-b, nash-b-plus, nash-e, nash-m, nash-p, nash-h.
Flow: ONNX/Caffe -> YAML -> PTQ -> HBIR (.bc) -> HBM (.hbm) -> verify / analyse / deploy.

## Libraries

horizon_plugin_pytorch, horizon_plugin_profiler, hbdk4-compiler, hmct (+ hmct-gpu), horizon_tc_ui,
hbDNN, llm_compression, oellm_runtime. NONE is published to a public package registry — npm, PyPI,
Maven Central, NuGet, pkg.go.dev, RubyGems, Packagist and crates.io were all probed and all 404.
They ship only inside the OE package, which requires a portal account.

## Security

- [Product Security Policy](https://www.horizon.auto/en/legal/security): coordinated disclosure,
  report to report_vulnerability@horizon.auto. Safe harbour offered. Advisories carry CVSS ratings.
  In-vehicle findings must be reported within 168 hours of identification. NO bug bounty.
  CAVEAT: the page instructs reporters to encrypt with a PGP key and shows the unfilled placeholders
  "[pgp-public-key.asc]" and "(insert key link)"; no key file is served (404).
  No /.well-known/security.txt on any host.

## Corporate

- [Website](https://www.horizon.auto/en)
- [About](https://www.horizon.auto/en/about)
- [Investor relations](https://www.horizon.auto/investor-relations)
- [Privacy policy](https://www.horizon.auto/en/legal/privacy)
- [Intellectual property notice](https://www.horizon.auto/en/legal/intellectual-property-rights)
- [Contact form](https://www.horizon.auto/message-form)

## What does NOT exist (probed, not assumed)

No OpenAPI/Swagger document. No GraphQL endpoint. No AsyncAPI, webhooks or event stream. No A2A
agent card at /.well-known/agent-card.json or /.well-known/agent.json on any host. No
/.well-known/api-catalog, openid-configuration, oauth-authorization-server or ai-plugin.json.
No status page. No published rate limits. No pricing or plans. No deprecation policy. No SDK on any
public package registry. No Postman collection found.

## Not Horizon Robotics

D-Robotics (地瓜机器人, developer.d-robotics.cc, github.com/D-Robotics, and the renamed
github.com/HorizonRDK org) is a SEPARATE company spun off from Horizon Robotics in 2024 and
independently funded since. Its RDK developer kits, documentation and repositories are NOT
catalogued here and must not be attributed to Horizon Robotics.