A typed request. Visible rules. A result you can inspect before you connect anything.
Run a local exampleconst result = kernel.classify(input);{
"category": "billing",
"priority": "high",
"owner": "payments",
"reference": "1042",
"nextAction": "Review duplicate charges before replying."
}Edit the input to change the result. This example runs entirely in your browser.
The request contract has an answer for missing data, wrong types, and valid input.
{
"subject": "Need a receipt"
}A generic failure leaves people guessing. The contract names the exact field and the smallest change that makes this request valid.
{
"field": "message",
"error": "Required",
"recovery": "Add a non-empty message field."
}{
"subject": "Need a receipt",
"message": 42
}The field exists, but its type is wrong. Preserve the input and return a useful correction without replacing the last valid result.
{
"field": "message",
"error": "Expected string",
"recovery": "Replace the number with the complete support message."
}{
"subject": "Need a receipt",
"message": "Please share the receipt for order 1042."
}A valid request returns the agreed shape. The owner and reference stay visible so the next step can be inspected.
{
"category": "general",
"priority": "normal",
"owner": "support",
"reference": "1042"
}One support note, four inspectable steps.
The request must include a subject and a message. Missing data is returned as an explicit field error before any rule is evaluated.
Two required fields present{
"subject": "Checkout charged me twice",
"message": "Urgent: two charges…",
"valid": true
}The billing rule matches “charged” and “charges”. The urgent rule raises the priority. These are deterministic sample rules, visible in the result.
Billing and urgent rules matched{
"matchedRules": ["billing", "urgent"],
"category": "billing",
"priority": "high"
}Billing requests route to payments. The order reference is retained, so the receiving team has the context needed to act.
Routed to payments with order 1042{
"owner": "payments",
"reference": "1042",
"reason": "category is billing"
}The final object includes category, priority, owner, reference, and a next action. No hidden account change or external request takes place.
Typed sample result ready{
"category": "billing",
"priority": "high",
"owner": "payments",
"nextAction": "Review duplicate charges"
}Choose a realistic input, inspect the useful result, then run it yourself.
Turn a duplicate-charge note into an owned billing task.
{
"subject": "Checkout charged me twice",
"message": "Urgent: two charges appeared for order 1042.",
"customer": "Mina"
}{
"category": "billing",
"priority": "high",
"owner": "payments",
"reference": "1042",
"nextAction": "Review duplicate charges before replying."
}Extract a reference, amount, currency, and review date from one sentence.
{
"text": "Invoice INV-312 for 280 EUR is due on 2026-11-04."
}{
"reference": "INV-312",
"amount": 280,
"currency": "EUR",
"dueDate": "2026-11-04"
}Keep an everyday request in the normal support queue.
{
"subject": "Workspace members",
"message": "How do I invite a teammate?"
}{
"category": "general",
"priority": "normal",
"owner": "support",
"reference": null,
"nextAction": "Review the note and reply with the next step."
}Small methods. Explicit inputs. Predictable return shapes.
kernel.classify(input)
| Field | Type | Description |
|---|---|---|
| subject | string | Required. A concise support subject. |
| message | string | Required. The complete support message. |
| customer | string | Optional. A display name for context. |
Returns Classification
const result = kernel.classify({
subject: "Checkout charged me twice",
message: "Urgent: two charges for order 1042."
});
// result.owner === "payments"kernel.extract(input)
| Field | Type | Description |
|---|---|---|
| text | string | Required. Invoice reference, amount, and due date. |
Returns InvoiceFields
const invoice = kernel.extract({
text: "Invoice INV-204 for 840 USD is due on 2026-10-18."
});
// invoice.reference === "INV-204"kernel.validate(input, schema)
| Field | Type | Description |
|---|---|---|
| input | object | Required. Data to inspect. |
| schema | "triage" | "invoice" | Required. The expected field contract. |
Returns ValidationResult
const validation = kernel.validate({
subject: "Need a receipt"
}, "triage");
// validation.errors.message === "Required"Select a method to inspect its contract.
The support example evaluates billing and urgency rules, retains an order reference, and chooses an owner. The invoice example extracts a reference, amount, currency, and date. The response and execution trace update from those actual values.
No. The examples use deterministic local rules so you can inspect every state without an API key. The SDK is a design concept; replace its example rules with your own runtime when integrating the template.
Invalid JSON and missing or incorrectly typed required fields name the issue beside the input. The most recent valid result is preserved. On a narrow screen, a validation error switches the bench to its Input view.
Yes. Select any trace step, pause the replay, or turn motion off. A reduced-motion preference shows the complete result directly. The displayed durations are illustrative, not measured service latency.
Start with one request.
Inspect the playground