Physical Capability Cloud

Activate an approved registration, making the operator's equipment live on the network and ready to accept jobs.

AI analysis of machine documentation. Upload docs to get suggested capabilities, extracted specs, materials, and tolerances.

Approve a submitted machine registration. Moves it from 'submitted' to 'approved' status, enabling the operator to activate and start accepting jobs.

Archive an encrypted evidence bundle to IPFS and store the resulting CID in the database. Idempotent — returns existing CID if already archived.

Archive an evidence bundle to IPFS/Storacha for permanent decentralized storage. Returns the content-addressed CID.

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 neutral. Returns the channel record with a generated id.

Build and submit a capability contract with on-chain milestone escrow. Returns job ID and escrow address.

Calculate price for a capability configuration. Returns base price, tier premiums, and estimated total cost.

Validate an invite code before redeeming it. Returns whether the code is valid and what it includes.

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.

Ask to take on a bounty as the authenticated operator. No gateway route creates a bounty, so the request finds none (409); no bounty is funded or pays anything.

Claim an IP asset's recorded revenue. Story Protocol (now The DATA Foundation). These tools make no on-chain call: nothing is registered, claimed or disputed on chain. Nothing is paid out: any amount or transaction hash in the reply is a placeholder.

Operator claims an investment pool reward after capability verification.

Close an investment pool to new stakes. Pool enters sunset phase.

Create a Merkle commitment for an evidence bundle hash. Used as the first step in ZK proof generation for Tier 3 assurance.

Convert an existing bounty into an investment pool. Allows community staking toward the bounty's capability.

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.

Create an investment pool for a capability bounty.

Register a new Shop Kernel (physical site) on the PCC network. Part of Step 2 in the onboarding flow.

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`.

File a dispute against the consensus verdict. Only verifiers who submitted a response can dispute. Requires additional evidence CID.

Set revenue splits for an IP asset among stakeholders (designer, operator, verifier, assembler, curator). Splits must sum to 100. Story Protocol (now The DATA Foundation). These tools make no on-chain call: nothing is registered, claimed or disputed on chain. No revenue is paid from these splits.

Manually emit a telemetry event for a job pipeline phase. Used by kernels and agents to report execution progress.

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 dev/test. Re-executing an already-run composition replays the stored result (idempotent — reputation deltas are applied exactly once).

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.

List currently active jobs with their current pipeline phase and telemetry status.

Get anomalies involving a specific agent, plus their trust impact score.

Get aggregate anomaly statistics — total, unresolved, by severity, by category.

Get the bounty leaderboard. No gateway route creates or verifies a bounty, so expect an empty list.

Get configuration options for a capability type: parameter groups, each parameter's definition, and a base price hint. It includes no assurance tiers. Use before calling calculate_price.

Get IPFS CIDs for a bundle — returns the primary CID, metadata CID, and Filecoin deal ID if available.

Get the IP record PCC holds for a capability by its capability ID. Story Protocol (now The DATA Foundation). These tools make no on-chain call: nothing is registered, claimed or disputed on chain. Any id or transaction hash in it is a placeholder.

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.

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).

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.

Read full on-chain escrow state with all milestone details from the blockchain. More detailed than get_escrow for on-chain contracts.

Read dispute state for a specific milestone from the blockchain.

Get on-chain event history for an escrow contract. Returns funding, release, dispute, and bond events.

Get an encrypted evidence bundle by its bundle ID. Returns the encrypted payload and key capsules.

Get the IP lineage PCC has recorded for an asset: parent capabilities and derivative job records. Story Protocol (now The DATA Foundation). These tools make no on-chain call: nothing is registered, claimed or disputed on chain.

Get the revenue PCC has recorded for an IP asset. Story Protocol (now The DATA Foundation). These tools make no on-chain call: nothing is registered, claimed or disputed on chain. No revenue has been paid: any figure in the reply is a placeholder.

Get job details including progress, evidence bundles, and milestones.

Get full event timeline for a specific job — all pipeline phase transitions with timings and metadata.

Get kernel details including full capability objects, devices, and queue.

List all devices registered under a specific kernel, including adapter configs and device types.

List all jobs submitted to a specific kernel, including job status and progress.

Get sensor channels for a specific kernel. Returns live channel descriptors.

Get Lit Protocol access conditions for a Lit-encrypted evidence bundle. Returns the conditions that gate decryption.

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).

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.

Answers 501 not_available: operator earnings history is not recorded on this gateway. Per-job payment state is at GET /api/jobs/:jobId/execution.

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.

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` | `unconfigured`. Public — operator slug is non-secret and the response carries no credentials (channel `credentialRef` values are vault references, not secrets).

