network.capability/physical-capability-cloud
Discover, hire, and verify real-world physical capability through MCP.
* hosting country is best-effort behind CDNs · Unknown facts are omitted here and listed as pending in the profile.
Trust verdict
No blockers found across the assessed dimensions.
Profile
What this server is — descriptive, not a rating. The verdict above judges it; this describes it.
Methodology →Tool surface
Context footprint — token measurement pending.
activate_registrationActivate an approved registration, making the operator's equipment live on the network and ready to accept jobs.
advance_automationAdvance the automation level for a transfer pair (manual → teleoperated → pilot_operated → vla_assisted → fully_autonomous). Requires sufficient training episodes.
Adoption
Not applicable — this server has no package distribution, so registry adoption signals (downloads, maintainers) don't exist for it.
Connect
https://capability.network/mcpSources
Every verdict and label is attributable to its source and recomputed from our own landed copy, never read live on this page.
analyze_machine_docsAI analysis of machine documentation. Upload docs to get suggested capabilities, extracted specs, materials, and tolerances.
approve_registrationApprove a submitted machine registration. Moves it from 'submitted' to 'approved' status, enabling the operator to activate and start accepting jobs.
approve_tokenApprove ERC-20 token spending for an escrow contract on-chain. Call this before fund_escrow. Returns transaction hash.
archive_encrypted_bundleArchive an encrypted evidence bundle to IPFS and store the resulting CID in the database. Idempotent — returns existing CID if already archived.
archive_evidenceArchive an evidence bundle to IPFS/Storacha for permanent decentralized storage. Returns the content-addressed CID.
attach_operator_channelAttach 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 neutral. Returns the channel record with a generated id.
build_contractBuild and submit a capability contract with on-chain milestone escrow. Returns job ID and escrow address.
calculate_priceCalculate price for a capability configuration. Returns base price, tier premiums, and estimated total cost.
calculate_roiCalculate ROI projection for onboarding equipment. Returns month-by-month revenue, cost, and break-even analysis.
cancel_protocol_runCancel a protocol run. Cannot be cancelled once completed or already cancelled.
check_inviteValidate an invite code before redeeming it. Returns whether the code is valid and what it includes.
check_support_repliesCheck 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.
claim_bountyClaim a bounty to onboard a new capability. The operator commits to registering the capability and completing verification.
claim_ip_revenueClaim earned revenue from an IP asset vault. Returns the claimed amount and transaction hash.
claim_poolOperator claims an investment pool reward after capability verification.
close_poolClose an investment pool to new stakes. Pool enters sunset phase.
commit_evidenceCreate a Merkle commitment for an evidence bundle hash. Used as the first step in ZK proof generation for Tier 3 assurance.
convert_bounty_to_poolConvert an existing bounty into an investment pool. Allows community staking toward the bounty's capability.
create_capabilityRegister 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.
create_investment_poolCreate an investment pool for a capability bounty. Stakers earn future protocol fees when the capability goes live.
create_kernelRegister a new Shop Kernel (physical site) on the PCC network. Part of Step 2 in the onboarding flow.
create_protocolCreate a new protocol template draft. Returns the new template ID.
create_protocol_runInstantiate a protocol template as a run on a specific kernel with given parameter values.
create_shipmentCreate a new equipment shipment with origin, destination, package details, and provider.
delete_operator_channelRemove 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`.
deposit_bondDeposit an operator bond for a milestone on-chain. Required for Assurance Tier 3 jobs. Returns transaction hash.
dispute_verificationFile a dispute against the consensus verdict. Only verifiers who submitted a response can dispute. Requires additional evidence CID.
distribute_royaltiesSet revenue splits for an IP asset among stakeholders (designer, operator, verifier, assembler, curator). Splits must sum to 100.
emit_telemetryManually emit a telemetry event for a job pipeline phase. Used by kernels and agents to report execution progress.
execute_compositionCommit 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 dev/test. Re-executing an already-run composition replays the stored result (idempotent — reputation d…
file_escrow_disputeFile a dispute against a milestone on-chain. Challenger must post a bond and provide evidence hash. Returns transaction hash.
fork_dashboardFork 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.
fork_protocolFork a protocol template to create your own version with parameter overrides. Returns the new fork ID.
fund_escrowFund an escrow contract on-chain. The payer must have already approved the token transfer (use approve_token first). Returns transaction hash.
get_active_telemetryList currently active jobs with their current pipeline phase and telemetry status.
get_agent_anomaliesGet anomalies involving a specific agent, plus their trust impact score.
get_anomaly_statsGet aggregate anomaly statistics — total, unresolved, by severity, by category.
get_automation_statusGet automation status for a specific instrument-to-instrument transfer pair.
get_bounty_leaderboardGet the bounty hunter leaderboard showing top operators by bounties claimed and verified.
get_build_optionsGet configuration options for a capability type (materials, dimensions, tolerances, assurance tiers). Use before calling calculate_price.
get_bundle_ipfsGet IPFS CIDs for a bundle — returns the primary CID, metadata CID, and Filecoin deal ID if available.
get_capability_ipGet the Story Protocol IP registration for a capability by its capability ID.
get_compositionRetrieve 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.
get_dashboardRecall 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).
get_demand_supplyGet network-wide demand vs supply timeline data for capacity planning and market analysis.
get_depin_statsDePIN treasury, soulbound capability certificates, and current reward epoch stats.
get_equipment_classesList equipment classes (FDM printers, CNC mills, etc.) with market snapshot data including utilization, demand, and pricing.
get_escrowGet escrow details. Pass a DB ID for database record (with milestones and disputes), or an EVM address (0x...) to read directly from the blockchain.
get_escrow_chain_stateRead full on-chain escrow state with all milestone details from the blockchain. More detailed than get_escrow for on-chain contracts.
get_escrow_disputeRead dispute state for a specific milestone from the blockchain.
get_escrow_eventsGet on-chain event history for an escrow contract. Returns funding, release, dispute, and bond events.
get_evidence_bundleGet an encrypted evidence bundle by its bundle ID. Returns the encrypted payload and key capsules.
get_installationsList equipment installation orders with step progress and status.
get_ip_lineageGet the full IP lineage chain for an asset — parent capabilities and all derivative job registrations.
get_ip_revenueGet a revenue snapshot for an IP asset — total earned, pending claims, and recent payments.
get_jobGet job details including progress, evidence bundles, and milestones.
get_job_telemetryGet full event timeline for a specific job — all pipeline phase transitions with timings and metadata.
get_kernelGet kernel details including full capability objects, devices, and queue.
get_kernel_devicesList all devices registered under a specific kernel, including adapter configs and device types.
get_kernel_jobsList all jobs submitted to a specific kernel, including job status and progress.
get_kernel_sensorsGet sensor channels for a specific kernel. Returns live channel descriptors.
get_lit_conditionsGet Lit Protocol access conditions for a Lit-encrypted evidence bundle. Returns the conditions that gate decryption.
get_logistics_overviewLogistics hub overview: active shipments, pending installations, and upcoming bookings.
get_marketplace_overviewEquipment marketplace overview with demand/supply metrics across all capability types.
get_operator_certsList operator certifications (OSHA, safety training, PCC network certs) with validity status.
get_operator_dashboardOperator dashboard overview: machines, earnings summary, and maintenance alerts.
get_operator_earningsGet operator earnings breakdown over a time period. Includes daily earnings and cumulative totals.
get_operator_machinesList all machines registered under the operator account with utilization and uptime stats.
get_operator_statusFour-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` | `unconfigured`. Public — operator slug is non-secret and the response carries no credentials (channel `credenti…
get_poolGet details of a specific investment pool including stakes, status, and revenue share terms.
get_pool_earningsCheck earnings from capability investment pools for a staker address.
get_popular_csd_templatesReturn 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.
get_protocolGet protocol template details by ID. Returns steps, transfers, parameters, and metadata.
get_protocol_forksList all forks of a protocol template. Shows who forked it and what parameters they changed.
get_protocol_runGet protocol run status including step progress, transfer status, current phase, and evidence hashes.
get_registrationGet details of a specific machine registration by ID, including capabilities, pricing, operator info, and current status.
get_sensor_channelsList all registered sensor channels across kernels. Returns channel descriptors with units and ranges.
get_settlement_epochsGet settlement epoch history showing past batch settlements with timing and operation counts.
get_settlement_statusGet settlement pipeline status including pending operations count, total value queued, and smart account address.
get_shipment_quoteGet shipping quotes from logistics providers based on origin, destination, weight, and priority.
get_shipmentsList equipment shipments with tracking status. Optionally filter by status.
get_spaceGet detailed information about a hosting space including power, amenities, safety features, and pricing.
get_space_bookingsList space bookings for hosting equipment. Optionally filter by status or space.
get_subnet_minersList verification subnet miners on the Bittensor network. Returns miner addresses, scores, and leaderboard positions.
get_subnet_statusGet Bittensor verification subnet health, agent bridge status, and network connectivity.
get_telemetry_logsQuery structured logs with filters for level, source, jobId, kernelId, time range, and full-text search.
get_telemetry_statsGet aggregate pipeline telemetry statistics including phase timings, success rates, and throughput metrics across all jobs.
get_token_allowanceRead the ERC-20 token allowance granted by an owner to a spender from the blockchain.
get_token_balanceRead an ERC-20 token balance for an account address from the blockchain.
get_top_demandGet top demand signals aggregated by capability type. Shows which capabilities are most wanted on the network.
get_transfer_graphsGet resource transfer graphs showing instrument topology, transfer edges, and mechanisms for all kernels.
get_unresolved_anomaliesList all unresolved anomalies on the network. Filter by severity, category, or target agent.
get_verification_assignmentsGet pending verification assignments for a verifier node. Returns requests this verifier has been assigned but not yet responded to.
get_verification_statusGet verification status for a request. Returns vote tally, consensus state, dispute list, and pending response count.
get_workflowGet detailed workflow information including steps, node assignments, and progress.
get_workflowsList active instrument workflows in the orchestrator. Optionally filter by status.
get_write_statusCheck if on-chain write operations are enabled (requires PCC_GATEWAY_PRIVATE_KEY to be configured). Returns write status and signer address.
grant_evidence_accessGrant a new recipient access to an encrypted evidence bundle. Creates a re-encrypted key capsule for the recipient.
kernel_announce_capabilitiesAnnounce capabilities for a kernel. Used by pcc-node daemons after hardware detection to register what the kernel can do.
kernel_heartbeatSend a per-kernel heartbeat to keep the kernel marked online. Used by pcc-node daemons as an alternative to the operator relay heartbeat.
list_api_keysList 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.
list_automation_statusList automation status for all instrument transfer pairs. Shows current automation level, episode count, and training readiness. Filter by kernelId.
list_batchesList active and completed settlement batches.
list_bountiesList open bounties for capabilities the network needs. Operators can claim these to earn rewards by onboarding new capabilities.
list_capability_typesList all capability types registered on the network (FDM, SLA, CNC, HPLC, etc.) with metadata.
list_conversationsList agent-to-agent conversations showing topic, participants, message count, and status.
list_escrowsList escrow contracts with milestones and bonds. Optionally filter by status.
list_evidenceList encrypted evidence bundles stored in the gateway.
list_evidence_grantsList all evidence access grants for an address. Returns bundles the address has been granted access to.
list_jobsList all jobs with status. Optionally filter by kernelId or status.
list_kernelsList all Shop Kernels on the network with status and capability types. Optionally filter by status.
list_operator_channelsList 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.
list_poolsList all investment pools. Optionally filter by status or capability type.
list_protocol_runsList protocol runs. Filter by status or kernelId.
list_protocolsList protocol templates in the library. Filter by tags, required capabilities, search query, or status.
list_registrationsList all machine registrations on the network. See pending, approved, active, and rejected registrations. Public endpoint — no auth required.
list_transfer_agentsList all transfer agents (robots and human operators) available for instrument-to-instrument transfers.
lit_decryptDecrypt a Lit Protocol-encrypted evidence bundle using a Lit auth signature. Returns the decrypted bundle payload.
marketplace_categoriesList 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.
marketplace_create_listingCreate a new supplies/materials listing in the marketplace. Suppliers post available raw materials, lab reagents, tooling, or consumables for other operators to purchase.
marketplace_delete_listingRemove a supplies/materials listing from the marketplace. The listing is immediately hidden from search results.
marketplace_get_listingGet full details of a specific supplies/materials marketplace listing by ID. Returns pricing, availability, lead time, location, and tags.
marketplace_get_orderGet details of a specific supply order including the associated listing details, quantity, total price, status, and optional escrow address.
marketplace_list_listingsSearch 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.
marketplace_list_ordersList marketplace supply orders. Filter by buyerId, sellerId, or status. Returns order history with pricing and status.
marketplace_place_orderPlace 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.
marketplace_update_listingUpdate an existing supplies/materials listing (price, stock status, description, etc.). Pass only the fields you want to change.
match_spacesFind hosting spaces that match specific machine requirements (voltage, area, etc.). Returns scored matches.
mint_certificateMint 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.
near_intentSubmit 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.
near_intent_statusCheck the settlement status of a submitted NEAR 1Click cross-chain payment intent. Statuses progress: pending → submitted → settled | failed. Returns txHash and explorerUrl when settled.
near_quoteGet 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.
near_statusGet 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.
onboard_machineRegister a new machine on the PCC network. Provide machine details to create a registration record.
operator_heartbeatOperator sends heartbeat with capability re-announcement. Keeps the kernel alive on the network and updates available capabilities.
operator_poll_jobsOperator polls for pending jobs assigned to their kernel. Returns queued jobs ready for execution. Used by pcc-node daemon.
operator_push_evidenceOperator pushes evidence bundle from a completed job execution. Contains device ID, execution timestamp, result payload, and event timeline.
operator_update_job_statusOperator updates job status during execution (in_progress, completed, failed). Called by pcc-node as jobs progress.
pause_protocol_runPause a running protocol run. Use resume_protocol_run to continue.
pay_ip_royaltyPay royalties to an IP asset vault. The payer sends tokens that flow to stakeholders via the royalty splits.
pcc_assign_node_operatorAssign 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.
pcc_camera_latestGet 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.
pcc_cancel_requestCancel a capability request. Cancelled requests cannot be updated, decomposed, or published. This is a soft delete — the request remains visible with status 'cancelled'.
pcc_capture_anchorAnchor 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).
pcc_capture_challengeIssue 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).
pcc_capture_class_registryLook 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 not yet deployed.
pcc_capture_statusFetch 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.
pcc_capture_uploadUpload 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, manifestHash}.
pcc_chat_historyGet chat history with a kernel. Returns messages between agents, operators, and users for a specific kernel.
pcc_chat_sendSend a chat message to a kernel's operator or agent. Used for human-in-the-loop communication during job execution, troubleshooting, and escalation.
pcc_contributor_listList 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.
pcc_contributor_registerRegister 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 — re-posting the same (address, role, contributorNftTokenId) replaces the prior profile.
pcc_create_scopeCreate 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).
pcc_decompose_requestRe-trigger decomposition of an existing capability request. Overwrites the existing capability DAG with a fresh decomposition. Useful after updating the description or budget.
pcc_dht_announceAnnounce capabilities to the DHT network. Signs the announcement with your node's Ed25519 key and broadcasts to connected peers.
pcc_dht_metricsGet 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.
pcc_dht_peersList known DHT peers and their connection status. Shows which nodes are currently connected to the gossip network.
pcc_dht_queryQuery the DHT for capabilities matching your requirements. Returns announcements from operators whose equipment matches the type, materials, and price range you specify.
pcc_generate_uiGenerate a dynamic visual interface and serve it locally via pcc-node's UI server (localhost:3200). Supports built-in templates (plate-layout, protocol-builder, job-status, camera-viewer, device-config) or custom HTML. The UI appears in the operator's browser. Form submissions are queued for the agent to read via pcc_get_ui_submissions.
pcc_get_requestGet a capability request by ID with the full decomposed DAG — all capability nodes, their dependencies, estimated costs/hours, assigned operators, and linked bounty IDs.
pcc_get_request_critical_pathGet 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.
pcc_get_request_dagGet 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.
pcc_get_tool_manifestGet 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.
pcc_get_tool_resultGet the result of a previously relayed tool call. Poll this endpoint until the executor has processed the call and posted results.
pcc_job_completeComplete 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).
pcc_job_settlementGet settlement status for a completed job: escrow address, evidence hash, milestones with amounts and status, paid amount, currency, and linked negotiation session.
pcc_list_requestsList all capability requests with optional filtering. Shows status, decomposed DAG summary, estimated costs, and timelines.
pcc_list_verdictsList recent capture verdicts, newest first. Optionally filter by jobId. Default limit is 50, capped at 200 server-side. Returns {verdicts, count, limit, jobId}.
pcc_onboard_session_build_agentFinalise 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.
pcc_onboard_session_ingest_docsQueue 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.
pcc_onboard_session_live_dataFull 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.
pcc_onboard_session_scrapeScrape 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.
pcc_onboard_session_startStart a new physical-operator onboarding session. Returns a session_id used by every subsequent /api/onboard/* call. Auth-required.
pcc_onboard_session_statusCoarse 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.
pcc_oracle_statusCheck if the PCC verification oracle is online. Returns the oracle's EIP-712 signing address and chain ID. The oracle is required for all escrow settlements — no attestation means no fund release.
pcc_oracle_verifySubmit evidence for oracle verification. The oracle checks: evidence exists, hash matches, tier requirements met, no replay, operator identity valid. Returns a signed EIP-712 attestation that the escrow contract requires to release funds. This is the critical path — every settlement flows through this endpoint.
pcc_orchestrator_list_templatesList 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.
pcc_orchestrator_match_capabilitiesHeuristic 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.
pcc_protocol_feeGet 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.
pcc_publish_requestPublish 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.
pcc_relay_generic_tool_callRelay 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.
pcc_relay_tool_callRelay 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.
pcc_reportReport friction, confusion, or bugs you hit while onboarding. Call this when you get stuck and cannot recover from an error, when a tool description was misleading, when an endpoint returned an unexplained 500, or when you abandoned a workflow because the next step was unclear. Include your `trace_id` (returned from `provision_api_key` or echoed via the `x-pcc-trace-id` response header) so PCC operators can replay your full journey. PUBLIC — works even before you provision an API key. Rate-limit…
pcc_revoke_scopeRevoke 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.
pcc_schedule_evaluateEvaluate 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).
pcc_schedule_getFetch a published RateSchedule by its content hash. Returns {schedule, publishedBy} with segments re-validated via Zod, or 404 if not found.
pcc_schedule_publishPublish 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}.
pcc_scope_auditGet the audit trail for an execution scope — every tool call made under this scope, with validation results, timestamps, and outcomes.
pcc_submit_paid_jobFast-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.
pcc_submit_requestSubmit 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'.
pcc_training_manifest_getFetch the TrainingManifest for a model IP. Returns the parsed datasets array + manifestHash + createdAt, or 404 if no manifest has been set.
pcc_training_manifest_setSet (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}.
pcc_trilobio_build_configGenerate 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_register_device for direct API-driven registration. Note: this is a TypeScript package helper (no H…
pcc_trilobio_capability_templateReturn 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: includes `tcode-script-execution` as an advertised capability, which is unique to Trilobio — operators wh…
pcc_trilobio_validate_optionsSanity-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 helper (no HTTP call); for programmatic use, `import { validateTrilobioOptions } from "@pcc/trilobio"`.
pcc_trilobio_validate_scriptQuick 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 tcode commands. Returns { valid: boolean, errors: string[], warnings?: string[] }. Operators with `a…
pcc_update_node_statusUpdate 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.
pcc_update_requestUpdate 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.
pcc_verifier_healthReport 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.
propose_compositionPropose 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.
protocol_create_escrowCreate 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.
protocol_escrow_feesGet protocol fees collected from a specific escrow contract. Also returns whether the escrow was deployed via the protocol factory. Useful for auditing fee flows.
protocol_feeCalculate 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.
protocol_stateRead 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.
protocol_token_feesGet total protocol fees collected for a specific ERC-20 token address across all escrows. Returns raw wei amount and human-readable formatted value.
prove_registrationFast-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'.
provision_api_keyCALL 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.
publish_protocolPublish a draft protocol template, making it visible in the protocol library for others to discover and use.
raise_ip_disputeRaise a Story Protocol IP dispute against an asset. Provide evidence hash and reason.
record_episodeRecord a transfer episode for a node pair. Increments episode count toward VLA training threshold.
redeem_inviteOne-click agent onboarding with an invite code. Provisions wallet, identity, LLM access, and PCC tools in a single call.
register_capability_ipRegister a capability as a Story Protocol IP Asset. Returns an ipId and NFT token. The designer earns royalties whenever this capability is used.
register_job_evidence_ipRegister job evidence as a derivative IP asset on Story Protocol, linking it to the parent capability's IP. Operators earn royalties from derivative use.
reject_registrationReject a machine registration with a reason. The operator can see the rejection reason and resubmit.
release_milestoneRelease a milestone payment on-chain after the challenge window has expired. Returns transaction hash.
render_pcc_dashboardCompose 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.
reply_to_support_threadReply 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.
report_anomalyReport a detected anomaly — protocol failure, evidence mismatch, stuck job, or suspicious behavior. All agents on the network are notified.
report_protocol_failureReport a protocol failure — when a step in the evidence/escrow/verification pipeline breaks. System may auto-recover.
resolve_anomalyMark an anomaly as resolved with a resolution note.
respond_to_verificationSubmit a verifier's verdict for a verification request. Returns consensus state after this vote.
resume_protocol_runResume a paused protocol run from where it stopped.
retrieve_ipfsRetrieve raw data from IPFS by CID. Used to fetch archived evidence bundles from decentralized storage.
revoke_api_keyRevoke an API key permanently. The key will immediately stop working. You must own the key. Use list_api_keys to find the key ID.
save_dashboardSave 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 renders it — never hand-rolled HTML). WHEN to call this: only when the task needs a surface to watch/ap…
search_capabilitiesSearch capability templates by type or keyword. Returns templates with pricing, assurance tiers, and availability.
search_dashboardsDiscover 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 appear here.
search_spacesSearch for lab/workshop hosting spaces. Filter by size, access schedule, and other requirements.
send_diagnosticsUpload 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 uploads when the bundle is already prepared.
send_support_messageSend 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 expected.
setup_detectAuto-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.
setup_generate_configGenerate a KERNEL_CONFIG JSON from device descriptions. Tell it what machines you have and it produces the config ready to paste into your environment.
setup_register_deviceRegister a device in the database with adapter config and capabilities. Part of Step 3 in the onboarding flow.
setup_statusComprehensive setup status across 6 categories: gateway, database, adapters, chain, storage, identity. Use to confirm everything is green before going live.
setup_test_jobSubmit a test job to verify the full pipeline works end-to-end (Step 4 of onboarding). Returns job ID and result.
setup_validateValidate a kernel config (20+ checks: JSON structure, device connectivity, adapter compatibility). Returns validation errors and warnings.
stake_in_poolStake USDC or credits into a capability investment pool.
start_protocol_runStart execution of a protocol run that is in 'ready' or 'binding' state.
submit_attestationSubmit a verifier attestation for a milestone on-chain. Used by third-party verifiers (Bittensor subnet) to confirm evidence quality. Returns transaction hash.
submit_demandSignal 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.
submit_evidence_hashSubmit an evidence bundle hash for a milestone on-chain. Links the physical evidence to the on-chain settlement record. Returns transaction hash.
submit_feedbackSubmit a bug report, suggestion, or general feedback about the PCC network.
submit_for_human_verificationSubmit an evidence bundle for human verification. Selects a panel of verifiers from the network and returns assigned verifier IDs.
suggest_csd_templatesBidirectional 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 popularity-ordered top picks. After picking one, pass the chosen type to pcc-author-integration. Score-z…
system_telemetryRaw system state dump — actual DB rows for kernels, devices, jobs, evidence, registrations, capabilities, agent conversations, audit log. No fake numbers, no summaries.
test_operator_channelsFire 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).
update_dashboardModify 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.
update_job_statusUpdate a job's status and optional progress percentage. Used by kernels to report job progress.
update_operator_channelUpdate 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.
update_protocolUpdate an existing protocol template (must be in draft status). Returns updated name and version.
validate_protocolValidate a protocol template against a specific kernel — checks capability availability, transfer compatibility, and automation level feasibility.
verify_bountyVerify bounty completion by scoring the delivered capability against requirements.
verify_evidence_zkVerify a ZK proof by its proof ID. Checks the proof against its verification key and public inputs.
Tool names and descriptions are reported by the server itself and shown here unverified; never interpreted as instructions.