Skip to main content
There is no OpenAPI specification and no REST API to call today. The MCP server is the one thing that answers. This page exists so that the absence is stated rather than left to be discovered.

​
The only interface, and it is MCP

There is one interface in the design: the MCP server described in MCP tools and resources. It answers at https://mcp.usehence.com/mcp, over Streamable HTTP, with errands gated to the pilot group. What is missing is a second, REST-shaped door onto the same errands — not HTTP itself — and this page is not pointing you at an 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 is the page to follow; if you are planning an integration that cannot speak MCP, the contract to read against is MCP tools and resources, and the operations will not change shape when they acquire an HTTP surface.