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)

The stateless client is its own package since @terminal3/t3n-sdk 5.31.0 (testnet-v1.0.12). invoke, the discover* reads, parseContractResponse, the token-unit helpers, NODE_URLS / Environment and the T3nError family now live in @terminal3/t3n-client, which @terminal3/t3n-sdk depends on at runtime and re-exports under the same names — imports from @terminal3/t3n-sdk are unchanged. Install @terminal3/t3n-client on its own only for a stateless caller (webhook, serverless function) that never needs a session.

Removed from the SDK in 5.22.0 (shipped with testnet-v1.0.12) — breaking

The legacy grant / agent-auth request surface is removed, not deprecated. Only the delegation vocabulary remains. Confirmed live on testnet: the matching contract-side removal is in tee:user 5.0.0, tee:authorisations 4.0.0 and tee:org-data 4.0.0, and testnet’s pinned contracts rev (3305a95) is at tee:user 5.0.8, tee:authorisations 4.0.8 and tee:org-data 4.1.4 — all past the gate. (testnet.json’s tee:user 3.8.2 entry is the Veriff webhook’s own target version, not what’s registered.) A raw execute caller using a legacy function name now gets FunctionNotFound against testnet, and checkDelegation() only returns the collapsed grant kinds there. Because this SDK’s semver is patch=fix, minor=break-or-feature, the removal shipped as a minor — treat upgrading past 5.21.x as a breaking upgrade.
checkDelegation() / discoverCheckDelegation() now return the node’s delegation.check verdict as received. The contracts emit only member_delegation / org_delegation grant kinds (and the member_delegation_not_found / _expired / _not_yet_valid deny codes); the SDK no longer maps the pre-collapse tokens (agent_auth, user_grant, agent_auth_*). Against an older cluster those old tokens reach your code unmapped.

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 stood in the SDK’s public API at testnet-v1.0.11; the entries below were not re-checked at testnet-v1.0.12. (getAuditEvents()/getActivityLog() used to sit in this section too — moved up to the main table above now that they’re confirmed and written up.)