Sess

Sess SDK

Ask a person a question from your server and continue with their verified answer.

Create and run a small agent:

npm create @sess.si/agent@latest my-agent

What you'll see: a Sess link. Answer two questions on your phone and your plan prints in the terminal with a verified receipt.

Install the SDK in your own server project:

npm install --save-exact @sess.si/sdk@0.1.1

Ask a person

Use a developer API key from the Sess developer portal. Keep it on the server. The hosted no-signup demo is a separate trial flow; a Sess link or trial credential is not an owner API key. You need no LLM, agent framework, Docker or Sess source checkout.

import { Sess } from '@sess.si/sdk';

const sess = new Sess({ apiKey: process.env.SESS_API_KEY }); const question = await sess.ask({ question: 'Approve the synthetic refund?', fields: [ { name: 'approved', label: 'Approve it', type: 'boolean' }, { name: 'amount', label: 'Refund amount', type: 'number', minimum: 0 }, ], }); console.log(Send this Sess link to the person: ${question.link}); const { approved, amount } = await question.answer(); // verified; the Session is now complete if (approved) console.log(Refund of ${amount.toFixed(2)} approved.);

sess.ask() checks the question locally, creates the Session once and returns its Sess link before anything waits. The link is a bearer capability: deliver it only to the person, never to logs or analytics. answer() waits for the person (ten minutes by default), verifies the signed receipt against the exact question, checks that the answer is still the current step, completes the Session and returns the values typed from your fields. Completion closes the Session: the link no longer accepts answers. Field types are text, number, integer, boolean, choice and multi_choice (API reference).

If the wait times out (wait_ended, code WAIT_TIMEOUT) or you abort it, nothing changes remotely: call answer() again on the same handle. An error with outcome: "unknown" means completion is not confirmed; calling answer() again replays the same completion. The handle lives in memory only. To resume after a restart, persist sessionId and revision and continue with the API below (Integration).

If Sess refuses a call, the error says what happened and what to do. A key Sess does not accept prints: "Sess did not accept your API key. Check SESS_API_KEY and the portal you made it on." The message comes first; the code and request ID follow it:

