Void Apps

Void Apps are services published by developers and made available to buyers through the marketplace. The Voidnet routes buyer requests to the publisher's server, handling authentication, rate limiting, metering, and billing. Your code only talks to the gateway.

App types

MCP — AI Tools (available)

Model Context Protocol servers expose callable tools, data resources, and prompt templates. AI clients discover and invoke these tools at runtime. Protocol version 2025-11-25.

An MCP server can expose:

Tools — callable functions with typed JSON input schemas.
Resources — URI-addressable data.
Prompts — reusable prompt templates.

MCP is the only app type available today.

A2A — AI Agents (not available)

Agent-to-Agent Protocol enables communication between autonomous AI agents. Protocol version 1.0. Not yet supported.

LLM — Language Model Integration (not available)

Connect and query language model providers through a unified interface. Not yet supported.

SLM — Specialized Language Models (not available)

Smaller, domain-tuned language models. Not yet supported.

How apps are consumed

POST /v1-beta/mcp/{username}/{appname}
Authorization: Bearer vnb-sk-...          # API key
Authorization: Bearer eyJhbGciOiJSUzI1... # JWT access token

Browse the Marketplace and purchase an app (free tiers require clicking "Get").
Note the publisher's username and the app's name.
Send JSON-RPC 2.0 requests through the gateway.

The gateway accepts both API keys and JWT access tokens and auto-detects the credential type.

How apps are published

Publishers register their app, choose its type (currently only MCP), and provide their server URL. The gateway stores the mapping between username/appname and the server. When a buyer makes a request, the gateway resolves the server URL, authenticates, validates the purchase, and proxies the request.

Publishers who want to build and list an app should read the Publisher Guide (MCP).