Pp Openrouter

OpenRouter — Printing Press CLI

Prerequisites: Install the CLI

This skill drives the openrouter-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:

1. Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:

   npx -y @mvanhorn/printing-press-library install openrouter --cli-only

2. Verify: openrouter-pp-cli --version
3. Ensure the reported install directory is on $PATH for the agent/runtime that will invoke this skill.

If the npx install fails before this CLI has a public-library category, install Node or use the category-specific Go fallback after publish.

If --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.

Every other OpenRouter tool wraps chat; this one governs it. A synced local mirror of models, generations, and credits powers per-cron cost attribution (usage cost-by), pre-flight budget gates (budget check), degradation watches (providers degraded), and runway projections (credits runway) that no single API call can answer. The full endpoint surface — catalog, keys admin, activity, analytics — ships alongside as typed commands.

When to Use This CLI

Reach for this CLI when the task is operating LLM workloads over OpenRouter: attributing spend to crons or agents, gating scheduled runs on budgets, shortlisting models by capability and price, watching provider health before dispatch, or projecting credit and cap runway. It is the right tool whenever the question spans local history plus the API — anything a single raw HTTP call cannot answer.

Anti-triggers

Do not use this CLI for:

• Interactive chat sessions or a conversational playground — use a chat client; the chat command here is agent plumbing, not a UX
• Building application inference paths — use the official OpenRouter SDKs in your app, not shell-outs to a CLI
• Org member management, SCIM provisioning, or SSO setup — use the OpenRouter dashboard
• Real-time token streaming displays — the CLI returns complete responses, not stream renderers

Unique Capabilities

These capabilities aren't available in any other tool for this API.

Catalog intelligence

• models query — Shortlist models by capability, price, and context window with a structured query over the synced catalog — offline and instant.

  Reach for this instead of fetching the full catalog: it answers a shortlist question in ~200 tokens instead of hundreds of KB.

  openrouter-pp-cli models query "tools=true cost.completion<5 ctx>=128k" --agent

• models churn — See what changed in the model catalog between syncs: additions, removals, and repricings with deltas.

  Use this to catch a pinned model repricing or vanishing before the invoice does.

  openrouter-pp-cli models churn --since 7d --agent

Cost governance for agent fleets

• usage cost-by — Attribute spend to the cron, agent, or lineage that incurred it, over any window.

  Use this when the question is 'which job burned the money', not 'which model'.

  openrouter-pp-cli usage cost-by --since 7d --agent

• usage anomaly — Flag per-model cost spikes against the trailing baseline before they compound.

  Run this in a daily cron to catch a misbehaving lineage the day it regresses, not at invoice time.

  openrouter-pp-cli usage anomaly --since 24h --agent

• budget — Set spend caps per cron or agent and enforce them pre-flight with typed exit codes.

  Gate a scheduled run on exit code 0/8 so an over-budget lineage never fires.

  openrouter-pp-cli budget check nightly-drafter

• generation explain — Break one generation into its cost anatomy: tokens, latency, and the delta versus the cheapest provider.

  The next command after an anomaly fires: it turns 'cost spiked' into 'this call, this provider, this delta'.

  openrouter-pp-cli generation explain gen-abc123 --agent

• usage reconcile — Verify the local usage mirror against upstream daily totals and flag days that disagree.

  Run this before trusting any local cost analysis — it is the trust root for the other usage commands.

  openrouter-pp-cli usage reconcile --since 7d --agent

Provider health and dispatch

• providers degraded — See which providers or models are currently degraded before dispatching work to them.

  Check this before dispatch to route around trouble instead of retrying into it.

  openrouter-pp-cli providers degraded --agent

• endpoints failover — Rank the providers serving one model by status, price, and observed latency for dispatch order.

  Feed this to a router to pre-empt degraded providers for a specific model.

  openrouter-pp-cli endpoints failover deepseek/deepseek-v4 --agent

Runway and rate-limit headroom

• key eta — Project the date your key's spend cap trips, from the observed burn rate.

  Use this to plan the week's runs against the cap instead of discovering it mid-run.

  openrouter-pp-cli key eta --agent

• limits status — One view of current headroom: key-cap remaining, free-tier daily quota, and today's free-model burn.

  Check before a free-tier dev loop or fleet dispatch to avoid opaque 429s.

  openrouter-pp-cli limits status --agent

• credits runway — Project days-to-zero for prepaid credits at the trailing burn rate — the 402 leading indicator.

  A daily cron on this answers 'when do we hit 402' while there is still time to top up.

  openrouter-pp-cli credits runway --agent

Command Reference

activity — Manage activity

• openrouter-pp-cli activity — Returns user activity data grouped by endpoint for the last 30 (completed) UTC days.

