Developer hub

Developer APIs

Start with the right Hushh API product. Agent Kai is the current consent-first runtime. Agentic APIs covers the older A2A, MuleSoft, browser-proxy, and enterprise activation surfaces.

Agent Kai is the current consent-first runtime.

Agentic APIs remains available as the older enterprise and browser-proxy lane.

Choose one track first and follow its docs in order.

Use browser testing only where the reference explicitly allows it.

Choose your track

Two API products, kept intentionally separate

The first job of this page is simple: help you enter the correct docs lane. Kai is the current consent-first PKM product. Agentic APIs is the older A2A, MuleSoft, browser-proxy, and enrichment product family.

Current lane

Recommended for new integrations

Agent Kai API

Consent-first PKM discovery, approval inside Kai, versioned REST endpoints, and remote MCP runtime guidance.

Consent-first PKM discovery and approval
Versioned REST contract for scoped reads
Remote MCP runtime and browser-safe docs flow

Kai apphttps://www.hushh.ai

REST basehttps://api.kai.hushh.ai/api/v1

Remote MCPhttps://api.kai.hushh.ai/mcp

Start with

Open Agent Kai API

Legacy + enterprise lane

Use when your backend already depends on it

Agentic APIs

Historical A2A, MuleSoft, browser-proxy, and profile-enrichment APIs for enterprise activation flows.

A2A and browser-proxy testing surfaces
MuleSoft and CloudHub enterprise runtime
Profile enrichment and activation workflows

Browser proxy/api/a2a/{agent}

Testing workspace/agents

Backend upstreamTrusted backend hosts only

Start with

Open Agentic APIs

Start here

A simple path into the docs

Step 01

Pick the product first

Use Agent Kai for new consent-first PKM integrations. Use Agentic APIs only when you are working against the older A2A, MuleSoft, or browser-proxy contract.

Step 02

Confirm runtime and auth

Before copying any endpoint, make sure you know whether you need Kai REST and MCP, or the older backend/browser-proxy surfaces.

Step 03

Start with the reference

Open the track reference first, then move into setup and supporting guides. That keeps the mental model clean and avoids mixing two different API stories.

Read this before integrating

The trust cues developers care about

Good API adoption usually comes down to three things: a clear current path, an honest explanation of legacy surfaces, and stable runtime information you can trust.

What is current

Start new work on Agent Kai

If you are beginning a new integration, Agent Kai is the default lane. It documents the current consent model, PKM data plane, and versioned runtime contract.

What is legacy

Use Agentic APIs only when the backend requires it

The older A2A, MuleSoft, and browser-proxy surfaces still exist for enterprise and migration scenarios, but they are not the same product as Kai.

What builds trust

Clarity beats volume

Developers adopt faster when the docs show stable URLs, clear boundaries, and an obvious first page. This hub is meant to help you decide quickly and move with confidence.