An economic network of capabilities for humans and agents.
Juice terraforms the web we already have: any existing HTTP endpoint becomes an action that anyone can call, pay for, and compose into new ones.
Features
- Composable actions
- An action is typed and priced, and may call other actions within its budget. Its owner sells the result as one thing at one advertised price; the parties beneath are paid from it.
- Delegated execution
- Like running a process, but on the network: a funded computation is handed off, may call other actions, may pause for a named person or agent, and settles when they answer.
- Blockchain micropayments
- Between nodes, every call settles on Arbitrum One. An obligation too small to be worth its own transaction settles by a draw neither side can rig: a larger amount paid rarely, averaging out exact.
- A market of capabilities
- Public actions are found by natural-language search across every node, and called from your own balance — no account anywhere else. Each result carries its typed interface and one advertised price.
- Traceable trade
- Every call records who paid, who asked and who was paid, and leaves a signed receipt verifiable offline. A rating rides with that receipt and crosses nodes as evidence, never an opaque score.
- Runs anywhere
- One binary and one file. A node on a laptop behind a home router is a full member of the network: no public address, no port forwarding, nothing hosted.
- Bring your own LLM
- The node's language model is whichever you point it at, a local one by default. Search falls back to keywords without one, and nothing about money depends on which model you run.
- The web as it is
- An existing API joins by its OpenAPI document, one action per operation; an action is an HTTP endpoint; consent is OAuth. There is no new protocol to adopt.
Manuals
| Component | What it is | Manual |
|---|---|---|
| Juice kernel | Accounts, actions, execution, settlement, federation | Juice manual |
| Juice UI | Building and running Juice apps | coming soon |
| Juice rail | Money rail and on-chain settlement | coming soon |
| Juice agent | Agent-side integration | coming soon |
| Juice services | Services published on the network | coming soon |
Where to start
Start with Getting started to run a kernel and make a first call. Concepts explains actions, kernels, records and ratings. To publish and sell an action, read Providing actions.
Background
Juice implements the architecture described in the DAIOS vision paper, Web 4.0: A New Paradigm for a Composable, AI-Powered Internet.