try {

const question = await sess.ask({ question: 'Approve the synthetic refund?', fields: [{ name: 'approved', label: 'Approve it', type: 'boolean' }], }); console.log(Send this Sess link to the person: ${question.link}); } catch (error) { console.error(error.message); // what happened and what to do const request = error.requestId ? , request ${error.requestId} : ''; console.error(Details: ${error.code ?? error.kind}${request}); process.exitCode = 1; }

Keep it short

A person reads the page on a phone, so Sess keeps every piece of it short. Lengths count characters (Unicode code points), and Sess never truncates:

There are at most 5 buttons. A value over its limit fails with a SessError that names it: field is a JSON pointer such as /question, limit is the most it may have and length is what it has. The message says how to fix it: "The title can be at most 80 characters. Keep it to a short heading, about 40." for the title, and for anything else, for example "/fields/0/label is 72 characters; the limit is 60. Shorten it to at most 60 characters." Nothing was created (outcome is not_sent or rejected), so shorten the value and ask again:

import { Sess, SessError } from '@sess.si/sdk';

declare function shorten(text: string, max: number): Promise ; // e.g. your model rewrites it

const sess = new Sess({ apiKey: process.env.SESS_API_KEY }); const fields = [{ name: 'approved', label: 'Approve it', type: 'boolean' }] as const; async function askShort(question: string) { try { return await sess.ask({ question, fields }); } catch (error) { if (!(error instanceof SessError) || error.field !== '/question' || error.limit === undefined) throw error; return sess.ask({ question: await shorten(question, error.limit), fields }); } }

Release status: 0.1.1 is the current release, served under the latest dist-tag. Its API is that of 0.1.0, the first stable release. next stays at the last release candidate, 0.1.0-rc.10. The changelog describes each version; npm view @sess.si/sdk dist-tags shows what the registry serves now.

Commerce

Sess takes no payment: the person approves a bill on a Sess page, and moving the money stays with you and your payment processor.

import { Sess, invoice } from '@sess.si/sdk';

const sess = new Sess({ apiKey: process.env.SESS_API_KEY }); const created = await sess.sessions.create({ interaction: invoice({ currency: 'CAD', // whole cents: 420000 is $4,200.00 reference: 'INV-2041', rows: [{ name: 'Design retainer, October', amount: 420000 }], lines: [{ label: 'GST 5%', amount: 21000, role: 'tax' }], }), }); console.log(Send this Sess link to the person: ${created.data.human_url});

Three things you will meet first:

• Short rows. A row name has at most 80 characters and its detail at most 160. A longer value is refused, never trimmed: the SessError names it by its pointer, such as /interaction/source/components/1/rows/0/name, with limit and length.
• Whole minor units. Amounts are integers in the currency's smallest unit: cents for USD, yen for JPY, fils for BHD. money(1250, 'USD') is $12.50; money(12.5, 'USD') throws, because Sess never rounds or converts.
• Exact totals. The builders compute the subtotal, total and amount due from your rows and lines. An items component you write by hand whose subtotal is not the sum of its rows is refused with HTTP 400:

{

"error": { "code": "INVALID_SCHEMA", "field": "/interaction/source/components/0/totals/0/amount", "expected": 441250, "actual": 451248 } }

invoice(), receipt(), quote(), refund() and purchaseOrder() each return an ordinary interactive Surface for sess.sessions.create({ interaction }): the bill as an items card, the document's reference under a plain name, and the buttons the person needs (Approve and Decline; Continue on a receipt; Accept on a quote). refund() states positive amounts under "Refund total". A row quantity lets the person change it and adds a Request changes button; your agent replies with a new revision and updated amounts. items() builds just the card, and lintText() finds a Markdown table in text, which the person would see as pipes. See the API reference.

What Sess does not do: take or move payment, convert currencies, compute tax or prices, show your logo or branding, or let another site frame the page (frame-ancestors 'none').

Advanced: the full Surface API

import { Sess } from '@sess.si/sdk';

const sess = new Sess({ apiKey: process.env.SESS_API_KEY }); const created = await sess.sessions.create({ interaction: { mode: 'interactive', title: 'Review a synthetic invoice', source: { kind: 'sess_surface', components: [ { type: 'record', label: 'INV-001', fields: { amount: 120 } }, { type: 'field', name: 'amount', label: 'Correct amount', required: true, schema: { type: 'number', minimum: 0 }, value: 120, }, ], }, actions: [{ id: 'submit', label: 'Submit review', intent: 'submit' }], }, });

// Privately deliver created.data.human_url through your application's handoff. // It is a bearer capability: do not put it in ordinary logs or analytics. const answer = await sess.sessions.waitForResponse(created.data.id, { revision: created.data.revision, }); const verified = await sess.receipts.verifyResponse({ sessionId: created.data.id, response: answer.response, }); const amount = verified.response.data.amount; if (typeof amount !== 'number' || !Number.isFinite(amount)) { throw new Error('Expected an accepted numeric amount'); }

Verification checks that the receipt was issued for your workspace. Sess names your workspace on authenticated responses (the Sess-Workspace-Id header), so you set nothing. If a runtime does not send it, set expectedWorkspaceId from trusted deployment settings; otherwise verification fails with VERIFICATION_CONTEXT_MISSING. The SDK never takes the workspace from the unverified receipt.

The quickstart function includes a private delivery callback. Three-round continuation persists mutation intent and checks that an answer is still the current expected business step before publishing or completing. Its store and worker lease are application-owned. See Integration.

Check a decision bundle

A decision bundle is one accepted decision that its owner chose to share: the signed receipt, the exact Surface and input, and the issuer's public keys. Check it on your own computer, with keys you trust (never the keys inside the bundle):

npx -p @sess.si/sdk@0.1.1 sess verify bundle.json --issuer https://api.sess.si --keys sess-receipt-keys.json

The sess command first ships in 0.1.0-rc.5; any later version, 0.1.1 included, has it.

You'll see Valid decision bundle. and what was accepted, when, on which revision; or Invalid and the first reason. Exit status is 0 valid, 1 invalid, 2 usage error; add --json for the full result. Nothing is sent anywhere. In code, use verifyDecisionBundle from @sess.si/sdk/receipts (Security). Formats: receipt-v1 and bundle-v1.

Show the link as a QR code

When the person is at a laptop and would answer on their phone, draw the link as a QR code, locally, with no network call:

import { printQr, qr } from '@sess.si/sdk/qr';

const link = 'https://sess.si/s/synthetic-link'; // the link sess.ask() returned console.log(link); printQr(link); // prints "Scan to answer on your phone" and the code, on an interactive terminal only const svg = qr(link, { format: 'svg' }); // also 'png' (bytes) and 'terminal' (text)

Use it where a person sees a screen but not their phone: a desktop chat window, a dashboard, a kiosk, print. Skip it in SMS, or when the person is already on their phone. Sess never shows or sends the code; your agent chooses. printQr prints nothing without a TTY, in CI (CI set), in production (NODE_ENV=production)