Quickstarts
Use these examples to configure a client for local runtime development or invite-only Hosted Alpha access. v0.1.x SDK package names are staged for private alpha distribution until v1; use install snippets only when your invite or package credentials include access.
Environment
For a local runtime:
For Hosted Alpha, use the hosted API URL and a scoped API key issued by the control plane:
Do not put hosted API keys in source control, docs, ledgers, issue comments, or chat output.
These environment variables are a shell convention used by curl examples and any
SDK helper that your private-alpha package documents. Follow the generated SDK’s
documented helpers when available, and fall back to explicit constructor or
config fields from the OpenAPI operation shape. Do not assume fromEnv /
from_env helpers exist unless the owning SDK README for your installed package
shows them for that version.
SDK Package Access
If you have private alpha package access, pin the staged v0.1.1 SDKs:
Go SDK support is reserved/candidate and is not a v0.1.1 private alpha install surface yet.
HTTP Smoke
The API reference is the source of truth for exact route shapes. A minimal HTTP readiness check looks like:
For hosted calls, use the SDK or gateway-supported routing metadata so the
request is bound to the authorized tenant, database, and branch. Do not send
x-tracedb-* actor headers as a way to impersonate routing state; the hosted
gateway strips client-supplied actor headers and injects trusted metadata from
verified claims.
Next Steps
- Use API authentication for token and routing rules.
- Use TraceQL and Native and Bounded GraphQL for query examples.
- Use Idempotency and Retries before retrying writes or polymorphic operations.