anyapi-cli

Official CLI for AnyAPI: any API, one key, one USD wallet, pay per request.

Install

npx -y anyapi-cli@latest --help

For local development:

npm install
npm run build
node dist/index.js --help

Quick start

anyapi init
anyapi search reddit
anyapi describe reddit.search
anyapi run reddit.search --input '{"query":"anyapi","limit":5}'

anyapi init mints a free trial key when none is available (about $0.05 of requests, no account created, self-expires in 7 days), saves it to ~/.anyapi/config.json, and installs the bundled agent skills. When the trial budget runs out, anyapi connect upgrades past it with one human approval.

Commands

• anyapi signup [--label <label>] [--show-key] - mint a free trial key and save it locally. The secret is not printed unless you pass --show-key.
• anyapi connect - upgrade past the free trial via a one-URL OAuth 2.1 approval (Authorization Code + PKCE over a loopback callback). Prints a single consent URL for a human to open; on approval the CLI stores the access token and keeps working.
• anyapi login - sign in to an AnyAPI account immediately with the OAuth 2.0 device flow. The CLI prints a verification URL and user code, opens the complete URL when possible, and waits without binding a localhost callback.
• anyapi login --api-key aa_live_... - manual-key compatibility path: store an existing dashboard key locally without starting OAuth.
• anyapi search <query> - search the public catalog and print SKU, name, and USD price terms. --category <cat> and --platform <platform> scope the search, and either one works without a query.
• anyapi list [--category <cat>] - list catalog APIs.
• anyapi describe <sku> - print the authenticated API definition, including opaque schemas and gateway-published USD pricing, lane order, and failover metadata.
• anyapi run <sku> [--input '<json>'] [-i file] [--idempotency-key <key>] [--jq <expr>] [--fields a,b] [--max-items N] [--summary] [-o path] [--json] - run an API. Always saves the full result; shape flags trim only the stdout view.
• anyapi view [path] [--last [sku]] [--jq <expr>] [--fields a,b] [--max-items N] [--summary] [--json] - re-shape a saved run file locally. Zero network, zero cost.
• anyapi balance - print the remaining USD balance.
• anyapi report-bug <summary> [--details <text>] [--sku <sku>] [--request-id <id>] [--contact <email>] - tell us something is broken: a wrong or empty result, a misleading error, a price that looks off. Free, never charged. --request-id from the failing run is the most useful thing you can attach, because it reaches the stored run and its upstream error body.
• anyapi feedback <summary> [--details <text>] [--sku <sku>] [--request-id <id>] [--contact <email>] - tell us something that is not a defect: a missing API, a missing field, confusing docs. Free, never charged.
• anyapi init [--all] [--yes] - mint a trial key if none exists, install bundled agent skills, and show or apply MCP setup snippets.
• anyapi setup skills - install only the bundled skills.

Auth resolution order is --api-key, then ANYAPI_API_KEY, then ~/.anyapi/config.json, then trial self-signup. When the trial budget is spent, runs return HTTP 402 trial_cap_reached; run anyapi connect to continue.

Use login for immediate account-backed OAuth on any device. Use connect to upgrade and continue an existing free trial while preserving its trial receipt. OAuth access tokens refresh automatically from the saved session before expiry.

Gateway and CLI responsibilities

The AnyAPI gateway owns input validation, provider normalization, pricing, lane order, routing, failover, and billing. The CLI is a thin transport and presentation adapter: it reads the known discovery fields it displays, tolerates safe additive discovery fields, and preserves input/output schemas as opaque JSON. In particular, pricing.from, pricing.failoverMaxUsd, and failover are authoritative gateway facts; the CLI does not recompute them from lanes.

Successful run payloads are customer data and pass through unchanged. Fields such as creditScore, provider, or providers inside a SKU's output are not discovery metadata and are never recursively removed or rewritten by the CLI.

Run idempotency

The CLI generates a fresh random idempotency key for every logical invocation. Use an explicit key when a run may need to be resumed manually without another charge:

anyapi run reddit.search --input '{"query":"anyapi"}' --idempotency-key k1

Repeating the same request with the same key returns the original result without another charge. Keys must be 1 to 255 visible ASCII characters. You can explicitly request another random key with auto:

anyapi run reddit.search --input '{"query":"anyapi"}' --idempotency-key auto

auto creates a random key for that invocation. It does not deduplicate a separate CLI command.

If a key is already running, the CLI asks you to retry shortly with the same key. If a key was used with a different SKU or input, the CLI asks you to use a new key or retry the original request.

Run output and local shaping

run always fetches and saves the full result to .anyapi/<sku>-<timestamp>.json and prints the path, costUsd, and items. Shaping is local: --jq, --fields, --max-items, and --summary trim only what is printed to stdout, never the saved file.

Because the full result is on disk, you pay once and re-slice it forever at zero cost with anyapi view:

# One paid run, saved in full:
anyapi run web.scrape --input '{"url":"https://example.com"}'

# Re-slice the same saved file for free - no network, no charge:
anyapi view --last web.scrape --jq '.data | {title, description}'
anyapi view --last web.scrape --jq '.data.markdown[:3500]'      # first chunk
anyapi view --last web.scrape --jq '.data.markdown[3500:7000]'  # next chunk
anyapi view --last --summary                                    # fields + byte sizes

jq targets the result output envelope {found, data}, so expressions start at .data or .found (identical on run and view). view --last <sku> reads the newest saved run for that SKU; omit the sku (or run a bare anyapi view) for the newest run of any SKU; or pass an explicit file path. A wrong jq expression prints the error and exits non-zero - the saved result is untouched, so just fix the expression and re-run view.

jq runs via a bundled WebAssembly build of jq (real jq 1.8.2, no system install required); if it cannot load, the CLI falls back to a system jq binary.

Migration note: shape flags used to be sent to the server and trimmed the saved file. As of 0.2.0 they are local and the saved file is always complete.

Publish

Tags matching v* run the compiled CLI against the live credentialless discovery endpoints, then publish to npm through GitHub Actions using the NPM_TOKEN secret and npm provenance.