Getting Started

Overview

Hushh Agentic Developer APIs let you build consent-first personalization with A2A (Agent-to-Agent) JSON-RPC 2.0 workflows. Use the testable /api/a2a/{agent} endpoints in the docs to prototype, then move server-to-server for production workloads.

The story: from first signal to activated profile

Imagine a luxury retail app onboarding Ava. She shares her email, selects a few style preferences, and explicitly consents to profile enrichment. Your app then:

Consented Identity

Create a clean profile record in Supabase with user consent.

POST /v1/user/create

Agentic Enrichment

Enrich profile with public and Gemini agents for deeper context.

POST /v1/agents/enrich

Normalization

Normalize the profile into CRM-friendly likes, dislikes, and affinities.

{ likes: ['Gucci', 'Prada'], dislikes: [] }

Activation

Activate that profile in your CDP or personalization engine.

SYNC -> Salesforce CDP

The result is a profile that is consented, current, and actionable.

Make your first request

Try it out right here. Use Ava as a reference profile to test the public agent.

POST/api/a2a/public

Enrich a profile using public data agents.

curl -X POST "https://hushh.ai/api/a2a/public" \
  -H "Content-Type: application/json" \
  -d "{\"text\":\"Provide a detailed JSON profile for Sundar Pichai, email sundar.pichai@example.com, phone +1 6505559001.\",\"sessionId\":\"session-123\",\"id\":\"task-abc123\"}"

Example identity payload

json

{
  "text": "Create a profile for Ava Torres with email ava.torres@example.com, phone +1 4155550199, city San Francisco, and interests luxury retail, travel, wellness.",
  "sessionId": "session-456",
  "id": "task-789"
}

Common pitfalls to avoid

warning

Do not use live endpoints from the browser implementation in production. Always move to server-to-server communication to protect your API keys.

Skipping consent metadata before enrichment.
Storing raw agent outputs without normalization.

Next steps

NextDeveloper Console Setup