io.net
io.net is a decentralized GPU network for AI compute, built on Solana, that aggregates idle consumer and data-center GPUs (NVIDIA A100, H100, H200, and Blackwell-class) into on-demand, geo-distributed compute clusters orchestrated with the Ray framework. The platform exposes a Web3-native alternative to hyperscaler GPU cloud through several developer-facing surfaces: IO Intelligence (an OpenAI-compatible inference API for 15+ open-source models including Llama 3.3 70B), IO Cloud (Container-as-a-Service and VM-as-a-Service APIs for deploying GPU containers, Ray clusters, Kubernetes clusters, and bare-metal instances), IO Agents (agent and agentic-workflow APIs), IO Explorer (a network analytics API for devices, clusters, and block rewards), IO Worker (the supplier-side onboarding stack), IO ID (the account/wallet hub), and IO Staking. Confidential Compute on Intel TDX-enabled H100/H200/B200 GPUs and a remote attestation service for Intel TDX and NVIDIA H200 confidential VMs round out the security surface. The IO token is an SPL token on Solana used for settlement, staking, and rewards; fiat and USDC payments are accepted and converted to IO. io.net also publishes an MCP server at mcp.io.solutions for agent-driven cluster provisioning. The platform's tagline is "the open-source AI infrastructure platform" and its commercial pitch is AI compute at 50–70% below comparable hyperscaler rates.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles io.net the way a machine reads it — 26 machine-readable artifacts across 8 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — io.net scores 22.4/100 (emerging), with a separate agent-readiness read of 10/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile io.net
Each block below is one kind of artifact we hold for io.net. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 8
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
IO Intelligence API
OpenAI-compatible inference API for open-source AI models hosted on io.net's decentralized GPU network. Exposes /v1/models and /v1/chat/completions over the base URL https://api...
IO Agents API
REST API for discovering, configuring, and running AI agents and agentic workflows on io.net's no-code workflow editor. Supports agent discovery, workflow execution, workflow-sc...
IO Cloud Container-as-a-Service API
Container-as-a-Service REST API for deploying GPU-backed containers across io.net's decentralized network. Operations include container deployment and termination, real-time log...
IO Cloud VM-as-a-Service API
VM-as-a-Service REST API for provisioning, extending, and terminating GPU virtual machines on io.net. Surfaces hardware availability and pricing, supports multi-VM cluster orche...
IO Explorer API
Network analytics API exposing device summaries and detailed metrics, block-reward analysis, proof-of-work challenge tracking, and device notifications. Powers the public IO Exp...
IO Sub-API Key Management API
Administrative API for creating scoped sub-API keys with per-model restrictions and per-key credit limits, tracking usage and aggregated spend, and revoking keys. Designed for t...
IO Cloud MCP Server
Hosted Model Context Protocol server at https://mcp.io.solutions/mcp that exposes IO Cloud provisioning and management tools to MCP-aware agents (Claude Desktop, Claude Code, Cu...
Confidential Compute Attestation Agent API
Open-source FastAPI remote attestation service for Intel TDX and NVIDIA H200 confidential VMs operating on the io.net network. Issues verifiable cryptographic attestations that ...
Scroll within the panel for all 8 ·
Features 17
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 17 ·
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for io.net — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Build 6
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 5
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/io-net · machine-readable index on apis.io