Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Physical Capability Cloud is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
256
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Discover, hire, and verify real-world physical capability through MCP.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http physical-capability-cloud-mcp https://capability.network/mcp
# 2 — ask your agent for something these tools do
# provision_api_key, list_api_keys, revoke_api_key and 253 more
Physical Capability Cloud costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CAAll 1 server
capability1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http physical-capability-cloud-mcp https://capability.network/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
256 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
CALL THIS FIRST. Provisions an API key for the operator. Returns a pcc_live_* key that must be included as 'Authorization: Bearer <key>' on all subsequent requests. Accepts either email OR walletAddress. The key is shown once — save it. Without it, all other endpoints return 401.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | no | Operator email address (use this OR walletAddress) | |
| walletAddress | string | no | EVM wallet address (use this OR email) |
| name | string | no | Operator display name (optional) |
| capability | string | no | What the operator does — e.g. 'FDM 3D printing', 'CNC milling', 'HPLC analysis' |
List all active API keys for the authenticated operator. Returns key IDs, prefixes, scopes, rate limits, usage counts, and creation/expiry timestamps. Requires a valid API key or SIWE session.
No parameter schema on file.
Revoke an API key permanently. The key will immediately stop working. You must own the key. Use list_api_keys to find the key ID.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyId | string | yes | Key ID to revoke (from list_api_keys) |
Auto-detect current setup state: env vars, database, adapters, chain connectivity, storage, identity. Use this to see what's configured and what's missing before onboarding.
No parameter schema on file.
Generate a KERNEL_CONFIG JSON from device descriptions. Tell it what machines you have and it produces the config ready to paste into your environment.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| devices | array | yes | Array of device descriptions with type, model, and connection info |
Validate a kernel config (20+ checks: JSON structure, device connectivity, adapter compatibility). Returns validation errors and warnings.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| config | object | yes | Kernel config JSON to validate |
Register a device in the database with adapter config and capabilities. Part of Step 3 in the onboarding flow. Required: kernelId, deviceId, type and adapterType (400 missing_required_fields otherwise).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelId | string | yes | Kernel ID to register the device under |
| deviceId | string | yes | Your ID for this device, unique within the kernel |
| type | string | yes | Device role: machine, sensor or camera (the values setup_generate_config and setup_validate accept) |
| model | string | no | Device model identifier (optional; stored as "unknown" if absent) |
| adapterType | string | yes | One of octoprint, modbus, opcua, sila, ipp, generic-http or mock; the route refuses anything else (including opentrons) |
| adapterConfig | object | no | Adapter-specific configuration (host, port, auth, etc.) |
| capabilities | array | no | Capability types this device serves |
Submit a test job to verify the full pipeline works end-to-end (Step 4 of onboarding). Returns job ID and result.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelId | string | yes | Kernel ID to test |
| deviceId | string | no | Specific device ID to test (optional) |
Comprehensive setup status across 6 categories: gateway, database, adapters, chain, storage, identity. Use to confirm everything is green before going live.
No parameter schema on file.
List all capability types registered on the network (FDM, SLA, CNC, HPLC, etc.) with metadata.
No parameter schema on file.
Search capability templates by type or keyword. Returns templates with pricing, assurance tiers, and availability.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search query (type name, material, process, etc.) |
Get configuration options for a capability type (materials, dimensions, tolerances, assurance tiers). Use before calling calculate_price.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | Capability type (e.g. fdm, cnc-3axis, hplc) |
| selections | object | no | Current selections to refine available options |
| profileId | string | no | Optional capability profile ID |
Calculate price for a capability configuration. Returns base price, tier premiums, and estimated total cost.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | Capability type |
| selections | object | yes | Configuration selections (material, dimensions, quantity, etc.) |
| profileId | string | no | Optional capability profile ID |
Build and submit a capability contract with on-chain milestone escrow. Returns job ID and escrow address.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | Capability type |
| selections | object | yes | Configuration selections |
| assuranceTier | number | yes | Assurance tier 0-3 (0=self-reported, 3=ZK-proven+bonds) |
| profileId | string | no | Optional capability profile ID |
List all Shop Kernels on the network with status and capability types. Optionally filter by status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Filter by kernel status (online, offline, maintenance) |
Get kernel details including full capability objects, devices, and queue.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelId | string | yes | Kernel ID |
List all devices registered under a specific kernel, including adapter configs and device types.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelId | string | yes | Kernel ID |
List all jobs submitted to a specific kernel, including job status and progress.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelId | string | yes | Kernel ID |
Register a new Shop Kernel (physical site) on the PCC network. Part of Step 2 in the onboarding flow.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Kernel/site name (e.g. 'BioPunk Lab - Bay A') |
| description | string | no | Description of the site and its capabilities |
| location | object | no | Location object with address and geo coordinates |
| config | object | no | Kernel configuration JSON |
List all jobs with status. Optionally filter by kernelId or status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelId | string | no | Filter by kernel ID |
| status | string | no | Filter by status (pending, queued, in_progress, paused, completed, failed, cancelled) |
Get job details including progress, evidence bundles, and milestones.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | yes | Job ID |
Update a job's status and optional progress percentage. Used by kernels to report job progress.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | yes | Job ID |
| status | string | yes | New status (pending, queued, in_progress, paused, completed, failed, cancelled). 'running' is accepted as a legacy alias for in_progress. |
| progress | number | no | Progress percentage 0-100 (optional) |
List escrow contracts with milestones and bonds. Optionally filter by status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Filter by escrow status |
Get escrow details. Pass a DB ID for database record (with milestones and disputes), or an EVM address (0x...) to read directly from the blockchain.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| escrowId | string | yes | DB escrow ID or on-chain contract address (0x...) |
Read full on-chain escrow state with all milestone details from the blockchain. More detailed than get_escrow for on-chain contracts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | On-chain escrow contract address (0x...) |
Get on-chain event history for an escrow contract. Returns funding, release, dispute, and bond events.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | On-chain escrow contract address (0x...) |
| fromBlock | string | no | Starting block number (optional) |
Read an ERC-20 token balance for an account address from the blockchain.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tokenAddress | string | yes | ERC-20 token contract address (0x...) |
| account | string | yes | Account address to check balance for (0x...) |
Read the ERC-20 token allowance granted by an owner to a spender from the blockchain.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tokenAddress | string | yes | ERC-20 token contract address (0x...) |
| owner | string | yes | Token owner address (0x...) |
| spender | string | yes | Spender address (0x...) |
Read dispute state for a specific milestone from the blockchain.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Escrow contract address (0x...) |
| milestoneIndex | number | yes | Milestone index (0-based) |
Check if on-chain write operations are enabled (requires PCC_GATEWAY_PRIVATE_KEY to be configured). Returns write status and signer address.
No parameter schema on file.
Fund a protocol-created escrow on-chain. Approval is handled INTERNALLY by the gateway for protocol-created escrows (audit C-03 removed the public approve step) — do NOT call a separate approve first; fund directly. Returns transaction hash.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Escrow contract address (0x...) |
Release a milestone payment on-chain after the challenge window has expired. Returns transaction hash.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Escrow contract address (0x...) |
| milestoneIndex | number | yes | Milestone index to release (0-based) |
File a dispute against a milestone on-chain. Challenger must post a bond and provide evidence hash. Returns transaction hash.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Escrow contract address (0x...) |
| milestoneIndex | number | yes | Milestone index to dispute (0-based) |
| challengerBond | string | yes | Bond amount in wei (as string) |
| challengerEvidenceHash | string | yes | Evidence hash as 0x-prefixed hex bytes32 |
| reason | string | yes | Human-readable dispute reason |
Deposit an operator bond for a milestone on-chain. Required for Assurance Tier 3 jobs. Returns transaction hash.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Escrow contract address (0x...) |
| milestoneIndex | number | yes | Milestone index to post bond for (0-based) |
Submit an evidence bundle hash for a milestone on-chain. Links the physical evidence to the on-chain settlement record. Returns transaction hash.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Escrow contract address (0x...) |
| milestoneIndex | number | yes | Milestone index (0-based) |
| evidenceBundleHash | string | yes | Evidence bundle hash as 0x-prefixed hex bytes32 |
Submit a verifier attestation for a milestone on-chain. Used by third-party verifiers (Bittensor subnet) to confirm evidence quality. Returns transaction hash.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Escrow contract address (0x...) |
| milestoneIndex | number | yes | Milestone index (0-based) |
| attestationHash | string | yes | Attestation hash as 0x-prefixed hex bytes32 |
Archive an evidence bundle to IPFS/Storacha for permanent decentralized storage. Returns the content-addressed CID.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bundle | object | yes | Evidence bundle object to archive |
Get an encrypted evidence bundle by its bundle ID. Returns the encrypted payload and key capsules.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bundleId | string | yes | Evidence bundle ID |
Grant a new recipient access to an encrypted evidence bundle. Creates a re-encrypted key capsule for the recipient.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bundleId | string | yes | Evidence bundle ID |
| recipientAddress | string | yes | Recipient EVM address (0x...) |
| accessLevel | string | no | Level of access to grant (default: full) |
List all evidence access grants for an address. Returns bundles the address has been granted access to.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | EVM address to look up grants for (0x...) |
Archive an encrypted evidence bundle to IPFS and store the resulting CID in the database. Idempotent — returns existing CID if already archived.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bundleId | string | yes | Encrypted evidence bundle ID |
Get IPFS CIDs for a bundle — returns the primary CID, metadata CID, and Filecoin deal ID if available.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bundleId | string | yes | Evidence bundle ID |
Retrieve raw data from IPFS by CID. Used to fetch archived evidence bundles from decentralized storage.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cid | string | yes | IPFS content identifier (CID) |
Get Lit Protocol access conditions for a Lit-encrypted evidence bundle. Returns the conditions that gate decryption.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bundleId | string | yes | Evidence bundle ID (must be Lit-encrypted) |
Decrypt a Lit Protocol-encrypted evidence bundle using a Lit auth signature. Returns the decrypted bundle payload.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bundleId | string | yes | Evidence bundle ID (must be Lit-encrypted) |
| authSig | object | yes | Lit auth signature object with sig, derivedVia, signedMessage, and address fields |
Verify a ZK proof by its proof ID. Checks the proof against its verification key and public inputs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| proofId | string | yes | ID of the ZK proof to verify |
Create a Merkle commitment for an evidence bundle hash. Used as the first step in ZK proof generation for Tier 3 assurance.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bundleHash | string | yes | SHA-256 hash of the evidence bundle |
Get aggregate pipeline telemetry statistics including phase timings, success rates, and throughput metrics across all jobs.
No parameter schema on file.
List currently active jobs with their current pipeline phase and telemetry status.
No parameter schema on file.
Get full event timeline for a specific job — all pipeline phase transitions with timings and metadata.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | yes | Job ID to get pipeline timeline for |
Query structured logs with filters for level, source, jobId, kernelId, time range, and full-text search.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| level | string | no | Filter by log level |
| source | string | no | Filter by source module |
| jobId | string | no | Filter by job ID |
| kernelId | string | no | Filter by kernel ID |
| search | string | no | Full-text search query |
| after | string | no | Return logs after this ISO timestamp |
| before | string | no | Return logs before this ISO timestamp |
| limit | number | no | Max entries to return (default 200) |
Manually emit a telemetry event for a job pipeline phase. Used by kernels and agents to report execution progress.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | yes | Job ID |
| phase | string | yes | Pipeline phase name (e.g. intake, binding, execution, evidence, settlement) |
| status | string | yes | Phase status |
| duration_ms | number | no | Phase duration in milliseconds |
| level | string | no | Log level for this event |
| source | string | no | Source module or component |
| metadata | object | no | Additional event metadata |
Submit an evidence bundle for human verification. Selects a panel of verifiers from the network and returns assigned verifier IDs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bundleHash | string | yes | SHA-256 hash of the evidence bundle |
| photoRef | string | yes | Reference to the photo evidence (CID or URL) |
| referenceRef | string | yes | Reference to the reference/spec document |
| comparisonScore | number | no | Pre-computed comparison score 0-1 (optional) |
| verifierCount | number | no | Number of verifiers to assign (default 5) |
Get pending verification assignments for a verifier node. Returns requests this verifier has been assigned but not yet responded to.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| verifierId | string | yes | Verifier node ID |
Get verification status for a request. Returns vote tally, consensus state, dispute list, and pending response count.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| requestId | string | yes | Verification request ID (hvreq_...) |
Submit a verifier's verdict for a verification request. Returns consensus state after this vote.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| requestId | string | yes | Verification request ID (hvreq_...) |
| verifierId | string | yes | Verifier node ID |
| verdict | string | yes | Verifier's verdict |
| notes | string | no | Optional notes explaining the verdict |
| signature | string | yes | Cryptographic signature of the verdict |
File a dispute against the consensus verdict. Only verifiers who submitted a response can dispute. Requires additional evidence CID.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| requestId | string | yes | Verification request ID (hvreq_...) |
| disputerId | string | yes | Verifier node ID filing the dispute |
| reason | string | yes | Reason for disputing the consensus |
| evidenceCid | string | yes | IPFS CID of the counter-evidence |
Register a capability as a Story Protocol IP Asset. Returns an ipId and NFT token. The designer earns royalties whenever this capability is used.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| capability | object | yes | Capability object |
| designerAddress | string | yes | EVM address of the capability designer |
| designerName | string | yes | Display name of the designer |
| commercialRevShare | number | no | Revenue share percentage for commercial use (0-100) |
| ipfsCid | string | no | IPFS CID of the capability spec document (optional) |
Register job evidence as a derivative IP asset on Story Protocol, linking it to the parent capability's IP. Operators earn royalties from derivative use.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| parentIpId | string | yes | IP ID of the parent capability |
| jobId | string | yes | Job ID whose evidence is being registered |
| evidenceBundleHash | string | yes | Hash of the evidence bundle |
| operatorAddress | string | yes | EVM address of the operator |
| operatorName | string | yes | Display name of the operator |
| ipfsCid | string | no | IPFS CID of the evidence bundle (optional) |
Set revenue splits for an IP asset among stakeholders (designer, operator, verifier, assembler, curator). Splits must sum to 100.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ipId | string | yes | IP asset ID |
| splits | array | yes | Revenue splits — must sum to 100 |
Pay royalties to an IP asset vault. The payer sends tokens that flow to stakeholders via the royalty splits.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ipId | string | yes | IP asset ID |
| amount | string | yes | Amount to pay in wei (as string) |
| payerAddress | string | yes | EVM address of the payer |
Claim earned revenue from an IP asset vault. Returns the claimed amount and transaction hash.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ipId | string | yes | IP asset ID |
| tokenIds | array | no | Specific royalty token IDs to claim (optional — claims all if omitted) |
Get a revenue snapshot for an IP asset — total earned, pending claims, and recent payments.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ipId | string | yes | IP asset ID |
Get the full IP lineage chain for an asset — parent capabilities and all derivative job registrations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ipId | string | yes | IP asset ID |
Get the Story Protocol IP registration for a capability by its capability ID.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| capabilityId | string | yes | Capability ID to look up IP registration for |
Raise a Story Protocol IP dispute against an asset. Provide evidence hash and reason.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ipId | string | yes | IP asset ID to dispute |
| evidenceHash | string | yes | Hash of the dispute evidence |
| reason | string | yes | Reason for the dispute |
List protocol templates in the library. Filter by tags, required capabilities, search query, or status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tags | string | no | Comma-separated tag filter (e.g. 'biotech,protein') |
| capabilities | string | no | Comma-separated required capability filter (e.g. 'hplc,centrifuge') |
| search | string | no | Full-text search query |
| status | string | no | Filter by template status |
Get protocol template details by ID. Returns steps, transfers, parameters, and metadata.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Protocol template ID |
Create a new protocol template draft. Returns the new template ID.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Protocol name |
| description | string | no | Protocol description |
| steps | array | no | Array of protocol step objects |
| transfers | array | no | Array of transfer objects between steps |
| parameters | array | no | Array of parameter definitions |
| tags | array | no | Tags for discovery |
| requiredCapabilities | array | no | Required capability types |
Update an existing protocol template (must be in draft status). Returns updated name and version.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Protocol template ID |
| name | string | no | Updated name |
| description | string | no | Updated description |
| version | string | no | New version string (semver) |
| steps | array | no | Updated steps array |
| parameters | array | no | Updated parameters array |
Publish a draft protocol template, making it visible in the protocol library for others to discover and use.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Protocol template ID to publish |
Fork a protocol template to create your own version with parameter overrides. Returns the new fork ID.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Protocol template ID to fork |
| name | string | no | Name for the forked protocol |
| parameterOverrides | object | no | Parameter values to override from the source template |
List all forks of a protocol template. Shows who forked it and what parameters they changed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Protocol template ID |
Validate a protocol template against a specific kernel — checks capability availability, transfer compatibility, and automation level feasibility.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Protocol template ID |
| kernelId | string | no | Kernel ID to validate against (optional) |
List protocol runs. Filter by status or kernelId.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Filter by run status |
| kernelId | string | no | Filter by kernel ID |
Get protocol run status including step progress, transfer status, current phase, and evidence hashes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| runId | string | yes | Protocol run ID |
Instantiate a protocol template as a run on a specific kernel with given parameter values.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Protocol template ID |
| kernelId | string | no | Kernel ID to run the protocol on |
| parameterValues | object | no | Runtime parameter values (overrides template defaults) |
| sampleIds | array | no | Sample IDs being processed in this run |
Start execution of a protocol run that is in 'ready' or 'binding' state.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| runId | string | yes | Protocol run ID to start |
Pause a running protocol run. Use resume_protocol_run to continue.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| runId | string | yes | Protocol run ID to pause |
Resume a paused protocol run from where it stopped.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| runId | string | yes | Protocol run ID to resume |
Cancel a protocol run. Cannot be cancelled once completed or already cancelled.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| runId | string | yes | Protocol run ID to cancel |
List active instrument workflows in the orchestrator. Optionally filter by status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Filter by workflow status (e.g. running, completed) |
Get detailed workflow information including steps, node assignments, and progress.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflowId | string | yes | Workflow ID |
Get resource transfer graphs showing instrument topology, transfer edges, and mechanisms for all kernels.
No parameter schema on file.
List automation status for all instrument transfer pairs. Shows current automation level, episode count, and training readiness. Filter by kernelId.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelId | string | no | Filter by kernel ID |
Get automation status for a specific instrument-to-instrument transfer pair.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fromNodeId | string | yes | Source instrument node ID |
| toNodeId | string | yes | Destination instrument node ID |
Record a transfer episode for a node pair. Increments episode count toward VLA training threshold.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fromNodeId | string | yes | Source instrument node ID |
| toNodeId | string | yes | Destination instrument node ID |
| episodeId | string | no | Episode ID (optional) |
| success | boolean | no | Whether the episode succeeded |
Advance the automation level for a transfer pair (manual → teleoperated → pilot_operated → vla_assisted → fully_autonomous). Requires sufficient training episodes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fromNodeId | string | yes | Source instrument node ID |
| toNodeId | string | yes | Destination instrument node ID |
List all transfer agents (robots and human operators) available for instrument-to-instrument transfers.
No parameter schema on file.
Logistics hub overview: active shipments, pending installations, and upcoming bookings.
No parameter schema on file.
List equipment shipments with tracking status. Optionally filter by status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Filter by shipment status (in_transit, delivered, pickup_scheduled, etc.) |
Create a new equipment shipment with origin, destination, package details, and provider.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| equipmentDescription | string | yes | Description of equipment being shipped |
| providerId | string | no | Logistics provider ID |
| origin | object | no | Origin location with label, address, geo coordinates |
| destination | object | no | Destination location with label, address, geo coordinates |
| package | object | no | Package details (weightKg, dimensions, fragile, etc.) |
Get shipping quotes from logistics providers based on origin, destination, weight, and priority.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| originZip | string | no | Origin ZIP code |
| destinationZip | string | no | Destination ZIP code |
| weightKg | number | no | Package weight in kg |
| priority | string | no | Shipping priority level |
List equipment installation orders with step progress and status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Filter by installation status (draft, scheduled, in_progress, completed) |
List space bookings for hosting equipment. Optionally filter by status or space.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Filter by booking status |
| spaceId | string | no | Filter by space ID |
Search for lab/workshop hosting spaces. Filter by size, access schedule, and other requirements.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| maxSqft | number | no | Maximum square footage |
| access | string | no | Access schedule (24/7, business-hours, all) |
Get detailed information about a hosting space including power, amenities, safety features, and pricing.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Space ID |
Find hosting spaces that match specific machine requirements (voltage, area, etc.). Returns scored matches.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| voltage | number | no | Required voltage (e.g. 208, 480) |
| minArea | number | no | Minimum floor area in square feet |
Equipment marketplace overview with demand/supply metrics across all capability types.
No parameter schema on file.
List equipment classes (FDM printers, CNC mills, etc.) with market snapshot data including utilization, demand, and pricing.
No parameter schema on file.
Get network-wide demand vs supply timeline data for capacity planning and market analysis.
No parameter schema on file.
Calculate ROI projection for onboarding equipment. Returns month-by-month revenue, cost, and break-even analysis.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| monthlyCost | number | no | Monthly operating cost in USD |
| avgJobValue | number | no | Average revenue per job in USD |
| utilization | number | no | Expected utilization percentage (0-100) |
Not available: no route answers GET /api/operator on this gateway. The operator's real kernels, devices and in-flight jobs are at GET /api/agent/me.
No parameter schema on file.
Answers 501 not_available: operator machines with utilization and uptime are not recorded on this gateway. The operator's real kernels, devices and in-flight jobs are at GET /api/agent/me.
No parameter schema on file.
Answers 501 not_available: operator earnings history is not recorded on this gateway. Per-job payment state is at GET /api/jobs/:jobId/execution.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| period | string | no | Time period for earnings data |
Answers 501 not_available: operator certifications are not recorded on this gateway (there is no certification store; certifications typed at registration are the operator's own claim and are not checked).
No parameter schema on file.
List all registered sensor channels across kernels. Returns channel descriptors with units and ranges.
No parameter schema on file.
Get sensor channels for a specific kernel. Returns live channel descriptors.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelId | string | yes | Kernel ID to get sensors for |
Get settlement pipeline status including pending operations count, total value queued, and smart account address.
No parameter schema on file.
Get settlement epoch history showing past batch settlements with timing and operation counts.
No parameter schema on file.
DePIN treasury, soulbound capability certificates, and current reward epoch stats.
No parameter schema on file.
Mint a soulbound capability certificate (cNFT via Metaplex Core) for a kernel. Proves a verified capability on-chain as an immutable credential. Step 5 of onboarding.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelDid | string | yes | DID of the kernel (e.g. did:pcc:kernel:biolab-01) |
| capabilityType | string | yes | Capability type (e.g. fdm, cnc-3axis, hplc) |
| assuranceTier | number | no | Assurance tier (0-3) |
| metadata | object | no | Additional metadata (tolerances, materials, calibration proof CID) |
Register a new machine on the PCC network. Provide machine details to create a registration record. Include operator ({walletAddress, displayName, email}): without it the registration is recorded as operator 0x0000000000000000000000000000000000000000 / "Unknown", and prove cannot match it to you.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Machine name |
| category | string | yes | Machine category (e.g. fdm, cnc, laser-cut, hplc) |
| manufacturer | string | no | Manufacturer name |
| model | string | no | Model identifier |
| description | string | no | Machine description |
| capabilities | array | no | Array of capability objects |
| operator | object | no | Who owns this machine. prove and activate match the caller against operator.walletAddress (or operator.email). |
AI analysis of machine documentation. Upload docs to get suggested capabilities, extracted specs, materials, and tolerances.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| document | string | no | Document content or reference to analyze |
One-click agent onboarding with an invite code. Provisions wallet, identity, LLM access, and PCC tools in a single call.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| inviteCode | string | yes | Invite code to redeem |
| string | yes | Email address for the account | |
| password | string | yes | Password for the account |
| name | string | no | Display name (optional) |
Validate an invite code before redeeming it. Returns whether the code is valid and what it includes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | Invite code to check |
List active and completed settlement batches.
No parameter schema on file.
List encrypted evidence bundles stored in the gateway.
No parameter schema on file.
Signal that you want a capability that doesn't exist on the network yet. Creates a demand signal and may auto-create a bounty if enough demand accumulates.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| requesterId | string | yes | ID of the requester |
| capabilityType | string | yes | Type of capability wanted (e.g. electron-beam-welding, cryo-em) |
| description | string | yes | Description of what you need |
| estimatedJobValue | number | no | Estimated payment per job in USD |
| estimatedFrequency | string | no | How often you would use this capability |
| assuranceTier | number | no | Required assurance tier (0-3) |
List open bounties for capabilities the network needs. Operators can claim these to earn rewards by onboarding new capabilities.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Filter by bounty status |
| capabilityType | string | no | Filter by capability type |
Claim a bounty to onboard a new capability. The operator commits to registering the capability and completing verification.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bountyId | string | yes | ID of the bounty to claim |
| operatorId | string | yes | ID of the operator claiming the bounty |
Verify bounty completion by scoring the delivered capability against requirements.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bountyId | string | yes | Bounty ID to verify |
| jobId | string | yes | Job ID that fulfilled the bounty |
| score | number | yes | Verification score (0-1) |
Get top demand signals aggregated by capability type. Shows which capabilities are most wanted on the network.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | number | no | Number of top demand entries to return (default 10) |
Get the bounty hunter leaderboard showing top operators by bounties claimed and verified.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | number | no | Number of entries to return (default 10) |
Create an investment pool for a capability bounty. Stakers earn future protocol fees when the capability goes live.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| capabilityType | string | yes | Type of capability to invest in (e.g. cnc-milling, sla-printing) |
| description | string | yes | Description of the capability pool |
| targetAmount | number | no | Funding target amount |
| currency | string | no | Currency for the pool |
Stake USDC or credits into a capability investment pool.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| poolId | string | yes | Investment pool ID |
| staker | string | yes | Address or DID of the staker |
| amount | number | yes | Amount to stake |
Check earnings from capability investment pools for a staker address.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| staker | string | yes | Address or DID of the staker |
Get details of a specific investment pool including stakes, status, and revenue share terms.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| poolId | string | yes | Investment pool ID |
List all investment pools. Optionally filter by status or capability type.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Filter by pool status |
| capabilityType | string | no | Filter by capability type |
Close an investment pool to new stakes. Pool enters sunset phase.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| poolId | string | yes | Pool ID to close |
Operator claims an investment pool reward after capability verification.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| poolId | string | yes | Pool ID to claim |
| operatorId | string | yes | Operator ID making the claim |
Convert an existing bounty into an investment pool. Allows community staking toward the bounty's capability.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bountyId | string | yes | Bounty ID to convert to a pool |
Get Bittensor verification subnet health, agent bridge status, and network connectivity.
No parameter schema on file.
List verification subnet miners on the Bittensor network. Returns miner addresses, scores, and leaderboard positions.
No parameter schema on file.
List agent-to-agent conversations showing topic, participants, message count, and status.
No parameter schema on file.
Submit a bug report, suggestion, or general feedback about the PCC network.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | no | Feedback type |
| message | string | yes | Feedback message (max 5000 chars) |
| page | string | no | Page or feature the feedback relates to |
Report a detected anomaly — protocol failure, evidence mismatch, stuck job, or suspicious behavior. All agents on the network are notified.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| severity | string | yes | Anomaly severity |
| category | string | yes | Anomaly category |
| description | string | yes | Human-readable description of what went wrong |
| targetAgentId | string | no | Agent or kernel ID being reported (optional) |
| jobId | string | no | Related job ID (optional) |
List all unresolved anomalies on the network. Filter by severity, category, or target agent.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| severity | string | no | Filter by severity: info, warning, critical |
| category | string | no | Filter by category |
| targetId | string | no | Filter by target agent/kernel ID |
Get anomalies involving a specific agent, plus their trust impact score.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agentId | string | yes | Agent or kernel ID |
Mark an anomaly as resolved with a resolution note.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| anomalyId | string | yes | Anomaly ID to resolve |
| resolution | string | yes | How the anomaly was resolved |
Get aggregate anomaly statistics — total, unresolved, by severity, by category.
No parameter schema on file.
Report a protocol failure — when a step in the evidence/escrow/verification pipeline breaks. System may auto-recover.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| protocol | string | yes | Which protocol failed: evidence_submission, escrow_release, verification_consensus, settlement |
| errorCode | string | yes | Error code |
| errorMessage | string | yes | Error description |
| involvedAgents | array | yes | Agent IDs involved |
| jobId | string | no | Related job ID |
| recoveryAction | string | no | Suggested recovery |
Query the DHT for capabilities matching your requirements. Returns announcements from operators whose equipment matches the type, materials, and price range you specify.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | no | Capability type to search for (e.g. 'fdm_print', 'liquid-handler', 'cnc-3axis') |
| materials | array | no | Materials you need (matches if operator supports ANY of these) |
| maxPrice | number | no | Maximum price per job — matches operators whose min price is at or below this |
| limit | number | no | Maximum results to return (default 10) |
Announce capabilities to the DHT network. Signs the announcement with your node's Ed25519 key and broadcasts to connected peers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelId | string | yes | Kernel ID announcing capabilities |
| capabilities | array | yes | Array of capability summaries to announce |
| ttlSeconds | number | no | How long the announcement is valid (default 300) |
List known DHT peers and their connection status. Shows which nodes are currently connected to the gossip network.
No parameter schema on file.
Create an execution scope for a job. Scopes define exactly which tool calls are allowed on a kernel during a job, with command budgets, retry limits, and time-to-live. Required before issuing SCOPED WRITE operations (protocol upload, run create, run action).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelId | string | yes | Kernel ID to create the scope for |
| jobId | string | no | Job ID this scope is bound to (optional) |
| allowedTools | array | yes | List of tool names allowed in this scope (e.g. ['ot2_protocol_upload', 'ot2_run_create', 'ot2_run_action']) |
| allowedPipettes | array | no | Which pipettes may be used (e.g. ['left']) |
| allowedSlots | array | no | Which deck slots may be accessed (e.g. [1, 2, 3, 9]) |
| maxCommands | number | no | Maximum tool calls allowed in this scope (default 100) |
| maxRetries | number | no | Maximum retries allowed (default 3) |
| ttlMinutes | number | no | Scope duration in minutes (default 30) |
| protocolHash | string | no | SHA-256 hash of the approved protocol content. If set, protocol uploads are hash-verified. |
Revoke an execution scope immediately (emergency stop). All pending tool calls under this scope are rejected. The kernel enters a stopped state. A new scope must be created to resume.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scopeId | string | yes | Scope ID to revoke |
Get the audit trail for an execution scope — every tool call made under this scope, with validation results, timestamps, and outcomes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scopeId | string | yes | Scope ID to audit |
Relay a tool call to a device executor. The brain (LLM) posts tool calls here; the executor (on the device) polls for them and executes locally. Used for the brain/executor split architecture.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelId | string | yes | Kernel ID of the target device |
| toolName | string | yes | Tool to execute (e.g. 'ot2_health', 'ot2_run_create') |
| toolArgs | object | yes | Arguments for the tool call |
| scopeId | string | no | Execution scope ID (required for SCOPED WRITE tools) |
Get the result of a previously relayed tool call. Poll this endpoint until the executor has processed the call and posted results.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| callId | string | yes | Tool call ID returned from pcc_relay_tool_call |
Get the latest camera frame from a kernel as a JSON snapshot (base64 JPEG + metadata). For raw JPEG image, use GET /api/ot2/camera/latest directly.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelId | string | yes | Kernel ID to get camera frame from |
Send a chat message to a kernel's operator or agent. Used for human-in-the-loop communication during job execution, troubleshooting, and escalation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelId | string | yes | Kernel ID to send the message to |
| message | string | yes | Message content |
| role | string | no | Sender role (default: user) |
Get chat history with a kernel. Returns messages between agents, operators, and users for a specific kernel.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelId | string | yes | Kernel ID to get chat history for |
| limit | number | no | Maximum messages to return (default 50) |
Approve a submitted machine registration. Moves it from 'submitted' to 'approved' status, enabling the operator to activate and start accepting jobs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| registrationId | string | yes | Registration ID (e.g. 'reg-1234567890') |
Reject a machine registration with a reason. The operator can see the rejection reason and resubmit.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| registrationId | string | yes | Registration ID |
| reason | string | no | Reason for rejection |
Activate an approved registration, making the operator's equipment live on the network and ready to accept jobs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| registrationId | string | yes | Registration ID |
Fast-track: submit evidence that your device works and get auto-approved + activated immediately. No manual review needed. Submit a photo of test output, device health snapshot, or a full evidence bundle with completion events. If evidence meets requirements, registration jumps straight to 'active'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| registrationId | string | yes | Registration ID to prove |
| evidence | object | yes | Evidence proving the device works. Include at least one of: bundleHash+events, photoBase64, or deviceHealth. |
List all machine registrations on the network. See pending, approved, active, and rejected registrations. Public endpoint — no auth required.
No parameter schema on file.
Get details of a specific machine registration by ID, including capabilities, pricing, operator info, and current status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| registrationId | string | yes | Registration ID |
Get NEAR Protocol chain-abstraction integration status. Returns supported chains (near, eth, base, arbitrum, optimism, polygon), supported assets (USDC, USDT, NEAR, ETH, WBTC), and capability flags. Use this to confirm cross-chain settlement is available before requesting quotes.
No parameter schema on file.
Get a cross-chain payment quote from the NEAR 1Click solver network (chaindefuser.com). Provides optimal routing and fee estimates for funding PCC escrow contracts using any source asset on any supported chain. Call near_status first to confirm available chains/assets.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fromChain | string | yes | Source chain (e.g. 'eth', 'base', 'near', 'arbitrum') |
| fromAsset | string | yes | Source asset symbol (e.g. 'USDC', 'ETH', 'NEAR') |
| toChain | string | yes | Destination chain (e.g. 'base', 'eth') |
| toAsset | string | yes | Destination asset symbol (e.g. 'USDC') |
| amount | string | yes | Amount as an integer string in the smallest denomination (e.g. '1000000' for 1 USDC with 6 decimals) |
| recipient | string | no | Recipient address on the destination chain (optional) |
Submit a cross-chain payment intent to the NEAR 1Click solver network. Creates a signed intent that routes the payment atomically across chains. Call near_quote first to obtain a quoteId. Intents typically settle within 30-60 seconds — poll near_intent_status to track progress.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quoteId | string | yes | Quote ID returned from near_quote |
| workflowId | string | yes | PCC workflow or job ID this payment is for |
| recipient | string | no | Recipient address on the destination chain (optional) |
Check the settlement status of a submitted NEAR 1Click cross-chain payment intent. Statuses progress: pending → submitted → settled | failed. Returns txHash and explorerUrl when settled.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| intentId | string | yes | Intent ID returned from near_intent |
Read the PCCProtocol root contract state: current fee rate, total protocol fees collected, total escrow count, and registry addresses. Requires PCC_PROTOCOL_ADDRESS to be configured on the gateway.
No parameter schema on file.
Calculate the protocol fee for a given USDC amount (6-decimal units). Returns the fee, the net amount after fee, and formatted versions of both. Use this before building escrow contracts to understand the true cost.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| amount | string | yes | Amount as a BigInt string in USDC 6-decimal units (e.g. '1000000000' = 1000 USDC) |
Get total protocol fees collected for a specific ERC-20 token address across all escrows. Returns raw wei amount and human-readable formatted value.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tokenAddress | string | yes | ERC-20 token contract address (0x...) |
Get protocol fees collected from a specific escrow contract. Also returns whether the escrow was deployed via the protocol factory. Useful for auditing fee flows.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| escrowAddress | string | yes | Escrow contract address (0x...) |
Create a new MilestoneEscrow contract via the PCCProtocol factory on-chain. Protocol-deployed escrows have fee collection and registry tracking built in. Requires PCC_GATEWAY_PRIVATE_KEY write access.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| payer | string | yes | Payer EVM address (0x...) |
| arbiter | string | yes | Arbiter EVM address (0x...) — resolves disputes |
| token | string | yes | ERC-20 token address for payment (0x...) |
| cwmId | string | yes | Capability Work Module ID as a 32-byte hex string (0x + 64 chars) |
Get a snapshot of DHT telemetry counters and recent events. Returns message counts, peer connection stats, query/announce rates, and a list of the last 50 metric events. Use for monitoring network health.
No parameter schema on file.
List all supplies and materials marketplace categories with the count of active listings in each. Categories cover the full spectrum of physical production inputs: raw metals, plastics, lab reagents, consumables, electronics, tooling, and more.
No parameter schema on file.
Search and filter supplies/materials marketplace listings. Operators buy raw materials here to fulfill capability contracts. Filter by category, in-stock status, location, or free-text query.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Filter by category: raw-metals, plastics-polymers, lab-reagents, lab-consumables, electronics, chemicals, biologicals, tooling, packaging, calibration, safety, other |
| query | string | no | Full-text search across name, description, and tags |
| inStock | string | no | Filter to only in-stock listings |
| location | string | no | Filter by region (e.g. 'US-Midwest', 'EU-West', 'Asia-Pacific') |
Get full details of a specific supplies/materials marketplace listing by ID. Returns pricing, availability, lead time, location, and tags.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Listing ID (e.g. 'lst-al6061-bar') |
Create a new supplies/materials listing in the marketplace. Suppliers post available raw materials, lab reagents, tooling, or consumables for other operators to purchase.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sellerId | string | no | Supplier entity ID |
| category | string | yes | Category: raw-metals, plastics-polymers, lab-reagents, lab-consumables, electronics, chemicals, biologicals, tooling, packaging, calibration, safety, other |
| name | string | yes | Product name |
| description | string | no | Detailed product description |
| unit | string | yes | Unit of sale: kg, L, each, box, plate, etc. |
| pricePerUnit | number | yes | Price per unit in USDC |
| minOrder | number | no | Minimum order quantity |
| maxOrder | number | no | Maximum order quantity |
| inStock | boolean | no | Whether the item is currently available |
| leadTimeDays | number | no | Estimated lead time in business days |
| location | string | no | Supplier region or country |
| tags | array | no | Search tags |
Update an existing supplies/materials listing (price, stock status, description, etc.). Pass only the fields you want to change.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Listing ID to update |
| pricePerUnit | number | no | New price per unit in USDC |
| inStock | boolean | no | Stock availability |
| description | string | no | Updated description |
| leadTimeDays | number | no | Updated lead time in days |
| tags | array | no | Updated search tags |
Remove a supplies/materials listing from the marketplace. The listing is immediately hidden from search results.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Listing ID to remove |
Place a purchase order for supplies or materials. Calculates total price automatically (quantity × pricePerUnit). Returns an order with 'pending' status. Optionally links to an on-chain escrow for trustless settlement.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| listingId | string | yes | Listing ID to order from |
| quantity | number | yes | Quantity to order (must meet listing minOrder/maxOrder) |
| buyerId | string | no | Buyer entity ID (operator kernel ID, etc.) |
| escrowAddress | string | no | Optional on-chain escrow address for trustless settlement |
List marketplace supply orders. Filter by buyerId, sellerId, or status. Returns order history with pricing and status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| buyerId | string | no | Filter to orders placed by this buyer |
| sellerId | string | no | Filter to orders received by this seller |
| status | string | no | Filter by order status |
Get details of a specific supply order including the associated listing details, quantity, total price, status, and optional escrow address.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Order ID (e.g. 'ord-demo-001') |
Raw system state dump — actual DB rows for kernels, devices, jobs, evidence, registrations, capabilities, agent conversations, audit log. No fake numbers, no summaries.
No parameter schema on file.
Operator polls jobs assigned to their kernel; status defaults to queued, and the route can filter any status. Requires operate authority for this kernel: its recorded operator identity (the caller that registered it), its proven operator wallet, or the gateway admin authority. Another identity gets 403; no credentials gets 401; an unregistered kernel gets 404 for a non-admin. Operator identity pro
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelId | string | yes | Kernel ID to poll jobs for |
Operator pushes evidence bundle from a completed job execution. Requires decide authority for the stored job's kernel: its proven operator wallet or the gateway admin authority. A matching claimed operator key gets 403 operator_proof_required. Evidence takes decide, per DECISIONS 2026-10-04 01:25 (N31c). Evidence is posted with the kernel's proven operator wallet authority (decide). The body's ker
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | yes | — |
| kernelId | string | yes | — |
| evidence | object | yes | — |
Operator sends heartbeat with capability re-announcement. Keeps the kernel alive on the network and updates its own capability rows. Requires operate authority for this kernel: its recorded operator identity (the caller that registered it), its proven operator wallet, or the gateway admin authority. Another identity gets 403; no credentials gets 401; an unregistered kernel gets 404 for a non-admin
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelId | string | yes | — |
| capabilities | array | no | — |
Operator reports a job's status (in_progress, completed, failed). Requires operate authority for the stored job's kernel: its recorded operator identity (the caller that registered it), its proven operator wallet, or the gateway admin authority. The body's kernelId cannot choose the authorization target. Another identity gets 403; no credentials gets 401 before the job read; a job without a kernel
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | yes | — |
| kernelId | string | yes | — |
| status | string | yes | — |
| metadata | object | no | — |
Fast-track paid job: one call from DHT discovery to funded escrow + active scope. Auto-negotiates, quotes, creates escrow with milestones, creates execution scope. Returns jobId, scopeId, escrowId, quote with pricing adjustments, contract terms. For testnet, escrow is mock-funded automatically.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelId | string | yes | Target kernel ID (from DHT query) |
| capabilityType | string | yes | e.g. 'liquid-handler', 'fdm', 'cnc-3axis' |
| parameters | object | no | Job parameters (protocolType, volume, materials, etc.) |
| paymentMethod | string | no | Payment method (testnet-mock for demo) |
| userAgentId | string | yes | Your agent/user ID |
Complete a job: gathers tool call audit trail from execution scopes, builds evidence bundle with SHA-256 hash, stores evidence, revokes scopes, and settles escrow (mock or real). This is how a job run through execution scopes is finished. A node that submitted its evidence and set status completed (operator_update_job_status) must not call it: it then answers 409 ("Job already completed or complet
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | yes | Job ID to complete |
| message | string | no | Completion message or notes |
Get a job's settlement status from its own escrow records: status (settled only when a settlement read confirms the release; reported_released when the milestone record says released but nothing confirms it; simulated for a mock escrow; awaiting_settlement, no_settlement_record, unknown or unavailable otherwise), settled, payout, paidAmount (confirmed releases only), reportedReleasedAmount, quoted
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | yes | Job ID |
Get the tool manifest for a kernel's device type. Lists all available tools with their safety classification (read, safe_control, scoped_write, privileged) and input schemas. Use to understand what tools are available before making tool calls.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelId | string | yes | Kernel ID |
Relay a tool call to any kernel's device executor via the generic relay (not OT-2 specific). Works with any device type. Safe tools (read/safe_control) don't need a scope. Scoped write tools require an active execution scope. Returns a call ID — poll pcc_get_tool_result for the response.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelId | string | yes | Target kernel ID |
| toolName | string | yes | Tool name from the device manifest |
| args | object | no | Tool arguments |
| scopeId | string | no | Execution scope ID (required for write operations) |
Submit a high-level capability request in natural language. The system automatically decomposes it into a capability DAG with dependencies, timelines, and budget allocation across fabrication, design, assembly, electronics, software, logistics, and verification nodes. Returns the request with full decomposed DAG. Example: 'Build a cute animatronic plush desk robot with servo-driven animations'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | Short title for the request |
| description | string | yes | Full natural language description of what needs to be built or done |
| budget | number | no | Total budget in USDC (default: 1000) |
| deadline | string | no | ISO 8601 deadline (default: 7 days from now) |
| urgency | string | no | Urgency level — affects cost multipliers (emergency: 2x cost, 0.5x time) |
| currency | string | no | Currency (default: USDC) |
| requesterEmail | string | no | Requester email for notifications |
| requesterWallet | string | no | Requester wallet address for payments |
List all capability requests with optional filtering. Shows status, decomposed DAG summary, estimated costs, and timelines.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Filter by status |
| urgency | string | no | Filter by urgency |
| requesterEmail | string | no | Filter by requester email |
Get a capability request by ID with the full decomposed DAG — all capability nodes, their dependencies, estimated costs/hours, assigned operators, and linked bounty IDs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| requestId | string | yes | Request ID |
Re-trigger decomposition of an existing capability request. Overwrites the existing capability DAG with a fresh decomposition. Useful after updating the description or budget.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| requestId | string | yes | Request ID to decompose |
Publish all pending capability nodes in a request as bounties. Each node becomes a bidding opportunity for operators. Returns the list of created bounty IDs linked to each capability node.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| requestId | string | yes | Request ID to publish |
Get the capability DAG (directed acyclic graph) for a request as adjacency data — nodes with all fields plus explicit edges showing dependency relationships. Useful for visualization or workflow planning.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| requestId | string | yes | Request ID |
Get the critical path (longest dependency chain) for a capability request. The critical path determines the minimum calendar time to complete the request. Returns node IDs in order, the full node details, and total hours on the critical path.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| requestId | string | yes | Request ID |
Assign an operator to a specific capability node within a request. The node status changes to 'assigned'. Operators claim nodes to indicate they will execute that capability.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| requestId | string | yes | Request ID |
| nodeId | string | yes | Capability node ID |
| operatorId | string | yes | Operator kernel ID or wallet address |
Update the status of a capability node within a request. Valid transitions: pending → bidding → assigned → in_progress → completed (or failed). When all nodes complete, the request automatically moves to completed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| requestId | string | yes | Request ID |
| nodeId | string | yes | Capability node ID |
| status | string | yes | New status for the node |
Update a capability request's title, description, budget, deadline, urgency, or contact info. Does not re-decompose — call pcc_decompose_request afterwards if you want a fresh DAG.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| requestId | string | yes | Request ID |
| title | string | no | — |
| description | string | no | — |
| budget | number | no | — |
| deadline | string | no | — |
| urgency | string | no | — |
| requesterEmail | string | no | — |
| requesterWallet | string | no | — |
Cancel a capability request. Cancelled requests cannot be updated, decomposed, or published. This is a soft delete — the request remains visible with status 'cancelled'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| requestId | string | yes | Request ID to cancel |
Not served by the PCC gateway: GET /api/oracle/health returns 404 there. PCC's verification oracle runs as a separate service, and this route answers only where a deployment fronts it. Agents never call the oracle to settle a job: settlement is the gateway's step after pcc_job_complete. Where it is served, it returns the oracle's EIP-712 signing address and chain ID.
No parameter schema on file.
Not served by the PCC gateway: POST /api/oracle/verify returns 404 there. PCC's verification oracle runs as a separate service, and this route answers only where a deployment fronts it. Agents never call it to settle a job: settlement is the gateway's step after pcc_job_complete. Where it is served, it checks that the evidence exists, its hash matches, tier requirements are met, there is no replay
| Parameter | Type | Required | Notes |
|---|---|---|---|
| escrowAddress | string | yes | Escrow contract address |
| jobId | string | yes | PCC job ID |
| kernelId | string | yes | Operator kernel ID |
| evidenceHash | string | yes | SHA-256 hash of evidence bundle |
| assuranceTier | integer | no | Evidence tier (0=none, 1=basic, 2=full, 3=ZK) |
Get the current protocol fee rate (2.35%, immutable) and fee recipient address. The fee is hardcoded in the PCCProtocol smart contract — no admin, no governance, no upgrade can change it.
No parameter schema on file.
Register a capability instance for a kernel. Required before submitting jobs — the gateway needs at least one capability per kernel. Creates a liquid-handler, fdm, cnc-3axis, or other capability type.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelId | string | yes | Kernel ID to register capability for |
| type | string | yes | Capability type (e.g. liquid-handler, fdm, cnc-3axis, laser-cut, document-printing) |
| name | string | no | Human-readable name for the capability |
| description | string | no | Description of what this capability does |
Send a per-kernel heartbeat to keep the kernel marked online. Used by pcc-node daemons as an alternative to the operator relay heartbeat.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelId | string | yes | Kernel ID |
| status | string | no | Kernel status (online/offline) |
| capabilities | array | no | Optional capability announcements |
Announce capabilities for a kernel. NOTE: the gateway currently acknowledges this call but stores nothing, so it does not put any capability on the network. To publish a capability, use create_capability (POST /api/capabilities).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelId | string | yes | Kernel ID |
| capabilities | array | yes | Capability objects to announce |
| devices | array | no | Device IDs that back these capabilities |
| signature | string | no | Ed25519 signature of the announcement |
Upload an encrypted diagnostic bundle when the operator's node has problems. The bundle is encrypted client-side with a retrieval code the operator must share with support before logs can be read. Use this when the operator reports errors, crashes, or misbehavior. The pcc-node CLI runs pcc-node logs --send locally to collect+encrypt; prefer that path when available. This tool is for agent-driven
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelId | string | yes | Kernel ID the diagnostics came from |
| encrypted | object | yes | Encrypted bundle payload |
| bundleHash | string | no | sha256 of plaintext bundle |
| bundleSize | number | no | Size of encrypted payload in bytes |
| logLineCount | number | no | How many log lines are in the bundle |
| systemPlatform | string | no | e.g. Linux-5.15, Darwin-23, Windows-10 |
| collectedAt | string | no | ISO timestamp when bundle was collected |
Send an operator support message to the PCC team. Creates a new support thread or appends to the operator's existing open thread. Can optionally attach a diagnostic retrieval code (from send_diagnostics) so support staff can decrypt logs. Discord webhook fires on every new message, so expect fast response. Use this whenever the operator says something is broken, confusing, or not behaving as expec
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelId | string | yes | Operator's kernel ID |
| kernelName | string | no | Human-readable kernel name |
| message | string | yes | The support message text — describe the problem concretely |
| subject | string | no | Optional thread subject (auto-generated from message if omitted) |
| retrievalCode | string | no | Optional diagnostic retrieval code to attach (from send_diagnostics) |
| systemInfo | object | no | Optional system context (platform, nodeVersion, daemonRunning, gatewayReachable) |
Check for admin replies on the operator's support threads. Call this periodically or when the operator asks 'did they respond yet?'. Returns all threads for this kernel and a hasUnreadReplies boolean indicating new admin messages.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kernelId | string | yes | Operator's kernel ID |
Reply to an existing support thread. Use when the operator wants to add information to a thread started earlier. Needs the threadId from check_support_replies or the original send_support_message response.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| threadId | string | yes | Thread ID to reply to |
| message | string | yes | Reply message |
| retrievalCode | string | no | Optional diagnostic retrieval code to attach |
Issue a fresh block-anchored CaptureNonceChallenge for a job. The operator's device must render this nonce into the captured media (QR code, audio tone, etc.) before calling pcc_capture_upload. The nonce is derived from (challengeId, latest blockHash, workOutputRoot) so captures cannot be pre-computed. Returns challengeId, 64-char hex nonce, blockNumber, maxAgeSeconds (clamped to 120).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | yes | PCC job ID the capture belongs to |
| declaredClass | string | yes | Capture class the operator plans to claim. Determines which gates the verifier will run. |
| requestedTtlSeconds | integer | no | Requested challenge lifetime in seconds. Clamped to 120 server-side. |
Upload a capture (photo / video / audio / sensor clip) with its CaptureManifest for G1..G6 verification. Bytes are base64-encoded inline; optional base64 C2PA manifest bytes can be supplied for CC3+ claims. The server runs the 6-gate CaptureVerifier and persists a PASS/PARTIAL/FAIL verdict. Returns {verdictId, verdict, verifiedClass, gatesPassed, gatesFailed, warnings, anchorCandidate, captureHash
| Parameter | Type | Required | Notes |
|---|---|---|---|
| manifest | object | yes | CaptureManifest — ALCOA+-ready metadata: class, declaredAt (ISO-8601), deviceFingerprint, mediaHash (sha256:<hex>), optional challengeId. See CaptureManifestSchema in @pcc/spec. |
| captureBytesBase64 | string | yes | Base64-encoded capture bytes (image / video / audio / sensor clip). Hash must match manifest.mediaHash. |
| c2paManifestBase64 | string | no | Optional base64-encoded C2PA manifest JUMBF bytes. Required when manifest.class >= CC3. |
| jobId | string | no | Job ID for telemetry binding. Falls back to manifest.jobId if omitted. |
| operatorId | string | no | Explicit operator ID. Falls back to the authenticated session userId. |
| challengeId | string | no | Challenge UUID to re-bind to the in-memory challenge cache (G3 freshness gate). |
| visualNonceEcho | string | no | The visual nonce value the operator rendered in-scene (QR payload, audio tone id, etc.). |
| submittedAt | integer | no | Client-submitted timestamp (epoch ms). Used in drift detection. |
Anchor a PASS + anchor-candidate capture verdict to CaptureClassRegistry on-chain (Base Sepolia by default). Rejects FAIL/PARTIAL verdicts. Idempotent — re-submitting the same verdictId returns the existing anchor row. Returns 202 {status:'deferred'} if CaptureClassRegistry is not yet deployed (CAPTURE_REGISTRY_ADDRESS unset).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| verdictId | string | yes | The verdictId returned by pcc_capture_upload. Must be a PASS verdict with anchorCandidate=true. |
Fetch the combined verdict + on-chain anchor view for a single capture. Mirrors the verifier's DB shape plus the anchor tx metadata (txHash, blockNumber, gasUsed, explorerUrl). Anchor is null if the verdict was never anchored.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| verdictId | string | yes | Capture verdict UUID (from pcc_capture_upload). |
List recent capture verdicts, newest first. Optionally filter by jobId. Default limit is 50, capped at 200 server-side. Returns {verdicts, count, limit, jobId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | no | Filter by job ID. Omit for all verdicts across jobs. |
| limit | integer | no | Maximum rows returned (default 50, hard cap 200). |
Look up a capture's on-chain anchor record in CaptureClassRegistry by its 32-byte captureHash. Returns the registry address, captureHash, and decoded anchor tuple (declaredClass, verifiedClass, manifestHash, submittedBy, jobId, challengeId, blockAnchor, capturedAt, attestationsRoot, attesterCount). onchain is null if the capture was never anchored. Returns 202 deferred when CaptureClassRegistry is
| Parameter | Type | Required | Notes |
|---|---|---|---|
| captureHash | string | yes | Capture hash (32-byte). Accepts 0x-prefixed or unprefixed hex, or sha256:<hex> format. Padded server-side to bytes32. |
Report CaptureVerifier health: which adapters are loaded (c2pa, webauthn, appattest, playintegrity), their staleness status, in-memory challenge cache size, whether CaptureClassRegistry is deployed, and the active PCC_NETWORK. Use this to diagnose why a capture class is being rejected or degraded.
No parameter schema on file.
List the orchestrator templates the dashboard's chat console can drive. Each entry includes slug, display_name, description, produces_kind, capability_class (physical | digital), greeting, and api_base (the route prefix that serves the six session-driver routes for that template). Public — no auth required.
No parameter schema on file.
Heuristic template matcher. Pass a free-text description of what you want to onboard (e.g. 'I run a CNC milling shop' or 'I have a Postgres database with a GraphQL endpoint') and the matcher returns all templates ranked by keyword score with a 'reason' string per match. Public — no auth required.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| input | string | yes | Free-text description of what you want to onboard. |
Start a new physical-operator onboarding session. Returns a session_id used by every subsequent /api/onboard/* call. Auth-required.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Operator / company name (e.g. 'Oakland Titanium Mills'). |
| url | string | no | Optional company website. If supplied, the orchestrator scrapes it on the next /scrape call. |
Scrape a URL into the running physical-operator onboarding session. Triggers a stealth fetch + structured extraction (machines, hours, services, certifications). Returns a small JSON summary; full extraction is appended to the session's running profile and visible via /live-data. Auth-required.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Session id returned by pcc_onboard_session_start. |
| url | string | yes | URL to scrape (e.g. company About page). |
Queue documents (datasheets, SOPs, MOPs, certifications) for ingestion into a physical-operator onboarding session. Document URLs may be local:// for files dropped in the chat console or full https:// URLs. Auth-required.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Session id returned by pcc_onboard_session_start. |
| doc_urls | array | yes | URLs of documents to ingest. Mix of local:// and https:// is fine. |
Finalise a physical-operator onboarding session: registers the operator on PCC, mints a wallet, writes the SEO mirror, returns the publication payload (capabilities, operator_id, discovery_url). Idempotent — safe to retry inside the same session_id. Auth-required.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Session id returned by pcc_onboard_session_start. |
Coarse status snapshot for a physical-operator onboarding session: current state, 0-100 progress, scraped_count, ingested_count, last_event, publication payload (if built). Cheap — designed for polling from the chat header. Auth-required.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Session id returned by pcc_onboard_session_start. |
Full event log for a physical-operator onboarding session — feeds the chat console's activity sidebar. Supports incremental polling via ?since=<unix-millis>. Returns the next cursor on every response. Auth-required.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Session id returned by pcc_onboard_session_start. |
| since | number | no | Unix milliseconds cursor — returns only events with t > since. Use the 'cursor' field of the previous response for incremental polling. |
Register a contributor profile binding a wallet address to a role and a published RateSchedule. Body: address (0x40hex), role (10 ContributorRole values from ADR-12 §2.1 + legacy 'designer'), scheduleHash (0x64hex of a previously published schedule), optional ipId, metadataUri, contributorNftTokenId. Returns the persisted profile (composite id is address:role:tail). Idempotent on the composite id
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Wallet address (0x + 40 hex chars) |
| role | string | yes | ContributorRole — 10 ADR-12 roles + deprecated 'designer' |
| scheduleHash | string | yes | 0x + 64 hex sha256 of a published RateSchedule |
| ipId | string | no | Optional Story Protocol IP Asset ID |
| metadataUri | string | no | Optional ipfs:// or https:// URI |
| contributorNftTokenId | string | no | Optional ContributorNFT tokenId once minted on-chain |
List all contributor profiles for an address across roles. Returns an array of {id, address, role, scheduleHash, ipId, contributorNftTokenId, metadataUri, registeredAt}. Returns empty array when no profiles exist for the address.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Wallet address (0x + 40 hex chars) |
Publish a sealed off-chain RateSchedule. Computes scheduleHash server-side via the canonical sha256-over-canonical-JSON algorithm (matching the on-chain RateScheduleRegistry.publish() invariant). Idempotent: re-publishing the same content returns alreadyPublished:true. Returns {scheduleHash, alreadyPublished}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| publishedBy | string | yes | Address that publishes (0x + 40 hex chars) |
| schedule | object | yes | RateSchedule body — version, segments (constant/step/linear-decay/exponential-decay/adoption-indexed/piecewise-value), and optional notes |
Fetch a published RateSchedule by its content hash. Returns {schedule, publishedBy} with segments re-validated via Zod, or 404 if not found.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scheduleHash | string | yes | 0x + 64 hex sha256 of the schedule |
Evaluate a published RateSchedule at a moment, returning the effective bps. Inputs: scheduleHash + now (unix seconds) + optional jobValueCents (piecewise-value) + optional jobsPerDay (adoption-indexed). Returns {scheduleHash, bps, segmentKind, segmentIndex}. segmentIndex=-1 + bps=0 when no segment covers the moment (silent gap).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scheduleHash | string | yes | 0x + 64 hex schedule hash |
| now | integer | yes | Unix seconds at evaluation moment |
| jobValueCents | integer | no | Job value in cents (piecewise-value segments) |
| jobsPerDay | number | no | Rolling 24h job count (adoption-indexed segments) |
Set (insert-or-replace) the TrainingManifest for a model IP — the dataset weight map the LicensingEngine walks when distributing payouts to a 'model-author' entry in a CompositionManifest. Dataset weightBps must sum to ≤ 10000 (gateway accepts partial mixes; on-chain enforces exact 10000). Returns {modelIpId, manifestHash}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| modelIpId | string | yes | Story IP Asset ID for the model |
| baseModelIpId | string | no | Optional parent ModelNFT IP if this was fine-tuned |
| datasetWeights | array | yes | DatasetIP entries with weightBps (sum ≤ 10000) |
| methodologyHash | string | no | Optional 0x + 64 hex reproducibility hash |
Fetch the TrainingManifest for a model IP. Returns the parsed datasets array + manifestHash + createdAt, or 404 if no manifest has been set.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| modelIpId | string | yes | Story IP Asset ID for the model |
Generate a complete KERNEL_CONFIG JSON for a Trilobio (tcode-api) fleet controller. Wraps buildTrilobioConfig() from the @pcc/trilobio npm package. Returns a TrilobioKernelConfig with sensible defaults (pollIntervalMs=3000, maxScriptTimeoutSec=3600, allowArbitraryScripts=false). The result can be passed to pcc-node start via the KERNEL_CONFIG env var, or handed to setup_generate_config / setup
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Fleet-controller URL on the LAN (host[:port], no trailing slash, no path) — e.g. http://192.168.1.50 |
| apiKey | string | no | Trilobio fleet-controller API key (from the trilobot admin UI). Either apiKey OR username+password is required unless mockMode=true. |
| username | string | no | Fleet-controller account username (basic-auth mode only) |
| password | string | no | Fleet-controller account password (basic-auth mode only) |
| kernelId | string | no | Kernel ID this device belongs to (auto-generated as kernel_trilobio_<timestamp> if omitted) |
| deviceId | string | no | Logical device ID within the kernel (default: trilobio-fleet-01) |
| tcodeApiVersion | string | no | Pinned tcode-api version on the fleet controller. Format: 'latest' or semver (e.g. 1.25.1). Default: latest. Surfaces in evidence bundles for reproducibility. |
| mockMode | boolean | no | Bypass real HTTP and simulate runs. Use for CI / floor demos. Default: false. |
| pollIntervalMs | number | no | Poll interval in ms for run status (range 500-60000). Default: 3000. |
| maxScriptTimeoutSec | number | no | Maximum allowed wall-clock seconds for a single tcode script (range 30-86400). Default: 3600. |
| mockRunDurationMs | number | no | Mock-mode simulated run duration in ms. Default: 2000. |
| allowArbitraryScripts | boolean | no | Permit customer-supplied tcode-api Python scripts (true) or only curated protocol IDs (false). Default: false. Set true only for trusted-counterparty deployments. |
Sanity-check operator-supplied Trilobio options before generating a KERNEL_CONFIG. Wraps validateTrilobioOptions() from @pcc/trilobio. Catches the common mistakes (malformed URL, missing creds, out-of-range timeouts, invalid tcodeApiVersion semver) before they hit the gateway or the device. Returns { valid: boolean, errors: string[], warnings?: string[] }. Note: this is a TypeScript package help
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | no | Fleet-controller URL |
| apiKey | string | no | Fleet-controller API key |
| username | string | no | Basic-auth username |
| password | string | no | Basic-auth password |
| kernelId | string | no | — |
| deviceId | string | no | — |
| tcodeApiVersion | string | no | 'latest' or semver string |
| mockMode | boolean | no | — |
| pollIntervalMs | number | no | — |
| maxScriptTimeoutSec | number | no | — |
| mockRunDurationMs | number | no | — |
| allowArbitraryScripts | boolean | no | — |
Quick lint of a tcode-api Python script before submission to a Trilobio fleet controller. Wraps validateTcodeScript() from @pcc/trilobio. Surface check only — NOT a sandbox or sanitizer. Looks for: imports of tcode_api (presence required), obviously dangerous statements (subprocess, os.system, eval, exec, __import__, socket, urllib, requests, file writes), empty scripts, and missing top-level
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source | string | yes | Full Python source of the tcode-api script to lint |
Return the TRILOBIO_CAPABILITY constant from @pcc/trilobio — a default capability template for a Trilobio fleet controller. Pass to POST /api/capabilities to publish a baseline liquid-handling capability for a kernel hosting a trilobot. Operators can extend the materials and capabilities arrays to advertise instrument-specific features (custom labware libraries, sample types). Notable: inclu
No parameter schema on file.
Attach a notification/dispatch channel to an operator so PCC knows how to ping them when a job lands. The operator's onboarding agent calls this AFTER the conversation that produced the channel record. Transport is a small stable enum (webhook|email|sms|voice|push|mqtt|file|manual) — vendor specifics live in the free-form describe field, written by the operator's agent. PCC the substrate stays n
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Operator slug (typically the operator's address or unique identifier). |
| label | string | yes | Short human label shown to the operator and in admin UIs: 'Front counter printer', 'Owner's phone'. |
| transport | string | yes | Which wire does the message go over. manual = no machine endpoint (dashboard-only). |
| direction | string | no | out=PCC pushes only; in-out=operator's system also replies; in=operator pushes unsolicited. |
| endpoint | object | no | Transport-specific routing payload. webhook→{url}, email→{address}, sms/voice→{phoneE164}, push→{token,platform}, mqtt→{brokerUrl,topic}, file→{scheme,path}, manual→{}. |
| credentialRef | string | no | Reference to a secret in the credential vault (not the secret itself). PCC resolves it at dispatch time. |
| describe | string | yes | Plain-English instructions for how PCC should talk to whatever is on the other end. Written by the operator's onboarding agent. Required, ≥4 chars. Example: 'POST JSON with keys order_id, line_items[] |
| replyContract | string | no | Optional operator-authored contract describing how the operator's system will respond to evidence requests, status pings, etc. |
| enabled | boolean | no | Whether the channel is live (defaults to true). |
List every channel attached to an operator. Returns the full channel records (id, transport, direction, endpoint, describe, enabled flags). Useful for an operator's onboarding agent to confirm what is wired up, and for status dashboards.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Operator slug. |
Update an existing channel — toggle enabled, rewrite the describe contract, change the endpoint payload, etc. Merges into the existing record. The operator slug, id, and createdAt are immutable.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Channel id (returned from attach_operator_channel). |
| label | string | no | — |
| direction | string | no | — |
| endpoint | object | no | — |
| credentialRef | string | no | — |
| describe | string | no | — |
| replyContract | string | no | — |
| enabled | boolean | no | — |
Remove a channel from an operator. Future jobs will not dispatch to it. Use update_operator_channel with enabled=false to silence temporarily without losing the recipe in describe.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Channel id. |
Fire a synthetic job at every enabled channel for an operator so the onboarding agent (and the human watching) can confirm the integration end-to-end before a real job lands. Returns per-channel dispatch results (delivered, ref, warnings).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Operator slug. |
Bidirectional onboarding: the registry talks back. Describe in plain English what you are trying to set up — 'wood-fired pizza shop in SF', 'Opentrons OT-2 liquid handler', 'same-day SF courier' — and the registry returns N candidate Capability StructureDefinition (CSD) templates ranked by keyword-overlap relevance (name×3, tags×2, description×1; tie-break on usage). Empty query falls back to popu
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Plain-English description of the capability the user is trying to set up. Optional — empty falls back to popularity. |
| limit | integer | no | Max results (1..20, default 5). |
| kind | string | no | Filter by CSD kind. |
Return CSDs sorted by adoption (usage-count descending). Useful for first-time operators who want to see what kind of capabilities others are publishing. Each entry includes the CSD record plus usage attribution: count, recent adopters (deduped, capped at 50), and lastUsedAt.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max results (1..50, default 10). |
Four-slot substrate view for an operator: kernels, capabilities (with sla + availability), notification channels, and the per-kernel A2A agent-card URLs. Returns totals and a missing list naming any of the four onboarding slots that are still empty. Use this from an onboarding agent's wrap-up step to confirm 'are all four slots wired before I go live?' status is ready | partial | `unconfigur
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Operator slug — typically the operator's wallet address used as operatorAddress on their kernels. |
Propose a composition — a sequenced DAG of capability instances to satisfy a multi-step outcome under a budget + assurance tier. Accepts either a flat steps list or an outcome chain. Returns a candidate plan ranked by optimizeFor (price | speed | quality) with per-step assignments. The composition is persisted for ~30 minutes (proposed status) and can be executed once via execute_composition.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| outcomeType | string | yes | High-level outcome label, ≤120 chars. Example: 'desk-robot-prototype'. |
| steps | array | no | Ordered list of capability types this composition needs (1..20). Use this OR outcomeChain. |
| outcomeChain | array | no | Alternative to steps: chain of named sub-outcomes. The planner expands each into capability types. |
| budgetUSD | number | yes | Total budget the user is willing to spend across all steps. |
| minAssuranceTier | integer | yes | Minimum acceptable assurance tier on every step. |
| location | object | no | Geographic constraint (lat/lng + radius, or country, etc). |
| optimizeFor | string | no | Ranking objective (default price). |
| requester | object | no | {agentId, did?} — the agent submitting the request. |
| description | string | no | Free-form natural-language description (≤4000 chars). |
Retrieve a previously-proposed composition by id. Returns 404 if unknown, 410 if the 30-minute proposal window has expired. Use this to inspect a plan before executing, or to recover a plan id after a restart.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Composition id (returned from propose_composition). |
Commit a proposed composition: drives the DAG through the workflow engine, each step records a reputation outcome, the composition's reputation is finalized when the run ends. When PCC_COMPOSE_EXECUTE_REAL=true is set on the gateway, steps submit real jobs via JobFacade and the workflow run is durable (@pcc/workflow). When the flag is off, the NOOP runner returns synthetic success — useful in de
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Composition id from propose_composition. Must be in proposed status and not expired. |
| idempotencyKey | string | no | Optional caller-supplied key (≤120 chars) to dedupe execute calls. |
Report a bug, friction, or dead-end you hit while using PCC. Call this the moment you get stuck and cannot recover: a 5xx (its response carries a report_hint with pre-filled fields), a 4xx you cannot fix from its message, the same step failing twice, or a misleading tool/description. PUBLIC — works before you provision an API key (cold agents are exactly who this is for). Persisted durably and r
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | no | bug = something is broken/wrong; friction = it works but was confusing/harder than it should be; idea = a suggestion or missing capability. Defaults to bug. |
| summary | string | yes | 1-line description of what you were doing and what went wrong. Example: 'POST /api/build/contract returned 500 with no hint about the missing field.' |
| detail | string | no | Multi-line context: the full error body, what you tried, what you expected. Optional but recommended. |
| endpoint | string | no | The route you were on when you got stuck. From a 5xx report_hint.send.endpoint. Example: '/api/build/contract'. |
| method | string | no | The HTTP method you used. From report_hint.send.method. Example: 'POST'. |
| status | integer | no | The HTTP status you got. From report_hint.send.status. Example: 500. |
| errorCode | string | no | The machine error code from the response body, if any. From report_hint.send.errorCode. |
| traceId | string | no | Your journey ID — returned by provision_api_key and on every response as x-pcc-trace-id (also in a 5xx report_hint.traceId). Lets PCC replay your full run. |
| severity | string | no | How badly this blocked you. Optional. |
| agentId | string | no | Which model/agent you are. Example: 'claude', 'gpt-4o', 'gemini'. Optional. |
| logs | array | no | Optional but valuable: your last few steps as SUMMARIES (never full request/response bodies) — the sequence that led to the failure. Secrets are never allowed in a note. |
Report one phase of an onboarding attempt, success or failure (attempt reporting contract v1). Send one report when each runbook phase ends, and a final report with phase "session" (with the phases roll-up), also when you stop early (outcome abandoned or budget_stop). Generate sessionId (UUID v4) once per attempt and increment seq with every report; a retried report with the same sessionId a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | yes | — |
| contract | integer | no | — |
| sessionId | string | yes | UUID v4, generated once at the start of the attempt |
| seq | integer | yes | Per-session report counter |
| phase | yes | — | |
| outcome | yes | — | |
| durationMs | integer/null | no | The phase's wall time; on session, the whole attempt |
| summary | string/null | no | One line, e.g. "register: failed, POST /api/kernels 400" |
| detail | string/null | no | — |
| logs | array/null | no | The phase's step timeline, summaries only |
| phases | array/null | no | Only on phase "session": the roll-up |
| ids | object/null | no | Only the ids known so far: each at most 200 characters of [A-Za-z0-9:._/-], or null |
| device | object/null | no | — |
| harness | object/null | no | — |
| pack | object/null | no | — |
| env | object/null | no | — |
| tokens | object/null | no | Never guess: send null with source "unknown" |
| proposal | object/null | no | One improvement idea |
| traceId | string/null | no | x-pcc-trace-id of the last PCC call |
| consent | object/null | no | — |
Save a generated dashboard to the network so the user gets a live, shareable URL: https://capability.network/a/<slug>. Pass a manifest — a small declarative DashboardManifest (windows + live-data bindings + actions) conforming to the schema at https://capability.network/ui-kit/v1/manifest.schema.json; the shipped pcc-ui kit renders it identically everywhere (you compose the manifest, the kit ren
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Short human name for the dashboard, e.g. 'Watch my pizza + courier'. Used to mint the slug. |
| description | string | no | One-line description of what the dashboard shows. |
| manifest | object | yes | The DashboardManifest (2-6KB JSON) conforming to https://capability.network/ui-kit/v1/manifest.schema.json. Required top-level keys: csd (must be 'pcc://artifacts/dashboard/v1'), title, and `secti |
| capabilityTypes | array | no | Capability types this dashboard is about, e.g. ['pizza.order','courier.dispatch']. This is the discovery join — it's how search_dashboards finds this artifact later. |
| composeRefs | array | no | Optional pinned, re-plannable ComposeRequest objects (value chains). Pin the request, never a compositionId (those expire in 30 min). |
| visibility | string | no | Who can load it. Default 'unlisted' (anyone with the link; not in listings). 'public' appears in search_dashboards; 'private' is owner-only. |
| renderedCid | string | no | Optional CID of a rendered-HTML export saved via /api/storage. |
Recall a saved dashboard by its id or slug. Returns the full artifact (manifest + metadata). Use this to reload a dashboard the user asks for again ('open my pizza dashboard') instead of regenerating it — a saved dashboard reloads with zero regeneration. Public for public/unlisted artifacts; owner-only for private ones. Increments the load counter (a popularity signal).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| idOrSlug | string | yes | The artifact id (ua_...) or its slug (e.g. 'watch-my-pizza-8k3f', the tail of the /a/<slug> URL). |
Discover existing public dashboards before you generate a new one (recall-first — the library accrues; adopt > extend > build for UIs too). Filter by capabilityType (e.g. 'pizza.order'), free-text q over name/description/types, and sort by popularity or recency. Returns { entries, total, offset, limit }. Only public artifacts are listed; unlisted ones load by slug via get_dashboard but never
| Parameter | Type | Required | Notes |
|---|---|---|---|
| capabilityType | string | no | Filter to dashboards tagged with this capability type, e.g. 'pizza.order'. |
| q | string | no | Free-text search over name, description, and capability types. |
| sort | string | no | Ranking: 'popular' (by use+load+fork counts) or 'recent' (default). |
| offset | integer | no | Pagination offset (default 0). |
| limit | integer | no | Max results (1..100, default 20). |
Fork an existing dashboard into a new artifact you own, preserving lineage back to the original (the social remix verb). Use this to adapt a popular dashboard rather than build from scratch — e.g. fork a 'watch pizza' dashboard and raise the budget or add a receipt window via update_dashboard. Increments the source's fork counter. You can fork any public/unlisted artifact, or a private one you own
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The id (ua_...) of the artifact to fork. |
| name | string | no | Optional name for the fork (defaults to '<original> (fork)'). |
| visibility | string | no | Visibility of the fork (default 'unlisted'). |
Modify a dashboard you own (owner-only). Replace the manifest or any metadata field; the version increments. Use this to edit a saved surface meaningfully — 'raise budgetUSD to 40', 'add a receipt window', 'make it public'. A replaced manifest must still conform to the schema and must not contain an API key. Only send the fields you want to change.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The id (ua_...) of the artifact to update. |
| name | string | no | New name. |
| description | string | no | New description. |
| manifest | object | no | Replacement DashboardManifest (must conform to the schema; no API key). Omit to leave the manifest unchanged. |
| capabilityTypes | array | no | Replacement capability-type tags. |
| composeRefs | array | no | Replacement pinned ComposeRequest objects. |
| visibility | string | no | New visibility (e.g. flip 'unlisted' -> 'public' to list it). |
| renderedCid | string | no | New rendered-HTML export CID. |
Compose a live PCC dashboard for a physical-capability task — pass a DashboardManifest (windows + live data bindings + actions) and it renders as an interactive MCP App.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| csd | yes | The builtin CSD URI this manifest conforms to. | |
| title | string | yes | — |
| description | string | no | — |
| api_base | string | no | Gateway base URL. Default https://capability.network. |
| theme | no | — | |
| sections | array | yes | — |
Compose a live PCC dashboard rendered through the closed, PCC-owned IR (read-only). Pass a DashboardManifest; it renders as an interactive MCP App via the audited closed-IR render path.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| csd | yes | The builtin CSD URI this manifest conforms to. | |
| title | string | yes | — |
| description | string | no | — |
| api_base | string | no | Gateway base URL. Default https://capability.network. |
| theme | no | — | |
| sections | array | yes | — |
Price a configured PCC capability (typed operation). Returns the itemized quote for the given capability type + selections. Pure calculation — no funds move and nothing is created. Maps to POST /api/build/price.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | Capability type, e.g. 'fdm'. |
| selections | object | yes | Parameter selections. |
| profileId | string | no | — |
| capabilityId | string | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Physical Capability Cloud or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 2.19.0.
2.19.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Physical Capability Cloud can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.