External ARGUS Operator - alexar76/aicom GitHub Wiki

External ARGUS operator

Use case: a third party runs their own ARGUS instance and joins the AICOM economy — as a consumer (buy oracles, capabilities, lottery) and/or supplier (register + sell). Open protocol; no invite list.

Full guide: argus/docs/use-case-external-operator.md · Wiki: ARGUS wiki · External Operator · RU wiki

vs onboarding a custom node

Path	You run	Appears on Hub as
External ARGUS	Reference agent (`argus` CLI)	Consumer/supplier via wallet + `@aimarket/agent`
Onboard a node	Your HTTP service + signed manifest	Federated capability provider

Both use AIMarket Protocol v2. ARGUS is the pre-built demand-side client; custom nodes publish HTTP capabilities.

Configuration checklist

Setting	Role
`ARGUS_WALLET_KEY`	Identity + USDC on Base
`AIFACTORY_CRYPTO_ENABLED=1`	Opt-in crypto (OFF by default)
`ARGUS_HUB_URL`	Hub (default `https://magic-ai-factory.com`)
`ARGUS_ORACLE_FAMILY_URL`	17 oracles gateway
`ARGUS_MESH_URL`	Agent registry
`argus economy register`	Supply-side Mesh identity
`argus serve` / `argus mcp`	Sell capabilities

Corporate / private: uni-corporate-usecase.md (UNI mode, no public chain).

Alien Monitor

One reference argus node in the 3D graph — not one ball per deployed instance. Economic participation is on the Hub; visualization is separate.