AI Interface

API

Interface

API

Status

Planned

Purpose

Use supported ASUME capabilities and outputs programmatically.

Works with

Maintained understanding

The ASUME API is the planned programmatic interface to ASUME. It is intended for teams that want to use supported company-understanding and objective capabilities inside their own products, workflows, and internal systems.

The API will work with the maintained understanding ASUME already holds rather than requiring each application to construct its own representation of a company.

Programmatic access

The API is intended to make supported ASUME capabilities available beyond the ASUME application through structured programmatic access.

Depending on the capabilities available when the API is released, this can include access to:

Capability	Purpose
Company understanding	Work with supported parts of the maintained understanding available to the workspace.
Objectives	Use supported objective-specific capabilities and outputs programmatically.
Ask ASUME	Ask questions against maintained company understanding from another application or workflow.
Outputs	Bring supported ASUME results into internal systems and products.

The API is not intended to expose ASUME's internal reasoning architecture, proprietary model mechanics, or unrestricted access to underlying information.

One understanding across systems

Applications using the API should not need to create and maintain their own separate version of a company.

A company can be explored in the ASUME application and later used by an authorised internal system through the API while both work from the same maintained company understanding.

At a simplified level:

Company information → Maintained understanding → API → Application or workflow

This allows organisations to build around ASUME's understanding without rebuilding the company state for each system.

API and MCP

API and MCP are both programmatic interfaces to ASUME, but they are intended for different kinds of integration.

Interface	Intended use
API	Applications and workflows call supported ASUME capabilities through defined programmatic requests.
MCP	Compatible AI systems and agents use supported ASUME capabilities through the Model Context Protocol.

Both operate on the same underlying principle: ASUME maintains the company understanding; other authorised systems can use it through controlled interfaces.

Choosing API or MCP does not create a different company understanding.

Access and permissions

API access will remain subject to the permissions and information available to the relevant ASUME workspace.

Programmatic access should not expand what a user or system is authorised to see simply because ASUME is being accessed through an API rather than the application.

Authentication, access controls, available endpoints, rate limits, and other implementation details will be documented as the API is introduced.

Because the API is planned, its final capabilities and technical interface may change before release.