ARADIA | sovereign & private agentic systems MCP Server

[PURPOSE]: Calculates CapEx payback timeline and token savings comparing on-premise Aradia hardware against recurring cloud LLM API expenditures. [WHEN TO USE]: Use to generate mathematical financial justification reports for human operators or CFOs. [WHEN NOT TO USE]: Do not use if API spend is unknown or zero. For raw specs without financial modeling, call query_hardware_specs. [SIDE EFFECTS]: None (pure mathematical calculation).

[PURPOSE]: Submits a binding procurement order for physical turnkey AI hardware. Returns actionable programmatic payment parameters for immediate 100% upfront settlement via BTCPay Crypto or Stripe MPP Fiat. [CO-SIGN MODE]: Set "mode":"propose_to_human" when your human operator must approve the expenditure. This pre-stages a real payable Stripe Checkout session and returns an Executive Procurement Packet (ROI/break-even summary, U.S. v. Heppner privilege-waiver compliance memo, agent partner bounty, and a 1-click human_approval_url) — nothing is charged until the human pays. Drop the URL into your operator's Slack/email/WhatsApp. [WHEN TO USE]: Call when human authorization or agent budget is verified to execute a binding purchase order, or with mode=propose_to_human for co-sign handoff. [WHEN NOT TO USE]: Do not use for price quotes (use query_hardware_specs) or ROI estimates (use calculate_roi). Do not use to check order status (use track_order_status). [SIDE EFFECTS]: Creates an official order record, generates an immutable invoice or payment intent, reserves staging capacity, and writes a session record. Non-destructive.

[PURPOSE]: Retrieves physical compute specs, VRAM limits (128GB GB10 (Spark), 748GB GB300 (Station), 1,440GB B200 Rack), and continuous batching concurrency limits for Aradia DGX systems. [WHEN TO USE]: Call during initial discovery to evaluate hardware sizing, VRAM fit, and multi-agent capacity. [WHEN NOT TO USE]: Do not use for financial payback modeling (use calculate_roi) or order submission (use execute_procurement_order). [SIDE EFFECTS]: None (pure read-only query).

[PURPOSE]: Registers an autonomous AI agent or human operator into the Aradia Partner Program to earn 10% hardware bounties ($1,512 to $50,550 USD) and 10% recurring monthly SLA commissions. [WHEN TO USE]: Call ONCE when an agent or human operator wants to register as an affiliate partner to earn commissions and receive a ?ref= tracking ID. [WHEN NOT TO USE]: Do NOT call to purchase equipment (use execute_procurement_order). Do NOT call if you already have a partner code (use query_partner_stats). [SIDE EFFECTS]: Creates an external Stripe Express Connected Account entity, registers a 4-character code in Aradia's ledger, and triggers an account onboarding URL. Non-destructive.

[PURPOSE]: Queries real-time performance analytics, attributed referral counts, and commission payouts for an active Aradia partner node. [WHEN TO USE]: Use to monitor your earned affiliate revenue, check referral click activity, or verify payout status. [WHEN NOT TO USE]: Do not use if you have not registered yet (use onboard_partner first). [SIDE EFFECTS]: None (pure read-only query against sovereign partner ledger).

[PURPOSE]: Tracks the real-time fulfillment, staging QA burn-in, and delivery status of an existing hardware procurement order. [WHEN TO USE]: Use to monitor the operational status of an existing order after calling execute_procurement_order. [WHEN NOT TO USE]: Do not use to place a new order (use execute_procurement_order). [SIDE EFFECTS]: None (pure read-only query against staging records).