# iAgentEdge

> Agent Infrastructure Appliance, Turnkey On-Prem

iAgentEdge will ship as a pre-configured agent infrastructure appliance: hardware BOM plus iJarvis Agent Stack pre-installed plus remote management via Tailscale. First pilot deployments targeted 2027 after Cluster 1 customer references are in place.

## Planned capabilities

- **Reference hardware BOM**: Documented build guide from $25K dev-scale to $250K enterprise-scale.
- **Pre-configured stack**: Every iJarvis Agent Stack product installed and wired. Customer gets a private instance of the full stack.
- **Remote management**: Tailscale-based remote operations. iJarvis operates the appliance; customer owns the hardware and data.
- **Air-gapped option**: For regulated deployments: air-gapped with periodic update bundles.

## Part of the iJarvis Agent Stack

Four products shipping in 2026. Eleven more on a three-year roadmap. One entity (iJarvis LLC). One SDK (`pip install iagent-stack`).

**Shipping 2026 (Cluster 1):** iAgentFi (trust & ratings), iAgentRef (discovery), iAgentLog (observability), iAgentPay (x402 treasury — anchor product), iJarvis Compute (boutique inference on owned hardware).

**Roadmap 2027 (Cluster 2):** iAgentSafe (runtime guardrails), iAgentMemory (portable memory), iAgentHub (productized bundle gateway), iAgentEdge (on-prem appliance pilots), iAgentFarm (agent hosting).

**Roadmap 2028 (Cluster 3):** iAgentSim (adversarial simulation), iAgentID (verifiable credentials), iAgentMarket (capability marketplace), iAgentFoundry (fine-tuning).

**Parked:** iAgentLaw (pending law-firm anchor partnership).

**Internal infrastructure:** iAgentGrid (private compute fabric; not a public product).

Cluster 1 endpoints serve live traffic in 2026. Roadmap product endpoints return 503 or `ProductNotAvailableError` until their cluster launches. Check each site's `.well-known/agent-card.json` `status` and `productAvailability.publicEndpointActive` fields for honest availability.

## Standards and protocols

ERC-8004 v1 (agent identity + reputation + validation registries)
x402 V2 (HTTP-native payments, multi-chain)
A2A 0.3.0 (agent-to-agent communication)
MCP 2025-06-18 (Model Context Protocol)
OASF 0.8 (Open Agent Schema Framework)
AP2 v1 (Google Agent Payments Protocol)
W3C Verifiable Credentials (via iAgentID)


## Endpoints

- **Agent card (ERC-8004):** https://iagentedge.com/.well-known/agent-card.json
- **MCP manifest:** https://iagentedge.com/.well-known/mcp.json
- **x402 discovery:** https://iagentedge.com/.well-known/x402.json
- **DID document:** https://iagentedge.com/.well-known/did.json
- **OpenAPI 3.1:** https://iagentedge.com/.well-known/openapi.yaml
- **Public API:** https://api.iagentedge.com/v1/
- **MCP server:** https://mcp.iagentedge.com/

## Contact

hello@iagentedge.com · iJarvis LLC · https://ijarvis.ai