For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Book a demoLog inStart for free
  • Get started
    • Overview
    • Features
    • Authentication
    • OpenAPI extensions
    • Customization
Checking status...
SOC2Soc 2 Type II
© 2026 Fern • Birch Solutions, Inc., a Postman company

Documentation

SDKsDocsAsk FernCLI Reference

API Definitions

OpenAPIAsyncAPIOpenRPCgRPC

Resources

BlogSupportPricing

Company

Brand KitPrivacy PolicyTerms of Service
LogoLogo
Book a demoLog inStart for free
On this page
  • How it works
  • Built for agents and humans
Get started

CLI generator

Beta
||View as Markdown|
Was this page helpful?
Edit this page
Next

Features

Early access

The CLI generator is in early access. Reach out to get started.

Fern’s CLI generator produces a fully functional command-line tool from the same API spec you already use for SDKs. It ships alongside your Docs and SDKs as a single binary with no runtime dependencies, serving AI agents that need deterministic output and runtime-introspectable schemas as well as human developers who script, debug, and explore.

Building a CLI by hand is a multi-quarter project — commands, auth, pagination, retries, output formatting, cross-platform builds, shell completions, and keeping it all in sync as the API evolves. The generator handles that automatically.

How it works

Supported API definitions

Generate a CLI from an OpenAPI spec or a GraphQL introspection schema.

The CLI generator plugs into the same Fern workflow as your Docs and SDKs. When your spec changes, Fern opens a PR against your CLI repo with the generated source. On release, Fern automatically publishes the CLI to npm, Homebrew, and GitHub Releases so your users can install it with their package manager of choice. The CLI stays in sync with your Docs and SDKs, and you never need to write CLI code by hand.

The output is a single statically linked Rust binary. Users drop it onto their PATH and run it. There’s no language runtime and no dependencies.

Built for agents and humans

Runtime introspection

Schema and help available as structured JSON.

Input validation

Double-encoded URLs and other malformed inputs are caught before any request is sent.

Interactive output

Colored help, tabular output, and shell completions.

Dry-run mode

Preview a request without sending it.

Version-pinned

Each release maps to a specific API version.