Skip to content

CLI and Skill

The CLI calls CoreServiceBoundary for your agent and returns JSON on stdout. Logs go to stderr, so your agent can parse results without mixing them with diagnostics.

CLI JSON uses standard Unicode escapes so redirected output also works with legacy Windows console encodings. Parse the JSON to recover the original Unicode text and exact numeric strings; escaped text does not change values.

The CLI reaches the registry tools over REST. AI apps connected over MCP use the consumer tools instead.

Install and sign in

Install the official CLI from the API host. On Linux or macOS:

curl -fsSL https://api.argusfa.com/install | bash

In Windows PowerShell:

irm https://api.argusfa.com/windows/install | iex

Then sign in in your browser and check the session:

argus auth login
argus auth status

The CLI uses Authorization Code + PKCE S256 and the operating system's credential store, and never stores a client secret. An OAuth session selects the public API by itself. The CLI and the Skill run on your own machine; neither opens a shell on an Argus server.

Skill packages

A Skill tells a coding agent how to use the CLI. Fetch a package from the public API and verify the checksum it returns before you install it:

curl https://api.argusfa.com/v1/skills/codex
curl https://api.argusfa.com/v1/skills/claude-code
curl https://api.argusfa.com/v1/skills/multi-agent-workflow

GET /v1/skills lists the packages. The website's Developers page links the install scripts and Skill packages as well.

Identity and common fields

Official interactive login now exchanges the code through the trusted session component. Set the nonsecret ARGUS_SESSION_BASE_URL when the component has a separate origin; otherwise it uses ARGUS_BASE_URL. The server must have matching pre-registered cli-api and cli-mcp client keys (override with ARGUS_SESSION_API_CLIENT_KEY / ARGUS_SESSION_MCP_CLIENT_KEY). Run argus auth login --interface api or --interface mcp; the two audiences use separate OS credential-store entries. When MCP has a distinct pre-registered client, set its nonsecret ARGUS_OAUTH_MCP_CLIENT_ID. ARGUS_CLI_PROFILE selects a local installation/profile namespace, allowing two sessions on the same machine; this local label never determines server ownership.

The OS store contains only the opaque Argus session credential. Upstream tokens stay encrypted in the identity component. argus auth status checks the real registered session and returns safe metadata; argus auth refresh refreshes its upstream chain without changing its session ID or original absolute deadline. argus auth logout clears local credentials only and explicitly reports that it has not revoked the server session. Account-management revocation is separate. Never paste credentials into chat, command output, documentation or issue reports. See session protocol for the endpoints.

Use argus auth login for personal OAuth and registered unattended sessions. Identity is determined by the server. Data requests accept purpose, as_of, and output-format fields. They do not accept free-form execution instructions.

Capability discovery

Ordinary help shows personal and everyday research commands. Advanced research and diagnostics are grouped in the registry and require explicit signed grants. Platform provisioning and audit export live in the internal argus machine group. Run argus tool-registry for the authoritative inventory and structured major-version migration manifest. Generated parameter and transport mappings are in Generated Interface Contracts. Inspect argus <command> --help for executable options and defaults. Legacy financial commands accept --requires-redistribution and propagate it to core license checks.

The CLI has no commands for the 20 consumer tools. Those tools exist only on the OAuth MCP endpoint and are not registry entries.

Personal commands accept a closed JSON object through --request-file FILE. For example, argus personal-usage-read-v1 --request-file usage.json reads a file containing {"request_id":"usage-example","hours":24}. It requires the signed personal usage scope and active owner consent. Decode problem/payload using the personal contract, and follow the personal examples for writes, version checks and exports. Do not add legacy purpose, redistribution or ownership fields to a personal request.

For CLI bindings, apply parameter_aliases, then replace underscores with hyphens. Array parameters are comma-separated strings. For example, normalized field_names maps to --fields revenue,net_income; preflight range_start and range_end map to --from and --to.

JSON-string parameters ending in -json must encode the declared shape: filters, sort, facts, nodes, and observations are JSON arrays; limits is a JSON object. Use [] for an empty array and {} for an empty object. null is not an empty collection. A supplied invalid date or structured value returns success=false with error.error_code=invalid_argument on stdout and exit code 2, including in remote mode. Exit code 1 indicates an authentication, governance, or remote request failure. Shell syntax and missing options are reported by the CLI parser on stderr.

For a real first request, install the CLI and sign in, then call a registry tool:

argus auth login
argus --base-url https://api.argusfa.com entity-resolve --identifier-type ticker --identifier-value AAPL

The examples below show parameter syntax only. Their example identifiers and dates do not establish production coverage. Discover a real company/security identifier and check the source's actual historical window before replacing them; an empty or unavailable response is not a successful data request. point-in-time-dataset-export is an advanced command and needs an explicit signed grant.

argus filing-evidence-extract --query-terms revenue,annual
argus market-session-fact-package --market US --session us_regular_close --session-date 2026-06-16 --symbols EXM,ACME
argus point-in-time-dataset-export --as-of 2026-06-16T20:00:00Z

Financial commands read facts, evidence, catalogs, bounded streams and governance metadata, or perform controlled data exports. Personal commands additionally read and write private records, subscriptions and manual assets under explicit domain consent. The default public fact grant does not grant private access. Account revocation/deletion remains in the trusted owner flow. There are no investment recommendation, trading or agent-orchestration commands.