---
name: argus
description: Integrate machine-readable Argus facts, evidence, and neutral governance metadata.
---

# Argus Data Layer

## Customer-Side Installation

Set `ARGUS_BASE_URL`, run `argus auth login`, and use the live Agent Tool Registry as the runtime authority. Approved unattended clients may read `ARGUS_MACHINE_API_KEY`; do not pass credentials through a remote shell.

Authenticate through the approved CLI or machine credential and discover tools with `tool:agent_tool_registry`. Use `tool:field_catalog` before requesting unfamiliar fields.

Call read-only fact tools directly and pass declarative subjects, symbols, filters, and request `as_of`. Validate returned `effective_as_of` as response metadata. Preserve returned evidence, permissions, license, quality, and audit fields.

Run `argus tool-registry`; apply binding `parameter_aliases` and `parameter_encodings`. CLI and MCP arrays use comma-separated strings; REST arrays use JSON arrays. Use live OpenAPI for REST and `list_tools().inputSchema` for MCP. Decode business calls as `success`/`result`/`audit_id`; registry discovery is a raw snapshot. Omit server-managed identity fields with OAuth and check MCP `isError` before consuming structured content. Example subjects may not exist in production; resolve real identifiers first.

Argus does not produce interpretations, narratives, recommendations, strategies, orders, or account controls. The caller owns all analysis. Authentication and source-license controls remain mandatory.

## OAuth tool grants

Discovery does not grant execution rights. The signed `argus:tools:public` scope covers all 52 governed public business tools, including `metric_catalog` and the five bounded `stream_*` tools. Required signed scopes, permission, tenant, source-license, and output-policy checks still apply. Connector synchronization and platform administration are excluded. Do not retry a permission denial unchanged.