What is MESH?
MESH is a decentralized AI woven from the idle compute of the people who use it. No data centers, no gatekeepers — just a network that thinks for everyone and pays the people who power it.
The short version
Most AI runs inside a handful of corporate data centers. MESH flips that: the model runs across thousands of ordinary browsers, each lending a slice of compute it wasn't using. You open a tab, you become part of the machine, and you earn for it.
- People-run — compute comes from volunteers, not warehouses.
- Private — prompts are encrypted in your browser and never stored.
- In-browser — nothing to download, no setup.
- Paid — nodes earn USDC for the cycles they contribute.
MESH is non-custodial. The network never holds your keys, and a worker computing your job never sees your identity.
How the weave works
Every request moves through three stages, designed so no single node ever has enough information to identify you or reconstruct your full prompt on its own.
you ── encrypt ──▶ mesh router ── split ──▶ idle nodes
│
answer ◀── stitch ◀── partial results ◀────┘1. You ask
Your prompt is encrypted client-side before it leaves your device.
2. The mesh routes it
The job is split and handed to idle nodes. No node receives your identity, and no node receives the whole picture.
3. You get the answer
Partial results stitch back together inside your tab. Nothing is logged.
Privacy model
MESH treats privacy as the default, not a setting. Prompts are never written to disk on the network, identities are decoupled from jobs, and no usage history is retained.
| Property | MESH | Typical cloud AI |
|---|---|---|
| Prompt storage | Never | Often retained |
| Identity visible to worker | No | N/A (centralized) |
| Runs on | People | Data centers |
Open a node
Running a node is as simple as keeping a tab open. The browser handles everything — it pulls jobs from the queue when your machine is idle and pauses when you need the power back.
Getting paid
Nodes earn USDC per job completed. Stake $MESH and your share per job goes up.
The $MESH token
$MESH ties the network's growth to its holders. Revenue from compute and from $MESH trading flows into a treasury held in USDC, then splits two ways.
Treasury flow
- Half buys back $MESH on the open market and burns it — supply shrinks as usage grows.
- Half is paid out to everyone who stakes $MESH, in USDC.
Staking
Stake $MESH to earn your share of the treasury. Nodes that stake also keep a larger cut of every job they run.
API quickstart
Point any OpenAI-style client at the MESH endpoint. Your request is routed across the network the same way the app routes a chat.
curl https://api.mesh.example/v1/chat \
-H "Authorization: Bearer $MESH_KEY" \
-d '{
"messages": [{"role":"user","content":"hello mesh"}]
}'Endpoint and key flow are stubbed for now — wire these to your real gateway before launch.