Get details of a specific investment pool including stakes, status, and revenue share terms.

Check earnings from capability investment pools for a staker address.

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.

Get details of a specific machine registration by ID, including capabilities, pricing, operator info, and current status.

List all registered sensor channels across kernels. Returns channel descriptors with units and ranges.

Get settlement epoch history showing past batch settlements with timing and operation counts.

Get settlement pipeline status including pending operations count, total value queued, and smart account address.

List the gateway's verification oracles (uma, chainlink and eigenlayer, in the order it tries them): each one's name, whether it's available, its verification count since the gateway started, and its average score.

The gateway's agent bridge status: whether its in-process agents started, their names and roles, and the bridge's conversation and recent-message counts.

Query structured logs with filters for level, source, jobId, kernelId, time range, and full-text search.

Get aggregate pipeline telemetry statistics including phase timings, success rates, and throughput metrics across all jobs.

Read the ERC-20 token allowance granted by an owner to a spender from the blockchain.

Read an ERC-20 token balance for an account address from the blockchain.

Get demand aggregated by capability type. The gateway doesn't publish demand yet: it answers an empty list marked `suppressed`.

List all unresolved anomalies on the network. Filter by severity, category, or target agent.

Get pending verification assignments for a verifier node. Returns requests this verifier has been assigned but not yet responded to.

Get verification status for a request. Returns vote tally, consensus state, dispute list, and pending response count.

Check if on-chain write operations are enabled (requires PCC_GATEWAY_PRIVATE_KEY to be configured). Returns write status and signer address.

Grant a new recipient access to an encrypted evidence bundle. Creates a re-encrypted key capsule for the recipient.

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).

Send a per-kernel heartbeat to keep the kernel marked online. Used by pcc-node daemons as an alternative to the operator relay heartbeat.

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.

List active and completed settlement batches.

List bounties. No gateway route creates a bounty and none is funded, so expect an empty list; no bounty pays anything.

List all capability types registered on the network (FDM, SLA, CNC, HPLC, etc.) with metadata.

List escrow contracts with their milestone counts. Optionally filter by escrow status.

List encrypted evidence bundles stored in the gateway.

List all evidence access grants for an address. Returns bundles the address has been granted access to.

List all jobs with status. Optionally filter by kernelId or status.

List all Shop Kernels on the network with status and capability types. Optionally filter by status.

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.

List all investment pools. Optionally filter by status or capability type.

List all machine registrations on the network. See pending, approved, active, and rejected registrations. Public endpoint — no auth required.

Decrypt a Lit Protocol-encrypted evidence bundle using a Lit auth signature. Returns the decrypted bundle payload.

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.

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.

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.

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.

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.

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. Operator identity proof for operate is completed by WP-A (DECISIONS items 136 and 138).

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 proof for operate is completed by WP-A (DECISIONS items 136 and 138). The pcc-node daemon does not call it: it takes no jobs.

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 kernelId cannot choose the authorization target. No credentials gets 401 before the job read; a job without a kernel gets 403 for a non-admin. Contains device ID, execution timestamp, result payload, and event timeline. Success is a receipt with stored: true naming this jobId. HTTP 200 with stored: false means nothing was stored: never follow it with status completed.

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 gets 403 for a non-admin. Operator identity proof for operate is completed by WP-A (DECISIONS items 136 and 138). The node path finishes a job in two calls: submit its evidence (POST /api/operator/evidence, posted with the kernel's proven operator wallet authority, decide), and only if that receipt says stored: true for this jobId, set status completed here. HTTP 200 alone is not enough: the relay answers 200 with stored: false when it could not store the evidence (an unknown job, a storage failure); then set failed with the reason evidence_not_stored. On the current gateway, completed marks the job done and its timeline then says settled, but the escrow is not released yet (board G1). Do not call pcc_job_complete after this: it answers 409.

Record a royalty payment to an IP asset. Story Protocol (now The DATA Foundation). These tools make no on-chain call: nothing is registered, claimed or disputed on chain. No tokens move, and any transaction hash in the reply is a placeholder.

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.

Cancel a capability request. Cancelled requests cannot be updated, decomposed, or published. This is a soft delete — the request remains visible with status 'cancelled'.

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).