How inn-media/truyn works
TRUYN is a trust-aware peer network for agent discovery, requests, provider execution, and contextual data exchange. A user configures a node or provider through the CLI; the node client communicates with a relay, which supports discovery and dispatch, while a provider-side adapter host runs configured provider integrations. The repository also exposes A2A/MCP and NLWeb interoperability, semantic context, trust, and multi-language SDKs. Edges are limited to excerpted calls, SOURCE INDEX references, or README-documented capabilities; several large subsystems are represented by their exact directories because their implementation was not sampled.
Main entry points: client.js Node client · index.js CLI · server.js Relay and dispatch · runtime.js Network runtime
Components 23
Entry and APIs
- CLI
cli/index.js - Node client
node/client.js - HTTP API
adapters/http/server.js
Network runtime
- Relay and dispatch
network/relay/server.js - Network runtime
network/runtime.js - Peer discovery
network/discovery/peer-discovery.js - QUIC RPC
network/discovery/quic-rpc.js - P2P transport
network/transport/p2p.js - Persistent state
network/state/persistent-state.js
Trust and context
- Protocol envelopes
core/protocol/index.js - Node identity
core/identity/index.js - Trust services
core/trust/index.js - Semantic context
core/context/index.js - Semantic routing
core/context/semantic-router-v2.js
Provider execution
- Provider adapter host
adapters/sdk/index.js - Provider registry
adapters/providers/index.js - Provider integrations
adapters/providers
Interoperability and SDKs
- MCP server
adapters/mcp/server.js - A2A adapter
adapters/a2a/server.js - MCP clients
adapters/mcp - NLWeb interoperability
adapters/nlweb - Language SDKs
sdk
Other components
- User or operator
Connections 27
- User or operator → CLI: runs commands
- CLI → Node client: creates node
cli/index.js - CLI → Relay and dispatch: starts relay
cli/index.js - CLI → Provider registry: selects provider
cli/index.js - CLI → Provider adapter host: configures host
cli/index.js - CLI → HTTP API: starts API
cli/index.js - CLI → MCP server: starts MCP
cli/index.js - Node client → Protocol envelopes: signs and verifies
node/client.js - Node client → Node identity: creates identity
node/client.js - Node client → Relay and dispatch: sends requests
node/client.js - Node client → Semantic context: validates selections
node/client.js - HTTP API → Node client: routes discovery
adapters/http/server.js - MCP server → Node client: routes tool calls
adapters/mcp/server.js - Relay and dispatch → Protocol envelopes: verifies envelopes
network/relay/server.js - Relay and dispatch → Trust services: scores trust
network/relay/server.js - Relay and dispatch → Semantic context: retrieves context
network/relay/server.js - Network runtime → Peer discovery: loads discovery
network/runtime.js - Network runtime → QUIC RPC: loads RPC
network/runtime.js - Network runtime → P2P transport: loads transport
network/runtime.js - Network runtime → Persistent state: loads persistence
network/runtime.js - Provider adapter host → Provider registry: executes adapter
- Provider registry → Provider integrations: dispatches provider
adapters/providers/index.js - A2A adapter → MCP server: compatibility profile
- MCP clients → MCP server: connects to server
adapters/mcp/server.js - NLWeb interoperability → Node client: composes discovery and ask
- Semantic routing → Semantic context: uses context runtime
core/context/semantic-router-v2.js - Language SDKs → Node client: offers client access