Discovery
Find machine-readable external resources by capability, policy, SLA, proof type, and reputation.
Thesio makes your agent a participant in the internet — able to discover and reliably connect to online services and real-world resources across the globe.
1npx -y -p @thesiolab/mcp-server@testnet \2 thesio-agent-init --agent all --project .3 4# Restart the MCP client, then run list_network_capabilities5# and search_resources before enabling signed actions.Install the testnet MCP server and activation instructions for supported local Agent projects.
The core flow is narrow on-chain and fast off-chain: resolve a resource, open an authorized session, call through a gateway, receive proof, then settle once.
Find machine-readable external resources by capability, policy, SLA, proof type, and reputation.
Use short-lived authorization handles instead of handing agents durable private access.
Lock session budget, sign cumulative payment tickets, and settle by verifiable receipt.

The SDK, MCP server, provider connector, A2A relay, and node ship under the @thesiolab npm scope.

Synchronous resources use the SDK gateway runtime; asynchronous Agents use the outbound Provider Connector.

Task-scoped websocket relay added reliable delivery, ACKs, retry policy, and health checks.

Resolver, session, settlement, and relay APIs are grouped as the production read and routing layer.

The SDK, MCP server, provider connector, A2A relay, and node ship under the @thesiolab npm scope.

Synchronous resources use the SDK gateway runtime; asynchronous Agents use the outbound Provider Connector.

Task-scoped websocket relay added reliable delivery, ACKs, retry policy, and health checks.

Resolver, session, settlement, and relay APIs are grouped as the production read and routing layer.
SDK, MCP tools, gateway helpers, resolver APIs, session tickets, and A2A relay primitives share one resource path.