docs · what heygenie is

A helpdesk any product installs in one line. A genie that speaks only from the product's own knowledge.

The graph

Every product gets a knowledge graph: its surfaces, the symptoms people report, the fixes that were graded, the rules that bound them. Every node is reachable from the product; every fix cites its source. The genie retrieves from it on every turn and cites the node ids it used.

The genie

A language model phrases the answer from that knowledge and nothing else. When the graph holds nothing it says so, asks one clarifying question, and refers the product's team to the studio. It never asks for a key, a password or an address.

The judge

Before anyone pays, the answer is graded: code checks the facts (the cited nodes exist, nothing secret, something was said), then Jev's four questions are asked of the answer against the knowledge: spec met, unsupported claim, ending, cheat shaped. Composed under fixed thresholds into one score; the asker's word caps it. Under the grade gate nobody pays and nobody earns.

The power

Every turn is measured: the neurons the answer and its grade cost. Measured first, priced per case, never per token hidden in a bill.

The record

One sealed envelope per step of a case, on the tenant's own topic. The layer counts cases, grades and money; it never reads.

The studio

Where a product's team builds its graph (from the directory, from its own words, or empty), teaches the genie what it could not answer, trains and enforces its own agent on the graph, tunes the loops and reads the ledger. Open the studio.

how a case runs

Five steps, one record, one line of money.

1. AskA person or an agent asks in the product, the panel, the chat or by API. The question is graded for strength as it is written.
2. GraphThe product's own graph answers first. That answer is free.
3. RouteAn unknown goes to a nominated expert, the tenant's agent or a person. The open question lands on the product's weakest-link list.
4. GradeJev, the independent judge, or the asker grades the answer. Nobody pays until the grade stands.
5. SettleOne meter line: 70 percent to the answerer, 20 to the graders, 10 to the ecosystem. The graph learns. The record seals to your tenant.

price

Pay per solved case. Nothing for what the graph already knows.

the doors

Two doors on this site, four on the layer. One key.

POST /api/chat

The genie talks. Body {product, messages:[{role,content}], knowledge, known}; the page sends the knowledge of the turn (the graph as the core retrieved it, the graded fix if there is one). Answer: a server-sent stream of the words; each line carries the power used so far. CORS open: the same door serves the page, the browser panel and any chat.

POST /api/grade

The judge. Body {product, question, answer, knowledge, known}. Answer: {score, verdict: complete|needs_review|reject, forced, answers:{spec_met, unsupported_claim, ending, cheat_shaped}, facts:{cited, missing, grounded, secret}, neurons}. Thresholds: complete at 0.7, review at 0.4, cheat at 0.5.

/v1/sma/ask · graph · learn · nominate

The layer's doors (coord): ask opens a case under your key and meters it; graph reads a product's public graph; learn grants a wish and the graph learns it; nominate names an expert payee. Under x-api-key; 20 free answered cases a day per key, then 402 names the next step.

The embed

<script src="https://heygenie.online/embed.js" data-helpdesk="your-product"></script> mounts the genie on any page. The Chrome panel, the MCP tools, the n8n node, the Teams and Slack apps are the same core behind the same doors.

rollout · the mediums

Specified once, rolled out one medium at a time.

A page

The embed line. Live.

A browser

The Chrome side panel, the same bundle, no remote code. Built; store listing pending.

MCP and HTTP

The sma tools on the layer's MCP and the /v1/sma doors. Built; the layer's deploy pending.

n8n

The heygenie node in the Taifoon n8n package. Built.

Teams and Slack

The chat plugin: /heygenie callout or observe mode, one call per message, grades from the room. Core built; apps coming.

Any chat

createChatPlugin({graph, askedBy, mode}) from the package: onMessage, onFailure, grade, weakest, trainingSet, enforcer. The minimum set for any product's own chat.

what you can rely on

Sealed trail

Every step of a case is a sealed record on your own topic. The pipe holds no key and never decrypts.

Counts only

The layer sees cases, grades and money per tenant. Small counts are shown as "under five". Never a payload.

Open resource

A product's public graph is published under CC BY 4.0 and answered by open-weights models. Your sealed nodes never leave.

One ledger

Every case is one meter line on the Taifoon coordination layer, with its legs. Experts are paid from the same line that charged the case.

One core

What ran in your browser above is the helpdesk's core, byte-identical with the runtime and the layer's door. The language (coord, CUE) refuses every broken copy.