Personal access tokens

August 25, 2026·1 min read

Personal access tokens

A personal access token (PAT) is a bearer credential bound to your account, presented as Authorization: Bearer fpat_… on REST and MCP alike.

The one rule: tokens only narrow

A PAT can never do more than the account that minted it. Authorization runs in two layers on every call:

Grant — the token carries api:read or api:write.
Permissions — per-namespace roles and permissions on your account decide which resources the call may touch.

Scoping

At mint time a token can be narrowed further:

Constraint	Effect
`readOnly`	Write operations are refused regardless of grant
`namespaces`	Allowlist of app namespaces the token may touch
`permissions`	Allowlist ANDed with your real permissions
`expiresAt`	Hard expiry

Omitted constraints default to your full authority, and tokens from the device flow do not expire on their own — prefer narrow, expiring tokens for anything long-lived or agent-held.

furnace auth login --read-only --namespace=docs,marozzo

Lifecycle

Mint via the device flow, furnace auth login, or OAuth. Revoke in your account settings, or revoke the token you are currently calling with via DELETE /api/v1/auth/token; revocation is immediate on every surface. See Account & access.