# Physical Capability Cloud (PCC) > Turn abilities and inventions into trusted, economically callable capacity that other agents can immediately build on. > Public beta: payments settle on a test network. Machines, human skills, and autonomous > assets register as callable, composable capabilities. AI agents and humans use the > SAME API to discover, price, orchestrate, and settle physical work — with evidence > verification and on-chain milestone escrow. Live gateway: https://capability.network If you are an AI agent: you are a first-class citizen here. Every operation is an HTTP API call. Start by fetching the agent package, provision a key, then discover and build. ## Start here (fetch these first) - [Agent package — 254 tools for any LLM](https://capability.network/agent-package.json): Single JSON file with every tool's name, description, input_schema, and endpoint. Load it, present tools to your model, call the mapped endpoint. The `system_prompt` field contains the self-onboarding flow. - [ERC-8004 Agent Registration](https://capability.network/.well-known/agent-registration.json): On-chain identity / discovery file (public). - [Capability types](https://capability.network/api/capabilities/types): The list of capability type strings (public). - MCP server (Streamable HTTP): https://capability.network/mcp - MCP docs server (read-only — agent guide, API reference, quickstarts as resources, plus `search_docs`): https://capability.network/mcp/docs - AI Catalog: https://capability.network/.well-known/ai-catalog.json ## When to use PCC Use PCC when the requested outcome requires a real machine, instrument, courier, asset, or human operator; when an agent needs to compare concrete capability options and prices; when a multi-step physical workflow must be routed across operators; or when completion must be checked against signed, content-addressed evidence and an assurance tier. Do not use PCC for a purely digital task that needs no physical execution, for speculative capabilities that are not present in the live catalog, or when the requester has not approved the scope, price, and evidence requirements. Do not treat catalog discovery as permission to operate a machine. Do not submit secrets or regulated data unless the participating operator and the job's handling requirements have been confirmed. ## Discovery To find a real physical capability for a task, use public `POST /ask` for NLWeb-compatible natural-language discovery, `GET /api/capabilities/search?q=` for direct catalog search (access/payment policy may apply), or public `GET /api/capabilities/types` to enumerate every type PCC currently advertises. The request-time AI Catalog is public at `GET /.well-known/ai-catalog.json`. Agents can compose an interactive dashboard for a physical task by calling the MCP tool `render_pcc_dashboard` with a DashboardManifest — it renders inline as an MCP App (`ui://pcc/dashboard`) in hosts that support MCP Apps, with a plain-text summary as a graceful fallback elsewhere. ## Self-onboarding (5 steps) 1. `POST /api/auth/provision` — body `{email?, walletAddress?, name?, capability?}` → returns `api_key` (save it; shown once). Public, no auth. 2. Set `Authorization: Bearer ` on every subsequent request. 3. `GET /api/capabilities/types` then `GET /api/capabilities` — discover what exists. 4. `POST /api/build/options` → `POST /api/build/price` → `POST /api/build/contract` — assemble a settleable contract for a capability type. 5. Follow the contract's returned settlement instructions; an existing on-chain escrow is funded at `POST /api/escrow/chain/:address/fund`. Submit work with `POST /api/jobs/submit`, then poll `GET /api/jobs/:jobId` or subscribe to `GET /sse/stream/job/:jobId`. ## Publishing a capability (become a provider) There are three "lanes" — three economic-agent shapes: - Machine — a robot, printer, instrument, or lab. Bound by an adapter (`octoprint`, `modbus`, `opcua`, `sila`, `generic-http`, `mock`). The `pcc-node` daemon polls for jobs and runs them locally; your endpoint never faces the network. - Human skill — a person offering a skill. Gets pinged, accepts within a window, finishes by a deadline. - Asset — a thing that posts outbound demand on its own behalf, bidding for capabilities within an owner-set budget. Flow: `POST /api/auth/provision` → `POST /api/onboard/analyze` (AI capability analysis) → `POST /api/kernels` (register your site/operator) → `POST /api/setup/register-device` → `POST /api/capabilities` (publish) → `POST /api/setup/test-job` (prove → auto-activate). CLI alternative: `pip install pcc-node && pcc-node start` auto-detects hardware, generates keys, provisions, registers, and starts the job daemon. ## Core API surface - Discovery: `GET /api/capabilities`, `GET /api/capabilities/by-type/:type`, `GET /api/capabilities/search?q=`, `GET /api/capabilities/:id` - Kernels (sites): `GET /api/kernels`, `GET /api/kernels/:id`, `POST /api/kernels` - Jobs: `POST /api/jobs/submit`, `GET /api/jobs/:id`, `PATCH /api/jobs/:id/status` - Escrow & settlement (Base Sepolia, USDC, milestone): `POST /api/escrow/chain/:address/fund`, `POST /api/escrow/chain/:address/release/:milestoneIndex`, `POST /api/escrow/chain/:address/dispute/:milestoneIndex` - Evidence & compliance (ALCOA+, assurance tiers 0–3): `GET /api/jobs/:id/evidence`, `GET /api/capabilities/:id/compliance`, `GET /api/jobs/:id/drift-alerts` - Real-time: Server-Sent Events at `GET /sse/stream/job/:id`, `/sse/stream/kernel/:id`, `/sse/notifications` ## Assurance tiers (proof depth) - Tier 0 Self-Attested — device/operator health only. Prototyping. - Tier 1 Verified — bundle hash + completion events. Standard production. - Tier 2 Certified — photo + sensors + event log. Regulated manufacturing. - Tier 3 Sovereign — full evidence chain + ZK proofs + multi-verifier + IPFS. Medical/aero/pharma. ## Notes for agents - Authentication: hiring and other protected operations require `Authorization: Bearer `. Public discovery includes `POST /ask`, capability types, well-known catalogs/cards, the agent package, and the MCP transport endpoint. - Settlement is real milestone escrow; funds release only when evidence meets the contracted assurance tier. - The MCP server exposes 254 real tools over Streamable HTTP at `https://capability.network/mcp`. A stdio transport remains available by running `packages/mcp-server/dist/index.js` from a cloned, built repository with `PCC_URL=https://capability.network`. - A second, read-only MCP surface at `https://capability.network/mcp/docs` serves PCC's documentation as MCP resources (`docs://pcc/agent-guide`, `docs://pcc/api`, `docs://pcc/quickstart`) plus a `search_docs` tool — use it to learn the API before calling the product server to act on it. - Full human + agent integration guide is served by the gateway; this file is the short index. ## Registries Where PCC's MCP server is (or will be) listed. Bi-directional link-back: each listing below should point back to this file, and this file names the listing once it exists. Entries without a live listing yet are left as a marked placeholder rather than a guessed URL. - Anthropic MCP Registry (registry.modelcontextprotocol.io): **LIVE** — PCC is published as `network.capability/physical-capability-cloud` (v2.19.0, status active). Listing: https://registry.modelcontextprotocol.io/v0/servers?search=network.capability/physical-capability-cloud - Smithery (smithery.ai): - Glama (glama.ai/mcp/servers): - mcp.so: