Building against Temper

For someone writing code that talks to Temper — a service, a script, or an agent runtime that
is not the CLI.

The API

Every endpoint and schema is generated from the router, so the reference cannot drift from
what ships. It is published alongside these pages.

Before you call anything, read Temper auth & security — it sets out
the trust boundary the whole API sits behind.

A machine principal is not a user with a long-lived token; it is its own kind of principal,
registered ahead of time.

Machine credentials — issuing and using them.

The issuer / resource-server boundary — the
machine-token contract, and what a token does and does not carry.

Cognitive-map & resource authoring authorization —
the rules that decide whether a write is permitted.

Ruby, via temper-rb — the generated gem and how it tracks the
API.