API Services

Master Control Review Surface

Loading the live local MCP snapshot. Governance Operator can review and run governed actions on API Services.

Mutation enabledAPI ServicesLoading SnapshotAuto 30sUpdated Awaiting first syncFallback Snapshot0/5 Live SourcesCommercial surfaces remain mock-backed
API Services is in governed modeGovernance Operator can review and run privileged changes here. Mutation roles: Governance Operator / Finance Reviewer.
Live Local SnapshotLoading the live local MCP snapshot.
Last update: Awaiting first live snapshotAwaiting the first live snapshot.Auto-refresh runs every 30 seconds while this tab is active.

API Services

Governance-first API Services Pool view for package catalog, engine bindings, validation posture, and provider-scoped secret hygiene.

Governance OperatorMutation enabledOpen BillingOpen Engine Detail
3
API Service Packages
3
Tracked Credentials
0
Live API Leases
0
Usage Updates

API Services Pool

Approved API service packages that can be attached during governed provisioning.

3 Packages
Commerce baseline

Commerce API pool

Stripe + Cloudflare + Internal analyticsGovernance vault placeholderSaaS storefront / StableReady
Finance review bundle

Finance API pool

ERP bridge + Billing ledger + Audit feedGovernance vault placeholderSaaS and BaaS / StableReview
Operations integration bundle

Operations API pool

Notifications + Search + Workflow callbacksOperator-supplied secret setBaaS / StableReady

Engine Service Bindings

The service packages and production posture currently attached to managed engines.

3 Engines
  • 01
    POD Engine Alpha -> SaaS Growth Planprod-node-01 / 3 of 6 used · Live frontend / Governed adminPOD Storefront Core 2026.03.1
  • 02
    POD Engine Bravo -> SaaS Starter PlanPending placement · Staged frontend / Locked adminPOD Storefront Core 2026.03.1
  • 03
    POD Engine Charlie -> BaaS Scale Planprod-node-02 / 5 of 6 used · Live frontend / Review adminPartner Workflow Orchestrator 2026.02.h

Credential Vault

Masked provider credentials for DNS, registrar, billing, and API service workflows.

3 Visible
CredentialEngineProviderScopeStatusNext RotationValidation
POD Engine AlphaCloudflareDNS zone edit for acmeprints.exampleHealthyMarch 24, 2026Validated 2 hours ago
POD Engine BravoLogicBoxesDomain registration and nameserver syncRotation dueMarch 10, 2026Connectivity pending registrar cutover
POD Engine CharlieStripeInvoice sync and renewal reconciliationValidation failedMarch 14, 2026Validation failed 18 minutes ago

Selected Credential

Workflow detail, status posture, and masked secret continuity for the active credential.

Cloudflare
Cloudflare
Healthy
Validated 2 hours ago
March 24, 2026
cf_l...lphaFingerprint XALPHA | reveal disabled
February 24, 2026
  • 01
    DNS automation connectedThe token supports record template sync and validation record refresh.No scope mismatch detected.
  • 02
    Rotation window scheduledA routine rotation reminder is already attached to the next billing window.No immediate action required.

API Service Governance

Policy reminders that keep package attachment and secret handling inside the Governance Node model.

Policy
  • 01
    API service packages are assigned during provisioningThe Governance Node binds approved API service packages before an engine is deployed to a Production Node.This keeps integrations inside the governed deployment package.
  • 02
    Development Layer owns API service creationCodex and OpenClaw create the API services in the Development Layer, then the MCP attaches them from the API Services Pool.The MCP never authors provider integrations directly.
  • 03
    Secret handling remains package-awareCredential rotation and validation still occur at the secret level, but the package and engine binding context stay visible.This prevents operators from treating credentials as isolated strings.

Credential Hygiene Notes

Operational reminders for masked value handling, validation, and rotation continuity.

3 Notes
  • 01
    Credentials remain visibly scopedOperators can see provider ownership and intended surface without exposing raw secrets.
  • 02
    Validation health stays local-firstThe vault surface can represent connectivity, rotation, and revocation posture before live adapters land.
  • 03
    Secret masking remains intactOnly masked values are rendered in the local MCP seed data.