Quickstart
Point your existing agent at Humaner Intelligence in four steps.
What Custom is
Custom keeps your agent. Claude Code, Cursor, Codex, an internal LLM stack, a Slack bot — whatever already answers your customers. Humaner becomes the backend: knowledge retrieval, guardrails, runbooks, memory, and the Helpdesk your agent escalates into.
There is no hosted persona on Custom
Persona, tone, and voice belong to your agent. The dashboard does not configure your agent voice. Configuration only carries identity, endpoints, and guardrails.
Four steps
- 1
Subscribe to Custom and finish onboarding
Onboarding ends on the API key step instead of the personality step.
- 2
Create an API key
Settings → Developers, or Integrations → REST API. Scope it to intelligence, helpdesk, or both.
- 3
Copy your agent public ID
Agent → Configuration shows it. Every Intelligence call needs it as agentId.
- 4
Call Intelligence from your backend
Server-side only. Browser Origin auth is rejected on these endpoints.
Your first call
curl -X POST https://app.humaner.io/api/v1/intelligence/retrieve \
-H "Authorization: Bearer hm_live_xxxxxxxx" \
-H "Content-Type: application/json" \
-d '{
"agentId": "YOUR_AGENT_PUBLIC_ID",
"query": "What is your refund policy?"
}'Logged Activity
Every call is recorded through a 7 day window. /Analytics show status, tool, latency, and errors for the past week so you can check workability.
Next
Hand this to your coding agent
The Custom brief is one Markdown page covering keys, the replies, guardrails, and tickets configuration.