Enclave

Showing 25 of 36 from the live probe.

• Guide

  How-to guides for the Enclave platform (confidential compute for wasm apps, paid in USDC on Base). Topics: getting-started, deploy, publish, funding, attestation, volumes, networking, fees, cli. Start with getting-started.

• Platform Status

  Gateway health: live enclave count, fleet build metadata.

• Pricing

  Live platform rates and billing model (per-second USDC on Base; share prices for one GPU card / one CPU node, hardware sizing numbers used for share minimums).

• Availability

  Live fleet capacity: free GPU/CPU shares, hardware sizing minima (spec*), attached model volumes, and whether the fleet enforces the per-deployment WAF envelope.

• Gpu Capacity

  Live GPU partitioning detail (per-tenant SM grants / MPS view).

• List Apps

  List the on-chain app catalog (public). Optional substring query over slug/name/description.

• Get App

  One catalog app with all its versions: approval status, resource specs, ports, per-version config, publisher fee.

• App Reviews

  An app's on-chain ratings: the average, the star distribution, and the reviews themselves (1-5 stars with comments). Reviews come only from wallets that funded a deployment of the app, so the sample is people who ran it. Hidden (moderated) reviews are excluded from both the list and the average.

• List Deployments

  List a wallet's deployments: live fleet view (with a session token) merged with the on-chain ledger, so queued/stopped/unfunded work appears too. Ledger rows are public; pass owner to scope without a token.

• Get Deployment

  One deployment's record: status (awaiting_payment | queued | claimed | running | stopped | unfunded), rate, balance, time remaining, network addresses. Public ledger data; a session token adds the hosting enclave's live view.

• Deployment Logs

  Worker logs for a deployment (owner only; needs a session token from auth_login).

• Fleet Attestation

  The fleet's enclave attestation document (public). Verify CLIENT-SIDE with @tinfoilsh/verifier pinned to the repo EnclaveHost/enclave, or `enclave attest`; never trust this gateway's copy blindly.

• Deployment Attestation

  The attestation of the enclave hosting one deployment (public — no token needed; an owner token adds a fresh GPU report over a caller nonce). Verify client-side; see guide topic "attestation".

• Account

  Account summary for the signed-in wallet: payment addresses (forwarder, USDC), deployment counts. Needs a session token.

• Auth Nonce

  Step 1 of sign-in: fetch the SIWE message for a wallet. Sign it locally with personal_sign, then call auth_login. Only needed for owner-scoped reads (logs, account, live status detail); all transactions work without a session.

• Auth Login

  Step 2 of sign-in: exchange the signed SIWE message for a session token (ES256, minted inside the enclave). Pass the token to owner-scoped tools, or set it as this MCP server's Authorization header.

• Claim Hint

  Nudge the fleet to claim a funded on-chain deployment right now (otherwise the ~60s sweep finds it). Advisory and unauthenticated. Optional enclave pins the hint to one named box (see /enclaves) — the WASIp3-canary and placement path; the ledger stays an open queue either way.

• Restart Deployment

  Restart a running deployment in place (owner only; needs a session token).

• Terminate Hosted

  Tear down the hosted instance promptly after an on-chain stop (owner only; needs a session token). On-chain stop itself is build_stop; without this the runner tears it down on its next ledger pass anyway.

• Upload Token

  Trade a wallet signature for a one-time IPFS upload token (publishing step). Sign EXACTLY `enclave-upload:<sha256hex>:<expiry>` (personal_sign; expiry = unix seconds within +600s), then POST the bytes to https://ipfs.enclave.host/add-wasm (or /add-image) with headers x-upload-address/-expiry/-token. See guide topic "publish".

• Set Secrets

  Store/update a deployment's PRIVATE env vars (S3 keys, API tokens) on the relay — never on the public chain; the enclave holding the lease injects them into the app at every start (restart_deployment applies changes now), and $NAME/${NAME} placeholders inside the deployment's App config STRING values resolve from them at launch (so a public config can reference private values). payload is a JSON STRING like '{"set":{"NAME":"value"},"del":["NAME"],"clear":false}' — sign EXACTLY `enclave-secrets:p

• Get Secrets

  Read back a deployment's relay-stored secrets (names AND values — owner only). Sign EXACTLY `enclave-secrets:get:<id>:<expiry>` (personal_sign, the owner wallet, expiry = unix seconds within +600s; single-use).

• Plan Deploy

  Validate and price a deployment of a catalog app, returning the unsigned create transaction. Runs the same gates the CLI does: approval, share minimums on the fleet's hardware, the platform GPU cap, and the publisher-fee snapshot. After the create tx mines, the id is topics[1] of the Created event; then build_fund and claim_hint.

• Build Fund

  Unsigned funding transactions for a deployment: { usd } returns USDC approve + fund (whole cents; billed per second), { eth } returns one payable fundEth (credited at the live Chainlink rate). Anyone can fund any deployment.

• Build Host Fund

  Unsigned plain ETH transfer that GASES a self-hosted (metal) enclave's operator EOA — the in-config key that signs the box's register/heartbeat/claim transactions (metal/PROTOCOL.md; `enclave host init` prints the address). Not a payment to anyone: the ETH is consumed as Base network fees over months, and earnings never touch this key (they sweep to the box's payoutAddress). Once funded, the box registers itself and appears as serving.