Skip to content

Machines API: list the official client libraries - #2490

Open
alexleventer wants to merge 2 commits into
mainfrom
machines-api-client-libraries
Open

alexleventer wants to merge 2 commits into
mainfrom
machines-api-client-libraries

Conversation

@alexleventer

Copy link
Copy Markdown
Contributor

What

Adds a Client libraries section to the Machines API index page. It named the OpenAPI spec but no package, so a reader or agent landing here couldn't tell that fly-go exists, or that Sprites has SDKs.

The section: fly-go (the Go client flyctl is built on), "generate one from the OpenAPI spec" for every other language, and the four Sprites SDKs (@fly/sprites, sprites-py, sprites-go, sprites on Hex) plus the MCP server, each linked to its registry page.

Companion to superfly/landing#1249 (llms.txt) and superfly/ui-ex#5602 (ARD catalog), which surface the same list to agents. Ora's agent-readiness scan of fly.io currently reports "no SDK packages found" because nothing on the site links to them.

Every registry link was checked to resolve.

🤖 Generated with Claude Code

alexleventer and others added 2 commits September 18, 2026 11:54
The page linked the OpenAPI spec but named no package, so a reader (or
an agent) landing here could not tell that Fly.io publishes fly-go, or
that the Sprites SDKs exist. One short section: the Go client, how to
generate a client for anything else from the spec, and the Sprites SDKs.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The Sprites SDKs are for a different API; say so, rather than listing
them as if they drove Machines.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant