fftOne CLI for the fulfillmenttools API

One binary, one auth path, one output contract — reaching every one of the API's 557 operations from day one.

Every operation, from day one

Three tiers — curated commands, generated commands for the rest, and an escape hatch by operationId — share one binary. Not the endpoints someone got around to wrapping; all of them.

Auth that gets out of the way

Sign in once per project, switch between tenants freely, and let the CLI obtain and refresh tokens invisibly. Secrets live in your OS keychain.

A pipe is always safe

stdout is data and nothing else — totals, notices and prompts go to stderr. Under -o json you get the API's own bytes, never a re-encoding.

Runs without a tenant

fft emulator is a local, in-memory stand-in for the API — for a demo, a test, or trying a command out. Ships as a container image and as Go and Java Testcontainers modules.

Built for agents too

Ships an agent skill an AI reads before driving fft, compiled into the binary so it can never describe commands you don't have.