audio — Manage audio

• openrouter-pp-cli audio create-speech — Synthesizes audio from the input text. Returns a raw audio bytestream in the requested format (e.g. mp3, pcm, wav).
• openrouter-pp-cli audio create-transcriptions — Transcribes audio into text.

benchmarks — Benchmarks endpoints

• openrouter-pp-cli benchmarks — Unified benchmark endpoint that aggregates scores from multiple benchmark sources (Artificial Analysis, Design Arena

byok — BYOK endpoints

• openrouter-pp-cli byok create-byokkey — Create a new bring-your-own-key (BYOK) provider credential.
• openrouter-pp-cli byok delete-byokkey — Delete (soft-delete) a bring-your-own-key (BYOK) provider credential by its id.
• openrouter-pp-cli byok get-byokkey — Get a single bring-your-own-key (BYOK) provider credential by its id.
• openrouter-pp-cli byok list-byokkeys — List the bring-your-own-key (BYOK) provider credentials for the authenticated entity's default workspace.
• openrouter-pp-cli byok update-byokkey — Update an existing bring-your-own-key (BYOK) provider credential by its id.

chat — Chat completion endpoints

• openrouter-pp-cli chat — Sends a request for a model response for the given chat conversation. Supports both streaming and non-streaming modes.

classifications — Task classification market-share endpoints

• openrouter-pp-cli classifications — Returns the market-share breakdown of OpenRouter traffic by task classification (e.g.

containers — Containers endpoints

credits — Credit management endpoints

• openrouter-pp-cli credits create-coinbase-charge — Deprecated.
• openrouter-pp-cli credits get — Get total credits purchased and used for the authenticated user.

datasets — Public OpenRouter usage datasets. Data returned by these endpoints is licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/): reuse and republish it, including commercially, with attribution to OpenRouter.

• openrouter-pp-cli datasets get-app-rankings — Returns the top public apps on OpenRouter ranked by token usage inside the requested date window
• openrouter-pp-cli datasets get-rankings-daily — Returns the top 50 public models per day by total token usage on OpenRouter
• openrouter-pp-cli datasets get-session-cost — Returns weekly refreshed, aggregated cost-per-session cells for the published harnesses.

embeddings — Text embedding endpoints

• openrouter-pp-cli embeddings create — Submits an embedding request to the embeddings router
• openrouter-pp-cli embeddings list-models — Returns a list of all available embeddings models and their properties

endpoints — Endpoint information

• openrouter-pp-cli endpoints — Preview the impact of ZDR on the available endpoints

files — Files endpoints

• openrouter-pp-cli files delete — Deletes a file owned by the requesting workspace. Deletion is irreversible.
• openrouter-pp-cli files get-metadata — Retrieves metadata for a single file owned by the requesting workspace.
• openrouter-pp-cli files list — Lists files belonging to the workspace of the authenticating API key.
• openrouter-pp-cli files upload — Uploads a file to be referenced in future API calls.

generation — Generation history endpoints

• openrouter-pp-cli generation get — Get request & usage metadata for a generation
• openrouter-pp-cli generation list-content — Get stored prompt, completion, and error content for a generation
• openrouter-pp-cli generation submit-feedback — Submit structured feedback on a generation the authenticated user made.

guardrails — Guardrails endpoints

• openrouter-pp-cli guardrails create — Create a new guardrail for the authenticated user.
• openrouter-pp-cli guardrails delete — Delete an existing guardrail. Management key required.
• openrouter-pp-cli guardrails get — Get a single guardrail by ID. Management key required.
• openrouter-pp-cli guardrails list — List all guardrails for the authenticated user.
• openrouter-pp-cli guardrails list-key-assignments — List all API key guardrail assignments for the authenticated user.
• openrouter-pp-cli guardrails list-member-assignments — List all organization member guardrail assignments for the authenticated user.
• openrouter-pp-cli guardrails update — Update an existing guardrail, or materialize an unconfigured workspace default guardrail.

images — Images endpoints

• openrouter-pp-cli images create — Generates an image from a text prompt via the image generation router
• openrouter-pp-cli images list-model-endpoints — Returns the full per-endpoint records for an image model: each endpoint's definitive supported parameters, pricing
• openrouter-pp-cli images list-models — Lists every image generation model with its top-level supported-parameter superset and a URL to its full per-endpoint

key — Manage key

• openrouter-pp-cli key — Get information on the API key associated with the current authentication session

keys — Manage keys

• openrouter-pp-cli keys create — Create a new API key for the authenticated user. The plaintext key is returned only in this response.
• openrouter-pp-cli keys delete — Delete an existing API key.
• openrouter-pp-cli keys get — Get a single API key by hash. Management key required.
• openrouter-pp-cli keys list — List all API keys for the authenticated user. Management key required.
• openrouter-pp-cli keys update — Update an existing API key.

messages — Manage messages

• openrouter-pp-cli messages — Creates a message using the Anthropic Messages API format. Supports text, images, PDFs, tools, and extended thinking.

model — Model information endpoints

• openrouter-pp-cli model <author> <slug> — Returns full details for a single model identified by its author and slug (e.g. openai/gpt-4).

models — Model information endpoints

• openrouter-pp-cli models get — List all models and their properties
• openrouter-pp-cli models list-count — Get total count of available models
• openrouter-pp-cli models list-user — List models filtered by user provider preferences, [privacy settings](https://openrouter.

observability — Observability endpoints

• openrouter-pp-cli observability create-destination — Create a new observability destination. A maximum of 5 destinations per type is allowed.
• openrouter-pp-cli observability delete-destination — Delete an existing observability destination. This performs a soft delete.
• openrouter-pp-cli observability get-destination — Fetch a single observability destination by its UUID.
• openrouter-pp-cli observability list-destinations — List the observability destinations configured for the authenticated entity's default workspace.
• openrouter-pp-cli observability update-destination — Update an existing observability destination. Only the fields provided in the request body are updated.

openrouter-analytics — Manage openrouter analytics

• openrouter-pp-cli openrouter-analytics get-meta — Returns the available metrics, dimensions, filter operators, and granularities for the analytics query endpoint.
• openrouter-pp-cli openrouter-analytics query — Execute an analytics query with specified metrics, dimensions, filters, and time range.

openrouter-auth — Manage openrouter auth

• openrouter-pp-cli openrouter-auth create-keys-code — Create an authorization code for the PKCE flow to generate a user-controlled API key
• openrouter-pp-cli openrouter-auth exchange-code-for-apikey — Exchange an authorization code from the PKCE flow for a user-controlled API key

organization — Organization endpoints

• openrouter-pp-cli organization — List all members of the organization associated with the authenticated management key.

presets — Presets endpoints

• openrouter-pp-cli presets get — Retrieves a preset by its slug with its currently designated version inline.
• openrouter-pp-cli presets list — Lists all presets for the authenticated user, ordered by most recently updated first.

providers — Provider information endpoints

• openrouter-pp-cli providers — List all providers

rerank — Rerank endpoints

• openrouter-pp-cli rerank — Submits a rerank request to the rerank router

responses — OpenAI-compatible Responses API endpoints

• openrouter-pp-cli responses — Creates a streaming or non-streaming response using OpenResponses API format

scim — SCIM endpoints

• openrouter-pp-cli scim create-group-mapping — Create a SCIM group-to-workspace role mapping.
• openrouter-pp-cli scim delete-group-mapping — Delete a SCIM group-to-workspace mapping. Management key required.
• openrouter-pp-cli scim get-group-mapping — Get a SCIM group-to-workspace mapping. Management key required.
• openrouter-pp-cli scim list-group-mappings — List SCIM group-to-workspace mappings for the organization.
• openrouter-pp-cli scim list-groups — List SCIM groups for the organization. Management key required.
• openrouter-pp-cli scim update-group-mapping — Update a SCIM group mapping role. Management key required.

videos — Manage videos

• openrouter-pp-cli videos create — Submits a video generation request and returns a polling URL to check status
• openrouter-pp-cli videos get — Returns job status and content URLs when completed
• openrouter-pp-cli videos list-models — Returns a list of all available video generation models and their properties

workspaces — Workspaces endpoints

• openrouter-pp-cli workspaces create — Create a new workspace for the authenticated user.
• openrouter-pp-cli workspaces delete — Delete an existing workspace. Workspaces with active API keys cannot be deleted; remove the keys first.
• openrouter-pp-cli workspaces get — Get a single workspace by ID or slug. Management key required.
• openrouter-pp-cli workspaces list — List all workspaces for the authenticated user.
• openrouter-pp-cli workspaces update — Update an existing workspace by ID or slug. Management key required.

Finding the right command

When you know what you want to do but not which command does it, ask the CLI directly:

openrouter-pp-cli which "<capability in your own words>"

which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match — fall back to --help or use a narrower query.

Recipes

Monday cost review

openrouter-pp-cli usage cost-by --since 7d --agent

The weekly attribution pass: spend per cron/agent tag, ready to paste into a review note.

Anomaly to root cause in two commands

openrouter-pp-cli usage anomaly --since 24h --agent

When a model flags, follow with 'generation explain <id>' to get tokens, latency, and the cheapest-provider delta for the offending call.

Pre-dispatch health gate

openrouter-pp-cli providers degraded --agent

Run before firing a lineage; pair with 'endpoints failover <model>' to pick the dispatch order for the model you are about to use.

Narrow a deep endpoint payload

openrouter-pp-cli models endpoints list deepseek deepseek-v4 --agent --select data.endpoints.provider_name,data.endpoints.pricing.completion,data.endpoints.status

Per-model provider listings nest deeply; --select keeps the answer to the three fields a router actually needs.

Budget-gated cron pattern

openrouter-pp-cli budget check nightly-drafter

Exit code 0 under cap, 8 over — gate a scheduled run on this before it fires (e.g. 'budget check X && systemctl --user start X.service').

Auth Setup

Standard bearer auth with your inference key via OPENROUTER_API_KEY covers models, credits, key status, and chat. Two surfaces need the separate provisioning (management) key created in the dashboard: key administration (/keys) and account-wide usage rollups (/activity, analytics). A 401 or 403 on those commands with an otherwise-working key means you are holding the inference key where the management key is required — not a broken setup. Live-verified 2026-09: /activity returns 403 'Only management keys can fetch activity' on an inference key.

The CLI reads a single env var (OPENROUTER_API_KEY); it does not read OPENROUTER_MANAGEMENT_KEY. To call management-key endpoints, set your management key as the API key for that invocation. Ensure OPENROUTER_MANAGEMENT_KEY is set in your environment first:

# Prerequisite: export OPENROUTER_MANAGEMENT_KEY=<your-management-key>
OPENROUTER_API_KEY="${OPENROUTER_MANAGEMENT_KEY}" openrouter-pp-cli keys list --agent
OPENROUTER_API_KEY="${OPENROUTER_MANAGEMENT_KEY}" openrouter-pp-cli activity --agent

Run openrouter-pp-cli doctor to verify setup.

Agent Mode

Add --agent to any command. Expands to: --json --compact --no-input --no-color.

• Pipeable — JSON on stdout, errors on stderr

• Filterable — --select keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:

  openrouter-pp-cli benchmarks --agent --select accuracy,accuracy_stddev,agentic_index

• Previewable — --dry-run shows the request without sending

• Offline-friendly — sync/search commands can use the local SQLite store when available

• Non-interactive — never prompts, every input is a flag

• Explicit confirmation — --agent does not imply --yes; pass --yes separately only after the target, arguments, and side effects are clear

• Explicit retries — use --idempotent only when an already-existing create should count as success, and use --ignore-missing only when a missing delete target should count as success

Response envelope

Commands that read from the local store or the API wrap output in a provenance envelope:

{
  "meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
  "results": <data>
}

Parse .results for data and .meta.source to know whether it's live or local. A human-readable N results (live) summary is printed to stderr only when stdout is a terminal AND no machine-format flag (--json, --csv, --compact, --quiet, --plain, --select) is set — piped/agent consumers and explicit-format runs get pure JSON on stdout.

Paths and state

Agents should treat the CLI's path resolver as part of the runtime contract:

• Use --home <dir> for one invocation, or set OPENROUTER_HOME=<dir> to relocate all four path kinds under one root.

• Use per-kind env vars only when a specific kind must diverge: OPENROUTER_CONFIG_DIR, OPENROUTER_DATA_DIR, OPENROUTER_STATE_DIR, OPENROUTER_CACHE_DIR.

• Resolution order is per-kind env var, --home, OPENROUTER_HOME, XDG (XDG_CONFIG_HOME, XDG_DATA_HOME, XDG_STATE_HOME, XDG_CACHE_HOME), then platform defaults.

• config contains settings like config.toml and profiles. data contains credentials.toml, data.db, cookies, and auth sidecars. state contains persisted queries, jobs, and teach.log. cache contains regenerable HTTP/cache files.

• Stored secrets live in credentials.toml under the data dir. Existing legacy config.toml secrets are read for compatibility and leave config.toml on the first auth write.

• Run openrouter-pp-cli doctor --fail-on warn to surface path and credential-location warnings. agent-context exposes a schema v4 paths block for agents that need the resolved dirs.

• For MCP, pass relocation through the MCP host config. The MCP binary does not inherit CLI flags:

  {
    "mcpServers": {
      "openrouter": {
        "command": "openrouter-pp-mcp",
        "env": {
          "OPENROUTER_HOME": "/srv/openrouter"
        }
      }
    }
  }

Fleet precedence: an inherited per-kind env var overrides an explicit --home for that kind. Use OPENROUTER_HOME or per-kind vars as durable fleet levers, and use --home only for a single invocation. Relocation is not reversible by unsetting env vars; move files manually before clearing OPENROUTER_HOME, or doctor will not find credentials left under the former root.