AIality developer documentation

The AIality Gateway resolves exact, versioned Reality states over REST and MCP. Every route below is real and implemented — nothing on this page describes a planned feature as if it already existed.

Core concepts

  • Reality — the current answer to a specific question about the outside world (a "FactTopic" resolved against a scope).
  • Exact state — one immutable, versioned FactStateVersion, never mutated once written.
  • Authority — the explicit, versioned binding of a state to the source surface that produced it.
  • Freshness — a frozen-at-creation horizon that determines whether a state currently reads FRESH or STALE.
  • Change — a deterministic classification of what changed between two exact states.
  • Impact — attribution of a change to its registered dependents.
  • Reality Lock — an immutable decision basis over one or more exact states, assessable later for drift.

Where to start

New to the API? Start with the five-minute quickstart. Building an agent? Start with MCP.

Official SDKs

PythonOfficial Python SDK 0.1.0, available to pilot customers. PyPI publication pending. TypeScript — planned, not yet available; the OpenAPI spec and MCP tool schemas are the generated-client path today.

Not yet available

The following are explicitly deferred (ADR-027 §4.10) — do not expect them today:

  • Webhooks / push subscriptions on the Gateway (planned / not yet available)
  • TypeScript SDK (planned / not yet available — see Official SDKs above)
  • OAuth (Gateway auth is a Bearer API key today, see Authentication)
  • Self-service API key issuance (keys are created by an AIality operator today)
  • Batch resolution (resolve_reality_batch) — planned / not yet available