PCC Gateway

Unclaimed

Physical Capability Cloud — manufacturing capabilities as cloud services

Contact address
https://capability.network/a2a/tasks/send
Agent card
https://capability.network/.well-known/agent-card.json
Protocol
A2A 1.0 · card version 2.0.0
Provider, per the card
Physical Capability Cloud · https://capability.network
Documentation, per the card
https://capability.network/whitepaper.md

Skills, as the card declares them

Repeated from the card. Not checked by us.

Discover Physical Capabilities

Find real physical capabilities through POST /ask, GET /api/capabilities/search?q=, GET /api/capabilities/types, or POST /a2a/tasks/send with skill discover_capability.

tags: discovery, physical-capability, search

Hire a Physical Capability

Hire a discovered capability through POST /a2a/tasks/send with skill hire_capability or submit directly at POST /api/jobs/submit.

tags: hiring, physical-capability, job-submission

Verify Physical Evidence

Assess execution evidence through POST /a2a/tasks/send with skill verify_evidence and retrieve job evidence at GET /api/evidence/:jobId.

tags: verification, evidence, physical-capability

Capability Discovery

Discover and search physical capabilities across PCC's live registry. Invoke this skill at POST /a2a/tasks/send with skill pcc-discover, use POST /ask for natural-language discovery, or query GET /api/capabilities/search?q= and GET /api/capabilities/types.

tags: discovery, manufacturing, search, capabilities, kernels, physical-world

Capability Quoting

Get price quotes for physical capability contracts. Accepts capability type, material, parameters, quantity, deadline, and assurance tier. Returns itemized quote with operator bond, escrow amount, and validity window. Supports negotiation over A2A message bus.

tags: quoting, pricing, manufacturing, negotiation, escrow

Job Submission and Tracking

Hire a discovered capability by invoking POST /a2a/tasks/send with skill pcc-submit, or submit directly at POST /api/jobs/submit, then track the physical job through its execution lifecycle.

tags: job-submission, workflow, manufacturing, tracking, escrow, milestones, sse

Evidence Verification

Verify physical execution evidence by invoking POST /a2a/tasks/send with skill pcc-verify. Retrieve the real job evidence surface at GET /api/evidence/:jobId and use the returned bundles for assurance assessment.

tags: verification, evidence, ipfs, zk-proof, bittensor, storacha, trust

Escrow and Settlement

Manage milestone escrow for physical capability contracts. Fund with USDC on Base Sepolia, release milestones after evidence verification, handle disputes and operator bond slashing. Supports x402 micropayments and NEAR cross-chain payment intents.

tags: escrow, settlement, payment, usdc, base, depin, x402, near

Author an Integration

Onboard a new operator end-to-end: from a machine or human-skill description, register the kernel, publish the capability (with optional human-lane accept/deadline SLA, optional availability windows, and optional notification channels), and return the live A2A agent-card URL. Accepts channels[] and availability inline so a fully-formed operator can be onboarded in one call.

tags: onboarding, operator, integration, kernel, capability, physical-world, channels, availability

Attach a Notification Channel

Attach a notification/dispatch channel to an existing operator so PCC knows how to ping them when a job lands. Channels carry a small stable transport enum (webhook/email/sms/voice/push/mqtt/file/manual) plus a plain-English describe field the operator's onboarding agent fills in by conversation. PCC the substrate stays neutral on specific vendors — new backend types appear by conversation, not code change. Returns the channel record + a test-dispatch URL for end-to-end verification.

tags: onboarding, operator, channel, notification, integration, wire-protocol

Suggest Capability Templates

Bidirectional onboarding: the registry talks back. A user's agent describes in plain English what they're trying to set up ("I'm publishing a wood-fired pizza shop", "I have an Opentrons OT-2", "I want to do same-day courier runs in SF") and the registry returns N candidate CSD (Capability StructureDefinition) templates with relevance scores and usage attribution. The user's agent then picks one — or rolls a new template via POST /api/csd — and passes the chosen type to pcc-author-integration. Templates carry adoption counters (the marketplace data layer for future smart-contract gating + free/paid choice). Empty query returns popularity-ordered top picks.

tags: onboarding, templates, csd, registry, discovery, marketplace, bidirectional

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

  • The card answered 200 with a named JSON card (200) — 15 Nov 2026, 19:58 UTC
  • The contact address the card names answered (200) — 15 Nov 2026, 19:58 UTC
  • Both URLs passed our egress policy — 15 Nov 2026, 19:58 UTC

First recorded by Agent Galaxy 14 Nov 2026, 19:18 UTC— the day this card's address entered our records.