EasyNet is a Capability Control Plane built on top of the Axon Agent Invocation Protocol.
It turns every agent ability into a first‑class, addressable, signed, auditable network object — and ships the reference instantiation across runtime, addressing, identity, and language SDKs.
EasyNet is a Capability Control Plane for AI agents. It treats every agent ability — quote.order, image.caption, a three‑day monitor, a one‑shot tool call — as a first‑class network object with its own identity, schema, trust posture, scheduling contract, and signed receipt.
Underneath, EasyNet stands on a precisely specified mechanism: the Axon Agent Invocation Protocol, which defines what an invocation is when one autonomous agent calls another agent's ability. Axon is anchored to a seven‑tuple axiom:
Invocation ≜
⟨caller, callee, ability, subject, nonce, causal_context, args⟩
Layer map:
| Layer | Role |
|---|---|
| EasyNet | Capability Control Plane (system abstraction) |
| Axon | Agent Invocation Protocol (mechanism) |
| URA | Capability Addressing |
| Nucleus | Identity & Trust |
| EAL | Mission / Workflow description |
| Receipt Chain | Execution Provenance |
In today's AI agent stack, "calling another agent" is a function call wrapped in an RPC wrapped in a tool wrapped in a workflow. There is no shared object that says this is the invocation, this is what was called, this is what was returned, this is who signed for it. Capability, policy, scheduling, and provenance are scattered across independent layers.
EasyNet treats invocation as the smallest closed unit of the agent network — and the capability control plane is what makes that unit a first‑class object. Every ability has a stable URI. Every invocation produces a signed receipt. Every receipt closes a graph the verifier can replay — across SDKs, languages, and bindings — because the underlying Axon protocol semantics are independent of the wire.
| Component | What it is | Where |
|---|---|---|
| EasyNet‑Spec | The umbrella — protocol spec, RFC index, roadmap, long-form README | 🌐 Public |
| URA | Unified Resource Addressing — canonical URI scheme for agents, abilities, invocations, receipts | 🌐 Public · 2026‑02 |
| EasyNet‑Nucleus | Identity core — agent genesis, lineage, capability registry | 🌐 Public · 2026‑02 |
| EasyNet‑Axon | Reference runtime for the invocation protocol — Rust control plane, profile‑bound signing, federation hub | 📦 SDKs public · 2026‑03 |
| easynet‑axon‑go | Go SDK module mirror | 🌐 Public · 2026‑03 |
| EasyRemote | The 2024 origin project — "Torchrun for the World", the seed that became EasyNet | 🌐 Public · 2024‑11 idea / 2024‑12 first release |
Reference SDKs are shipping on public registries since March 2026:
pip install easynet-run-axon # Python
npm install @easynet-run/node # Node.js
npm install @easynet-run/react # React
go get easynet.run/axon/sdk/go # GoJava (Maven Central), Swift (SPM), and Rust (workspace crate) are part of the same release train.
| Date | Milestone |
|---|---|
| 2024‑11 | EasyRemote / EasyNet idea inception |
| 2024‑12‑05 | EasyRemote repository created on GitHub |
| 2024‑12‑09 | easyremote first published to PyPI |
| 2024‑12‑11 | EasyRemote / EasyNet first publicly announced on LinkedIn |
| 2025‑05‑28 | EasyRemote GitHub organization founded |
| 2026‑02‑18 | EasyNet‑Axon initial commit — reference runtime begins |
| 2026‑02‑20 | EasyNet‑Nucleus public — identity core |
| 2026‑02‑22 | URA public — Unified Resource Addressing Spec |
| 2026‑03‑19 | First multi‑language SDK release on PyPI, npm, Go module proxy |
| 2026‑04‑26 | AXON‑RFC‑001 — 150/150 RPCs restated under the invocation axiom |
| 2026‑05‑29 | Public umbrella launch — this profile |
Every dated public milestone is independently verifiable through GitHub repository createdAt, PyPI/npm upload timestamps, the LinkedIn post timestamp, or the Go checksum database.
What is EasyNet? EasyNet is a Capability Control Plane for AI agents. It turns every agent ability into a first‑class network object — with its own identity, schema, trust posture, scheduling contract, and signed receipt — and ships the reference instantiation across runtime (Axon), addressing (URA), identity (Nucleus), mission language (EAL), and seven language SDKs.
What is Axon?
Axon is EasyNet's underlying mechanism: an Agent Invocation Protocol for Open‑World Agent Systems. Where EasyNet is the system abstraction users see (Capability Control Plane), Axon is the wire‑level protocol that makes the abstraction work — defining what an invocation is when one autonomous agent calls another's ability. Axon is anchored to a seven‑tuple axiom ⟨caller, callee, ability, subject, nonce, causal_context, args⟩ and proven against five structural invariants Q1–Q5 (see the AXIOM paper).
How does EasyNet compare to A2A and MCP? A2A (agent‑to‑agent) and MCP (Model Context Protocol) are wire bindings — they specify how messages are carried between agents and between agents and tools. The Axon protocol that EasyNet stands on is the invocation semantics one level above: it specifies what the message means (which caller, which callee, which ability, what subject, what arguments, what receipt). Axon's RFC track formalises A2A as one profile of the invocation axiom and MCP as another, so a receipt chain that crosses an A2A hop and an MCP tool call is closed by the same verifier.
What language SDKs does EasyNet support?
Python (easynet-run-axon on PyPI), Node.js (@easynet-run/node on npm), React (@easynet-run/react on npm), Go (easynet.run/axon/sdk/go via the Go module proxy), Java (Maven Central), Swift (SPM), and Rust. All SDKs share the same canonical wire — receipts produced by any SDK verify under any other.
When was EasyNet started? The EasyRemote / EasyNet idea was conceived in November 2024 and first publicly announced on LinkedIn on 2024‑12‑11. The Axon reference runtime began on 2026‑02‑18, the addressing spec (URA) and identity core (Nucleus) went public on 2026‑02‑22 and 2026‑02‑20 respectively, and the first multi‑language SDK release shipped on 2026‑03‑19.
Who maintains EasyNet? EasyNet is built by Silan Hu and contributors under the EasyRemote organization.
Is EasyNet open source? The specifications (URA, RFC drafts, AXIOM paper) and language SDKs are public under permissive licenses (Apache 2.0 for code, CC‑BY 4.0 for documents). The Axon reference runtime is private during stabilisation; SDKs that wrap it are public on PyPI, npm, the Go module proxy, Maven Central, and SPM.
What is URA?
URA — Unified Resource Addressing — is EasyNet's canonical URI scheme for naming agents, abilities, invocations, and receipts. An ability URI looks like easynet:///r/<scope>/<registry>/<agent>/abilities/<ability>@<version>?tenant_id=<tenant>. URA is published as a separate spec at github.com/EasyRemote/URA.
- EasyRemote/EasyNet-Spec — the long form: scope, axiom, RFC index, roadmap.
- EasyRemote/URA — the addressing spec.
Built by Silan Hu and contributors · easynet.run