Two calls in your request path.

Concepts

Account, app, user.

Three levels, and every path you call contains all three. An account holds your key. An app scopes what is learned, so a support bot and a writing assistant never share a memory. A user is the person whose preferences accumulate.

The pattern

Read before, write after.

Ask for context before you call your model, and post the interaction once you have it. You send raw material — the message, the edit, the correction — and never a preference you inferred yourself. Working out which part was durable is our job, and the part we are measured on.

Quickstart

From nothing to a personalised reply.

{{ s.code }}

Reference

The whole surface.

Four endpoints. Two of them you call once when you set up; two of them sit in your request path. Every request carries Authorization: Bearer and returns JSON.

Objectives

Writing one worth learning against.

The objective on your app is the most consequential line of configuration you write: it decides which patterns are worth keeping. The shape that works is [outcome verb] + [what] + by [how] — measurable, user-centric, and about an outcome rather than a process.