Agentic APIs

Overview

Agentic APIs is the older Hushh API family for A2A orchestration, MuleSoft-backed browser-proxy testing, profile enrichment, and enterprise activation workflows. This is a different developer story from Agent Kai. Kai focuses on PKM, consent approval inside the Kai product, and the versioned /api/v1 contract.

info

Use /developers/agent-kai only when you need the Kai runtime. Use this page when you need the historical A2A, browser-proxy, and profile-enrichment stack.

Runtime model

The public browser-facing surface is the Hushh proxy route family at /api/a2a/<agent>. That proxy hides the upstream MuleSoft routing and keeps browser-safe testing on the website while direct CloudHub endpoints stay a backend concern.

{
  "jsonrpc": "2.0",
  "id": "task-124",
  "method": "tasks/send",
  "params": {
    "sessionId": "session-456",
    "message": {
      "role": "user",
      "parts": [
        {
          "type": "text",
          "text": "Provide a detailed JSON profile for Sundar Pichai, email sundar.pichai@example.com, phone +1 6505559001."
        }
      ]
    }
  }
}

Core browser-proxy endpoints

These are the browser-safe routes teams can test from the website before moving the same prompts or payloads into backend-owned upstream calls.

Endpoint	Agent	Purpose
`POST /api/a2a/public`	OpenAI Public Data Agent	Public-signal enrichment and first-pass profile expansion.
`POST /api/a2a/gemini`	Gemini Public Data Agent	Higher-confidence gap filling and enrichment.
`POST /api/a2a/hushh-profile`	Supabase Profile Creation Agent	Create a structured profile from natural language.
`POST /api/a2a/hushh-profile-update`	Supabase Profile Update Agent	Update an existing profile with new fields or instructions.
`POST /api/a2a/hushh`	Supabase Profile Query Agent	Read a structured profile by identifiers such as phone or email.
`POST /api/a2a/brand`	Brand User Data Query Agent	Translate profile signals into CRM-ready likes, dislikes, and affinities.
`POST /api/a2a/whatsapp`	WhatsApp delivery bridge	Route approved outbound messaging through the historical agent delivery path.

Try it out

Run a live agent request

Pick a workflow, edit the payload, and hit the restored browser proxy.

POST/api/a2a/public

Request body

Response

Run a request to see the response.

Requests run against the live test endpoint.

Enterprise activation flow

1) Collect consented identifiers

Capture the minimum identity inputs needed to create or query a profile.

2) Create or query the profile

Use the Supabase profile agents to establish the working record.

3) Run enrichment agents

Use Public and Gemini agents to fill gaps and improve confidence.

4) Normalize brand signals

Use the Brand agent to produce CRM-ready likes, dislikes, and affinities.

5) Activate downstream

Move the merged profile into CRM, CDP, personalization, or communications tooling.

Browser-safe vs backend-only boundaries

Browser-safe: /api/a2a/<agent> proxy calls, developer docs demos, and the site-hosted testing workspace at /agents.
Backend-only: direct MuleSoft or CloudHub endpoints, secret-bearing WhatsApp delivery credentials, and any production orchestration outside the website proxy.
Separate from Kai: do not document these endpoints as part of the Kai/api/v1 consent and PKM runtime.

NextAgent Reference