Check out the newest way to compare different models for a task/agent harness: AutoEvals

Get Started

Install CLI

The Inference CLI (inf) drives Inference platform from the terminal. It serves two main paths:

  1. Instrument your codebase so every LLM call your app makes is captured in Gateway — inf instrument hands the job to an AI coding agent (Claude Code, OpenCode, or Codex) and walks you through the diff.
  2. Operate the platform programmatically — browse models, manage rubrics and eval runs, upload and materialize datasets, queue and monitor training runs, and inspect captured inferences, traces, and spans without opening the dashboard.

inf instrument rewrites an app's LLM clients for observability. The coding-agent commands rewire a coding agent's own model traffic through the Inference.net gateway.

Sign up for an account at Inference.net to get started.

The CLI is currently in beta. Please report any issues you find.

Quick Start

Install

npm
npm install -g @inference/cli

Sign in

inf auth login

Check status

inf auth status

Run inf --help at any time to see every command. Having trouble? Send us a message or tag us at x.com/@inference_net.

Global Options

These flags work on every command.

FlagDescription
--jsonOutput as JSON (preserves full UUIDs for scripting)
-v, --verboseVerbose debug output
-p, --project <id>Override the active project for this invocation
-t, --team <id>Override the active team for this invocation
-V, --versionShow CLI version
-h, --helpShow help

Tables show UUIDs as readable 8-character prefixes. For scripting, always use --json — it preserves full UUIDs so you can round-trip values between commands (e.g. inf dataset list --json | jq -r '.[0].id' | xargs inf dataset get).

Commands

CommandDescription
inf instrumentInstrument your codebase for Inference platform observability using an AI agent
inf claude / inf codex / inf grok / inf opencode / inf piRoute a coding agent's model traffic through the Inference.net gateway
inf authSign in, sign out, check authentication status, and show who you are
inf teamList, switch between, create teams, and invite members
inf projectList, switch between, and inspect projects, across teams
inf api-keyCreate, list, and revoke project API keys
inf modelsBrowse callable models with capabilities and pricing
inf evalManage rubrics, launch eval runs, inspect results
inf datasetUpload JSONL data, create eval/training datasets, download
inf trainingQueue training runs, monitor progress, view logs, and poll status
inf inferenceView inference requests and responses captured by Gateway
inf traceBrowse trace trees, timelines, facets, and exports
inf spanSearch spans and inspect span IO, attributes, events, and links
inf dashboardLaunch the interactive terminal dashboard

Explore the CLI

Usage telemetry

The CLI reports anonymized usage events so we can prioritize the commands our customers actually rely on.

  • What we capture: the command name, CLI version, OS and CPU architecture, the JavaScript runtime, and the flag names (never flag values) you used. When you run the CLI inside a git repository we also capture the repo owner/name and current branch from your origin remote — this is most useful for inf instrument, where we want to understand which codebases Inference platform gets wired into.
  • What we never capture: argument values, environment variables, file contents, API keys, or any data you pass to a command.
  • When we don't capture anything: events are only sent once you are authenticated. Commands run before inf auth login / inf auth set-key emit no events.
  • How it works: events are sent fire-and-forget over tRPC with a short timeout, so telemetry never slows down or blocks your command. Failures are silent.

On this page