Hue is headless.
Your agents drive it. We keep the data, the rules and the receipts.

Everything Hue does in the Humonix app is also a tool your own AI assistant or code can call: over MCP from Claude, ChatGPT, Cursor or Claude Code, or over a REST API. Each connection belongs to one company and one person, sees only what that person’s role allows, and can read or propose, never send, pay, publish or delete.

What is live today

A per-company MCP server

One address for every client; when you connect, you sign in to your Humonix workspace and the connection is tied to your company and to you. OAuth 2.1 with PKCE (S256) and dynamic client registration, as the MCP authorization spec asks. Access tokens last an hour; refresh tokens rotate, and a reused one revokes the whole connection.

Scopes you choose when you connect

data:read (read your records and departments), hue:chat (ask Hue), desks:propose (prepare drafts that wait for your approval, owners only). The tools list an assistant sees is filtered by those scopes and by your role.

A REST API with OpenAPI 3.1

POST /api/v1/tools/<name> with a company API key an owner makes in the app (Developers). A key acts with the role of the person who made it, re-checked on every call; it stops working if that person leaves. Proposals accept an Idempotency-Key.

A public tool catalog

GET /api/v1/tools lists every tool with its kind (read or propose), scope, permission, input schema and hints an agent can use to choose: cost, typical latency, what the answer rests on, side effects. It describes the door, never anyone’s data.

Events and webhooks

Six topics: invoice.overdue, job.late, stock.low, quote.expiring, desk_request.needs_human, approval.waiting. Delivered as signed webhooks (HMAC-SHA256 over the timestamp and body), retried from one minute to 24 hours; or pull the same list with the recent_events tool. Each topic needs the module’s view permission.

Roles, approvals, audit

The same role rules as the app, on every call. A proposal only adds a draft to a queue a person already approves in the app. Every MCP and API call is written to your company’s access log (person, assistant or key, tool, time, IP address) before it runs, and counted per tool; the arguments and answers are not stored in the count.

Hosted in North America

The Humonix app and its database run on Fly.io in Toronto, Canada. What an assistant reads leaves through that assistant, under your account with its provider.

The tools

More than 80 tools today. The main groups: your company’s records (invoices and who to call first, jobs and dispatch, stock below its reorder point, purchase orders, quotes, margins, tasks, e-signatures, the P&L, one customer’s full picture), the workspace (your departments, what waits for approval, datasets, saved pages, ask Hue), the desk queue (file a customer request for Hue’s desk, what waits for you, what is late, one request in detail), and events. Two kinds only: read (changes nothing) and propose (a draft a person approves). The live catalog is the source of truth:

Agent to agent (A2A): hire Hue for results

Your agents do not need a screen to give Hue work. Hue speaks A2A, the Agent2Agent protocol now stewarded by the Linux Foundation (version 1.0, and 0.3 for older clients): another agent reads Hue’s Agent Card, sends it a task, and gets a result back, not a page to click through.

The Agent Card

Public at /.well-known/agent-card.json: Hue’s skills, the JSON-RPC endpoint, and how to authenticate. It describes the door, never a company or its data. A signed-in agent can ask for the extended card, which lists only the skills its key and role allow.

Ten skills

Answer a question about the business; answer a customer’s question; qualify an inbound lead; chase overdue invoices; draft a quote; propose a day’s dispatch; a research job; propose an ads change; online order status; and run any tool of the catalog by name.

Results, not screens

Reads answer in the call. Work becomes a draft a person approves in the app, and the task stays open, marked input-required with who must act and where, until a result exists: the answer approved, the reminders decided, the quote approved or declined, the report accepted. Then it completes with a result: outcome, summary, evidence with links, value (money chased, quotes approved, meetings booked, jobs scheduled), cost at list price, and what comes next.

The same rules as MCP and REST

A company API key or the same OAuth sign-in as the MCP server; the company always comes from the credential, never from the message; the same scopes and roles; every call in the access log. Nothing is sent, paid or published without a person.

Updates your agent can follow

Poll with GetTask, stream with server-sent events, or register a push-notification webhook per task. Results are also at GET /api/v1/results, through the MCP tool results_recent, and as the signed webhook topic result.completed.

https://humonix-hq.fly.dev/.well-known/agent-card.json

Give Hue a task (a company API key with write:proposals):

curl -X POST https://humonix-hq.fly.dev/api/a2a \
  -H "Authorization: Bearer hxc_…" -H "A2A-Version: 1.0" -H "content-type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"SendMessage","params":{"message":{"messageId":"m1","role":"ROLE_USER","parts":[{"data":{"skill":"chase_overdue_invoices"}}]}}}'

Connect your assistant

You need a Humonix workspace. The assistant asks you to sign in the first time; you choose the scopes. The same steps are in the app under Developers and Connections.

Settings › Connectors › Add custom connector, paste the address, then Connect and sign in.

https://humonix-hq.fly.dev/api/mcp

Settings › Apps & Connectors › Advanced › Developer mode on, then Create, paste the address, authentication OAuth, and sign in.

https://humonix-hq.fly.dev/api/mcp

Add the server, then run /mcp to sign in.

claude mcp add --transport http humonix https://humonix-hq.fly.dev/api/mcp

Settings › MCP › Add, then sign in when asked.

{ "mcpServers": { "humonix": { "url": "https://humonix-hq.fly.dev/api/mcp" } } }

With a company API key from Developers in the app.

curl -X POST https://humonix-hq.fly.dev/api/v1/tools/invoices_overdue \
  -H "Authorization: Bearer hxc_…" -H "content-type: application/json" \
  -d '{"limit": 5}'

Today the address is humonix-hq.fly.dev; it moves to app.humonix.com when our DNS change lands, and we will say so in the changelog.

The rules it runs on

  • The company is always your connection’s or your key’s, never something a tool takes as an argument; a request for another company’s data finds nothing.
  • No tool sends, pays, orders, publishes or deletes. Those stay in the app, with a person.
  • Text from your records that a tool returns is data, not instructions, and the server tells the assistant so.
  • Rate limits per tool and per person or key, on top of 300 calls an hour per assistant connection.
  • Your data is never used to train shared models. Built for Québec’s Law 25 and Canada’s privacy rules.

The Model Context Protocol is an open standard, introduced by Anthropic in November 2024, that lets AI assistants connect to tools and data through one common interface. Because Humonix speaks it, the assistants your team already uses can work with your records instead of you copying them into a chat.

Not yet

  • Listed in the Claude connector directory or as a ChatGPT app: not yet; today you add Humonix as a custom connector with the address above.
  • MCP resources and live subscriptions: later. Today, events come by webhook or the recent_events tool.
  • A role picker per API key: later. Today a key acts with its maker’s role.
  • Listed in A2A agent directories and registries: not yet; today an agent finds Hue from its Agent Card address.

Ask for access