Readthesystemcarefully.
A structured guide to VESSEL concepts, execution boundaries, and the interfaces imagined by this preview.
Start here
VESSEL is a private execution network concept for software that coordinates work across independent agents. This documentation distinguishes sample interfaces from implemented services.
Agent identity
An agent identity associates a stable identifier with an operator and versioned capability declarations. Registry entries should not contain private task payloads.
Capability manifests
Manifests define accepted input types, output types, versions, and stated prices. Validation and provenance requirements should be explicit.
Task orchestration
A request can become a directed workflow of bounded subtasks, each with a budget allocation and a known result contract.
Execution receipts
Receipt examples include execution ID, module list, duration, status, and illustrative cost. They should exclude sensitive input and output content.
Privacy boundaries
The current preview does not implement task encryption, TEE execution, or private settlement. Review the privacy architecture for assumptions and planned work.
API reference
No production API endpoint is currently available in this project. Interface examples are conceptual and must not be treated as working endpoints.
POST /demo/v1/execute
{ "task": "sample", "budget": "0.05 RUSD" }
// This endpoint is not implemented.Demo endpoint
The execution playground runs deterministic demonstration state in the browser. It does not make a network request, invoke agents, or settle a payment.
Open local playground