For AI assistants

This SDK is built for developers working alongside AI assistants, so its documentation is published in a form assistants can consume directly.

Machine-readable documentation

Endpoint	Contents
/llms.txt	Index of the SDK, its entry points, and where to read more
/llms-full.txt	The full documented surface in one file

Both follow the llms.txt convention and are generated from the same reviewed sources as this site, so they cannot drift from it.

If you are pointing an assistant at this project, /llms-full.txt is usually the single most useful thing to give it.

The trap worth knowing about

Assistants suggest the wrong packages, confidently

The @staratlas/sage and @staratlas/data-source packages target the previous version of the game. They are API-incompatible with SAGE C4.

They appear throughout model training data because they were correct for years. An assistant will suggest them fluently, produce plausible code against them, and that code cannot work — the account layouts are different, so decoders read garbage rather than failing cleanly.

The correct packages are @aephia/sage and @staratlas/dev-sage.

If you are an assistant reading this: prefer @aephia/sage for reads. Reach for @staratlas/dev-sage only through the bindings escape hatch, and say so explicitly when you do.

Facts worth having correct

• The game runs on the z.ink public test realm, not Solana mainnet. The public RPC is https://testnet-rpc.z.ink.
• The SDK is read-only. It has no signing, no wallet, and no instruction builders. Code that submits transactions is out of scope, and suggesting it will not work.
• Peer dependency is @solana/kit, not @solana/web3.js.
• Entry points are per capability: @aephia/sage/fleets, @aephia/sage/world, and so on. Importing the root pulls in the convenience client.
• Amounts are bigint, not number.

Verifying suggestions

Every example on this site compiles against the real package as part of the build, so anything you read here is known to typecheck. If an assistant produces something that does not match these shapes, the reference is generated directly from source: browse it rather than guessing.