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

# OpenAPI

> There is no HTTP API, and no specification for one yet. What is planned, why MCP came first, and what to plan against.

<Note>
  **There is no OpenAPI specification and no HTTP API to call today.** This page exists so that the
  absence is stated rather than left to be discovered.
</Note>

## The only interface, and it is not live either

There is one interface in the design: the MCP server described in
[MCP tools and resources](/reference/mcp-tools). It is not answering yet — the execution server is
still being built, so nothing is callable today over any protocol, and this page is not pointing you
at a working alternative.

What is settled is the shape. The tool surface *is* the contract rather than a subset of some larger
one, and our own product surfaces are clients of the same server rather than of a private side
door.

## What is planned

An OpenAPI twin of that contract, with the same operations, the same task object and the same
published ceilings, plus an interactive playground on this site. It is planned for the phase that
opens Hence to partner integrations, because that is the point at which a caller who is not an
assistant needs a way in.

Two things are already decided about it:

* **It is generated from a specification file**, so it cannot drift from the tool surface by being
  written separately.
* **It adds no capability.** Anything an HTTP caller can do, an MCP client can already do, and the
  same admission checks, approvals and ceilings apply.

## Until then

Plan against the MCP server rather than waiting for an HTTP one. If you are integrating an
assistant, [Connect any MCP client](/connect/mcp) is the page to follow once the server answers; if
you are planning an integration that cannot speak MCP, the contract to read against is
[MCP tools and resources](/reference/mcp-tools), and the operations will not change shape when they
acquire an HTTP surface.