CertifiedData.io
Workflows
PRODUCTION
Production — paid plan requiredBuild+ plan required

Cross-pillar orchestration

Chain datasets, decisions, and commerce into reproducible signed pipelines. Scheduled or manual trigger. Each run produces a certificate. Results are publicly verifiable.

V1 execution constraint

In V1, only the sandbox_conversion source type completes end-to-end. Other workflow types (scheduled generation, cross-pillar chains) can be created and configured but execution is gated for V2. Use the direct APIs (dataset generation, decision logging, commerce) for production workloads today.

Workflow types

sandbox_conversion
Sandbox conversion
Available (V1)

Converts a sandbox.cert.v1 artifact to a persistent cert.v1 by claiming and upgrading the sandbox certificate once an account is authenticated. The only workflow source type that completes end-to-end in V1.

  1. 1.Generate sandbox dataset → receive scert_xxxx
  2. 2.Authenticate (or create free account)
  3. 3.POST /api/sandbox/claim-and-upgrade with scert_xxxx
  4. 4.Returns cert.v1 with permanent registry listing and verify URL
dataset_certify_log
Dataset → certify → decision log
Planned (V2)

Generate a certified dataset, then log a decision that references it via artifactReference. Creates a full provenance chain from dataset to decision.

  1. 1.Generate dataset → cert issued (cert_xxxx)
  2. 2.Run inference or decision against dataset
  3. 3.POST /v1/decisions with artifactReference: cert_xxxx
  4. 4.Decision record cryptographically linked to dataset certificate
generate_publish_feed
Generate → certify → public feed
Planned (V2)

Generate a certified dataset and automatically publish a certificate entry to the transparency log and registry. Makes the artifact publicly discoverable and verifiable.

  1. 1.Generate with cert_level: cert.v1+
  2. 2.Certificate auto-published to registry
  3. 3.Transparency log entry created
  4. 4.Public verify URL available immediately
commerce_receipt_verify
Commerce → receipt → verify
Available (API)

Run an agent-commerce transaction, receive a signed receipt, and expose the verify URL for downstream consumers. Not a workflow object — available directly from the commerce API today.

  1. 1.POST /v1/receipts/quote → quote_id
  2. 2.POST /v1/receipts/authorize → auth record
  3. 3.POST /v1/receipts/execute → signed receipt
  4. 4.GET /api/payments/verify/:receipt_id → verification

Workflow API

Sandbox conversion (V1 — available today)
# V1 — sandbox_conversion (the only completed workflow type today)
curl -X POST https://certifieddata.io/api/sandbox/claim-and-upgrade \
  -H "Authorization: Bearer $CERTIFIEDDATA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"sandbox_cert_id":"scert_xxxx"}'
Create a scheduled workflow (Build+)
curl -X POST https://certifieddata.io/api/workflows \
  -H "Authorization: Bearer $CERTIFIEDDATA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Weekly fraud dataset",
    "source": {
      "type": "template",
      "templateId": "fraud_detection",
      "rows": 5000,
      "engine": "gaussian"
    },
    "schedule": "0 9 * * 1",
    "cert_level": "cert.v1"
  }'
Trigger + inspect a run
# Trigger a manual run
curl -X POST https://certifieddata.io/api/workflows/$WORKFLOW_ID/run \
  -H "Authorization: Bearer $CERTIFIEDDATA_API_KEY"

# Get workflow + last 20 runs
curl "https://certifieddata.io/api/workflows/$WORKFLOW_ID" \
  -H "Authorization: Bearer $CERTIFIEDDATA_API_KEY"

API surface

Method + pathPlan
POST /api/workflowsBuild+
GET /api/workflowsBuild+
GET /api/workflows/:idBuild+
POST /api/workflows/:id/runBuild+
GET /api/artifacts/feedFree+
POST /api/sandbox/claim-and-upgradeFree+
Agent Workflows — Cross-Pillar Orchestration | CertifiedData | CertifiedData