Skip to content

API overview

Argus provides read-only financial facts and separately authorized operations on personal data. CLI, REST and MCP share one public tool registry and the same governed core capability through CoreServiceBoundary. Each interface applies consistent checks for permissions, licenses, evidence, quality, timing, ownership and audit.

Consumer OAuth connections on https://mcp.argusfa.com/mcp list 20 consumer tools instead. They call the same governed tools and return consumer-result-v1.

The website's Developers page links the install scripts and Skill packages; individuals connecting an AI app start at Connect.

Use argus tool-registry or GET /v1/tool-registry to discover registry tools and their machine-readable migration metadata, and call them through the CLI or REST. The public MCP endpoint lists and calls only the consumer tools: agent_tool_registry and the other registry tools are neither listed nor callable there. See Generated Interface Contracts for the complete inventory.

Public onboarding and distribution endpoints on the API host include GET /cli, GET /skill, GET /mcp, GET /install, GET /windows/install, GET /v1/skills, and GET /v1/skills/{skill_id}; GET /mcp there is an HTML guide. The MCP endpoint itself is https://mcp.argusfa.com/mcp, which accepts OAuth only. The machine-authenticated /mcp-machine endpoint is internal-only: the public edge answers 404 for it. Credentials must never be passed through a remote shell.

For OAuth consumers, every tool reads only the sources that config/consumer_rights.yaml marks visible (requirements 3.1, section 6.4).

  • News events are left out, and so are events, corporate actions and materials from hidden sources.
  • Stream topics from hidden sources are absent from the catalog and answer as an unknown topic.
  • An option chain with no visible records reports the neutral option_record_store provider status instead of a hidden provider.

Machine connections keep their governed behaviour.

The API returns structured facts and neutral, reproducible metadata. The personal tools also manage watchlists, research, subscriptions, manual asset records and controlled exports under current owner consent. Personal results use typed problem/payload contracts; legacy financial tools retain CliToolEnvelope. See personal tools and executable examples.

Sensitive account revocation and deletion use the trusted owner application, not ordinary Agent tools. Argus does not generate investment recommendations, orders, narratives or trading strategies. Its structured filing workflow retrieves facts, evidence and transparent calculations for the caller's agent.