Build Star Atlas apps in TypeScript without becoming an on-chain program expert. Validated SAGE C4 reads, live derivation, and writes you can inspect before you sign.
These docs run on the same realm your app will. The example below executes
real SDK calls against the live z.ink test realm, in your browser — press Run,
or change the address first.
Every guide carries a runnable example like this one — try them all —
or install the package and run the same code verbatim:
You want a fleet’s name; the chain gives you bytes. With the Kit, names are
strings, quantities are exact bigints, state is a union you can switch
on, and relationships read like a data model — not RPC plumbing.
Account encodings, definition lookups, slot math — that knowledge stays in
the Kit. When the next SAGE version ships, the Kit absorbs the churn and
your app keeps talking about fleets.
A travelling fleet does not write its position every second — where it is
now is math, and the Kit ships that math as pure functions. Fetch once,
let the clock move it.
llms.txt endpoints, an installable agent skill, examples that compile in
CI, and errors that teach. Built to be easy for humans and coding agents —
and to steer assistants away from the incompatible legacy packages.
Actions build into Plans: inert, inspectable data with known signers,
assembled into one unsigned transaction under an explicit fee policy. The
Kit is non-custodial — nothing signs, submits, or retries implicitly.
New to the SDK? What is this? explains the game,
the realm, and the boundary the Kit will not cross —
your first read has live data on your screen in
about five minutes. Already oriented? The game map shows how
every concept connects, and the API map how every entry point does.