Skip to main content
This page collects everything scattered across the walkthrough and tips pages into one lookup table. If you already know the name of what you’re looking for, start here before searching the guides.
Every row below is confirmed against this documentation or the OpenAPI spec. Anything only seen in community code (not in official docs) is called out separately in the last section, with a warning — not stated as fact.

ADK client SDK (@terminal3/t3n-sdk)

Naming conventions

WIT host interfaces (contract-side capabilities)

Capabilities are determined entirely by which of these you import in world.wit — there’s no separate manifest. See Capabilities come from your WIT imports.

REST API

The full REST surface is documented via OpenAPI — see the API Reference tab for live, browsable endpoints generated directly from the spec (so it can’t drift out of sync with this page). Verified directly by parsing terminal-3-openapi.yml (21 paths, 24 operations, OpenAPI 3.0.3): Auth: bearerAuth by default, with an x-api-token header required on specific endpoints (e.g. user creation). Server: https://staging.terminal3.io.

Reported in community code — checked against the confirmed release (testnet-v1.0.11, @terminal3/t3n-sdk 5.19.0)

These symbols surfaced in community code but weren’t in the docs. Here’s how each actually stands in the current SDK’s public API. (getAuditEvents()/getActivityLog() used to sit in this section too — moved up to the main table above now that they’re confirmed and written up.)