SDK Generation

axs sdk generate reads your static config and emits a typed client SDK — REST via OpenAPI 3.1 + openapi-typescript/openapi-fetch, and GraphQL via one operation per root field through @graphql-codegen’s client preset. The SDK is generated into your project with a drift banner and a source-surface hash, so a stale client is visible.

Generate

axs sdk generate                    # both surfaces to ./sdk
axs sdk generate --target rest      # REST only
axs sdk generate --out packages/client
axs sdk generate --no-client        # spec artifacts only, skip the typed client

--target accepts rest | graphql | all (default all). See the axs sdk generate reference for every flag.

How it derives the surface

The generator discovers your route/resolver config the same way axs visualize does — a static read, no synth and no AWS calls. Each REST route becomes an OpenAPI path; each GraphQL root field becomes a client operation. Because it reads the same config the stacks read, the client can’t describe a surface your infrastructure doesn’t expose.

Ejecting the config

--eject materialises the built-in codegen/OpenAPI config into your project and stops, so you can customise it and re-run against your own config with --config.

Where to go next

• axs sdk generate for the full flag surface.
• REST v1 API and GraphQL API for the surfaces it reads.