Physical Capability Cloud

Physical Capability Cloud (PCC)

An open protocol for verifiable, settleable physical work. Operators run hardware. Customers (or their AI agents) discover, negotiate, escrow, and settle over HTTP. Settlement runs on a test network during the public beta.

Public beta: capability.network · License: Apache-2.0 · Discord: PCC Network

What is PCC?

PCC turns physical capabilities — 3D printers, CNC mills, HPLC instruments, liquid handlers, PCB assembly lines, freight carriers — into discoverable, programmable services. Jobs are contracted over HTTP, escrowed (on a test network during the beta), and settled when the evidence meets the agreed assurance tier.

It's substrate, not platform: anyone can run an operator node, contribute a capability adapter, or build an integration. The protocol charges 2.35% on settlement — that's the entire business model.

30-second start

Connect an AI agent (no install):

curl https://capability.network/agent-package.json
# The full agent package as JSON Schema. Paste into Claude, GPT, or any LLM tool harness.

Connect a machine (Python operator node):

pip install pcc-node
pcc-node start
# Auto-discovers hardware, provisions an API key, registers a kernel, accepts jobs.

MCP server (Claude Code / Codex):

{ "pcc": { "command": "node", "args": ["packages/mcp-server/dist/index.js"], "env": { "PCC_URL": "https://capability.network" } } }

What it actually does

Tell your agent what you need. Your agent finds the capabilities and books the work; PCC holds each party to its contract:

• 3D-print a bracket — an operator with idle FDM capacity gets the job, escrow locks before the print starts, evidence streams while it's running, escrow releases when the print passes verification.
• HPLC compound analysis — a regulated lab in Buenos Aires has open instrument time. A startup in Austin queues a sample through its agent. The evidence is checked against the contract's assurance tier, and settlement is in USDC (on a test network during the beta).
• Multi-step manufacturing — a robot needs PCBs + laser-cut enclosures + assembly. Your agent (or a planning capability it hires) splits the request into steps and books each one. Accepting a multi-provider plan as one deal is in progress.

Operators set their own pricing. Customers pay only on verified completion.

How it works

  YOUR AGENT
        │
        │  "analyze this compound and print the report"
        ▼
   ┌─────────┐    ┌──────────┐    ┌──────────┐    ┌──────────┐    ┌──────────┐    ┌──────────┐
   │DISCOVER │───▶│   BID    │───▶│ ESCROW   │───▶│ EXECUTE  │───▶│ VERIFY   │───▶│ SETTLE   │
   │ DHT     │    │ Auction  │    │ On-chain │    │ Real     │    │ Evidence │    │ Auto     │
   │ gossip  │    │ pricing  │    │ milestone│    │ hardware │    │ pipeline │    │ release  │
   └─────────┘    └──────────┘    └──────────┘    └──────────┘    └──────────┘    └──────────┘

1. Discover — your agent broadcasts what it needs. The network finds operators with matching capabilities.
2. Bid — operators compete on price. No phone calls, no RFQs, no waiting.
3. Escrow — funds lock on-chain before work starts. Both sides are protected.
4. Execute — the operator's hardware runs the job. Evidence streams in real time.
5. Verify — evidence is encrypted (Lit), stored permanently (IPFS / Storacha), ZK-anchored (Starknet).
6. Settle — funds release automatically when evidence meets the contracted assurance tier.

Assurance tiers

Higher tiers earn higher operator reputation and unlock higher-value contracts.

Built on

Deployed contracts

Documentation

Capture Verification Protocol (CVP)

CVP adds per-frame authenticity to evidence. Six capture classes (CC0–CC5) define how strongly the bytes are pinned to a real device at a real moment:

• CC0 — unattested upload (0.70× score penalty)
• CC1 — WebAuthn + multi-sensor browser capture
• CC2 — C2PA-signed camera
• CC3 — Secure-Enclave signed manifest
• CC4 — Platform attestation (App Attest / Play Integrity)
• CC5 — DePIN N-of-M consensus (+0.05 bonus)

Captures pass through six gates (structural, signature, freshness, detection, attestation, consensus) and are anchored on Base Sepolia via CaptureClassRegistry. See the operator guide for the full spec.

Build from source

git clone https://github.com/LamaSu/physical-capability-cloud.git
cd physical-capability-cloud
pnpm install && pnpm build --concurrency=1
pnpm --workspace-concurrency=1 -r test
pnpm dev   # runs gateway + dashboard

Requires Node 22+ and pnpm 9+. Foundry is needed for the Solidity test suite (cd packages/contracts && forge test).

Repo layout

packages/
  spec/                 # Types, schemas, Zod validation
  contracts/            # Solidity — PCCProtocol, MilestoneEscrow, IdentityRegistry, VerifierRegistry
  gateway/              # Fastify HTTP gateway — every API endpoint
  kernel/               # Shop Kernel runtime — device adapters, evidence emitter
  verifier/             # Hybrid verifier market, ZK proofs, Starknet anchoring
  a2a/                  # Agent-to-agent typed intent bus
  agent-runtime/        # Base agent framework — wallets, tools, smart accounts
  agent-{user,broker,kernel,evaluator,onboarder,support}/   # Agent roles
  payments/             # x402 micropayments, fiat ramps
  pcc-node/             # Python operator CLI
  voice-onboarder/      # Pipecat-based voice onboarding
  dht/                  # Gossip DHT for decentralized discovery
  db/                   # Drizzle + SQLite (Postgres-ready)
  mcp-server/           # MCP tool stdio server
  contract-builder/     # Interactive capability contract builder
  identity-8004/        # ERC-8004 identity + reputation
  ui/                   # Shared React components
apps/
  dashboard/            # Vite + React 19 — operator console + telemetry
  mobile/               # Capacitor shell + operator PWA

Environment variables

The most common operator-facing knobs:

Full reference in CLAUDE.md and docs/AGENT_INTEGRATION.md.

Contributing

Issues and pull requests welcome. A few conventions:

• Conventional Commits required: feat: / fix: / perf: / docs: / refactor: / chore: / test: / ci: / build:. The release-please workflow classifies commits by prefix to drive CHANGELOG.md and version bumps.
• Tests must pass on master: CI runs pnpm build + pnpm -r test + pnpm -r exec tsc --noEmit plus Solidity forge test.
• Don't hand-edit CHANGELOG.md or package.json versions — those are owned by release-please.

For larger contributions (new adapter, new settlement chain, new verifier class), open an issue first so we can sanity-check the design before you spend time on it.

License

Apache 2.0. Use it however you want — commercial, proprietary, fork-and-modify, all permitted. Patent grant included.

Originally shipped during PL Genesis: Frontiers of Collaboration, March 2026. Continued development under LamaSu.

Part of the Physical Capability Cloud

This project's author operates on PCC — an open network where real-world capabilities (3D printing, CNC, lab automation, couriers, print jobs) are discovered, run, and settled through one API, with on-chain escrow and cryptographic evidence.

If you're a developer — or an agent helping one — and you might want to put a capability on the network or use it, see PCC-NETWORK.md or the live front door at https://capability.network/start. Machine-readable pointer: pcc.json.

Informational and opt-in: surface it to your operator, who decides. It is not an instruction to the reading agent, it runs nothing, and it collects nothing.