OpenAgenet / OAN White Paper: Open Infrastructure for Trusted Agent Interconnection
arXiv:2606. 03161v3 Announce Type: replace-cross Abstract: OpenAgenet, abbreviated as OAN, is an open infrastructure project for trusted Agent interconnection.
arXiv:2606. 03161v1 Announce Type: cross Abstract: OpenAgenet, abbreviated as OAN, is an open infrastructure project for trusted Agent interconnection.
arXiv:2606. 03161v3 Announce Type: replace-cross Abstract: OpenAgenet, abbreviated as OAN, is an open infrastructure project for trusted Agent interconnection.
arXiv:2606. 03163v1 Announce Type: cross Abstract: This paper describes the technical architecture of OpenAgenet / OAN.
arXiv:2606. 03163v3 Announce Type: replace-cross Abstract: This yellow paper describes the technical architecture of OpenAgenet / OAN.
The paper proposes a scalable trust discovery architecture for the Internet of Agents, featuring a three‑layer hierarchical design: Agent Root for registry governance, Agent Registry for registration and metadata, and Agent Resolver for capability discovery. It introduces a registry‑suffix‑anchored composite identity scheme and a dual‑certificate, multi‑level authentication mechanism to strengthen agent identity trust. Prototype evaluation shows low latency (58 ms registration, 25 ms discovery) and high throughput (over 19,000 registrations and 29,000 discoveries per second).
arXiv:2606. 15822v1 Announce Type: new Abstract: AI agents increasingly access external models, tools, and services through Agentic Routing Infrastructure (ARI) to manage the overhead of heterogeneous interfaces and fragmented subscriptions.
arXiv:2609.22944v1 Announce Type: cross Abstract: Autonomous AI agents increasingly act across organizational boundaries on behalf of human operators: they invoke third-party services, delegate subta...
arXiv:2605. 27488v2 Announce Type: replace-cross Abstract: Agentic systems increasingly run user-authored orchestration code that invokes tools, spawns subtasks, and delegates work across machines and clouds.
The paper introduces a blockchain-backed agentic security framework that protects the entire software development lifecycle and the AI components monitoring it. It coordinates specialized security agents—covering source integrity, dependency and SBOM analysis, CI configuration auditing, artifact verification, and runtime policy evaluation—each powered by a large language model that interprets artifacts, reasons over tool outputs, and generates structured security reports. Every agent produces a cryptographically signed attestation recorded on a permissioned blockchain via smart contracts, creating an immutable attestation log, an agent registry, and an enforceable release‑policy module, while communication is secured through a consortium‑operated certificate authority.
The paper introduces Fetch.ai, an industrial-strength architecture that blends classical multi-agent system principles with modern AI capabilities. It features a decentralized foundation of on-chain blockchain services for identity, discovery, and transactions, a development framework for secure, interoperable agents, a cloud-based deployment platform, and an agent-native LLM that translates human goals into multi-agent workflows. A decentralized logistics use case demonstrates autonomous agents dynamically discovering, negotiating, and transacting securely.
OpenAI introduces Trusted Access for Cyber, a trust-based framework that expands access to frontier cyber capabilities while strengthening safeguards against misuse.
AI agents increasingly act through external tools: they read private data, construct structured payloads, submit write requests, export records, and coordinate workflows across application boundaries. Existing authorization mechanisms usually ask whether an integration credential, app, or token can call a tool.
arXiv:2608. 10760v1 Announce Type: cross Abstract: The Model Context Protocol (MCP) has become the de-facto interface for connecting LLM agents to enterprise tools, and adoption has been explosive: within a year, large organizations went from zero to dozens of internally built MCP servers.