Check rollback feasibility API

Evaluate whether a proposed deployment can be rolled back using supplied versions, migration reversibility, compatibility constraints, and recovery procedures. No deployment platform is queried.

The Check rollback feasibility operation is part of the Config Hardening & Release Operations API on BRAINIAC.software. Evaluate whether a proposed deployment can be rolled back using supplied versions, migration reversibility, compatibility constraints, and recovery procedures. No deployment platform is queried. It is exposed as POST /api/v1/devops/rollback-feasibility-check and priced at $0.04 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Caller-supplied Dockerfile/Kubernetes/Terraform text, dependency graphs, versions, migrations, monitoring, and release checklists processed locally Limitations: Config grading is a document check. It is not a cluster scan or proof a deployment is safe. Blast radius, rollback, and readiness use only supplied graphs and checklists. No CI/CD or cloud API is contacted. Kubernetes is read as a YAML subset. Terraform is read as JSON, not HCL. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Grade infrastructure config hardening, Calculate deployment blast radius, Audit release readiness. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.04 USDC
/api/v1/devops/rollback-feasibility-check

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/devops/rollback-feasibility-check" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "versions": [
    {
      "service_id": "api",
      "current_version": "1.2.0",
      "target_version": "1.3.0",
      "previous_version": "1.2.0"
    },
    {
      "service_id": "db",
      "current_version": "schema-9",
      "target_version": "schema-10"
    }
  ],
  "migrations": [
    {
      "id": "m1",
      "service_id": "db",
      "direction": "rewrite",
      "reversible": false,
      "detail": "Drops legacy column"
    }
  ],
  "compatibility": [
    {
      "id": "c1",
      "service_id": "api",
      "depends_on_service_id": "db",
      "compatible_with_rollback": false
    }
  ],
  "recovery_procedures": [
    {
      "service_id": "api",
      "procedure": "Redeploy previous image",
      "automated": true,
      "rto_minutes": 15
    }
  ],
  "max_rto_minutes": 30
}
JSON

An unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.

FAQ

  • Do I need an API key? No. Pay the listed USDC amount with x402.
  • What network? Base (eip155:8453), USDC.
  • Is this an official determination? No. Results are for human review against the cited sources.

Related APIs

Config Hardening & Release Operations APIFull docsHow it works