Calculate deployment blast radius API

Walk a caller-supplied service dependency graph from proposed changes and list upstream and downstream services that may be affected. No CI/CD system is contacted.

The Calculate deployment blast radius operation is part of the Config Hardening & Release Operations API on BRAINIAC.software. Walk a caller-supplied service dependency graph from proposed changes and list upstream and downstream services that may be affected. No CI/CD system is contacted. It is exposed as POST /api/v1/devops/deployment-blast-radius 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, Check rollback feasibility, 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/deployment-blast-radius

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/devops/deployment-blast-radius" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "services": [
    {
      "id": "api"
    },
    {
      "id": "worker"
    },
    {
      "id": "db"
    },
    {
      "id": "edge"
    }
  ],
  "dependencies": [
    {
      "from_service_id": "edge",
      "to_service_id": "api",
      "kind": "runtime"
    },
    {
      "from_service_id": "api",
      "to_service_id": "db",
      "kind": "data"
    },
    {
      "from_service_id": "worker",
      "to_service_id": "db",
      "kind": "data"
    }
  ],
  "changes": [
    {
      "id": "ch1",
      "service_id": "db",
      "change_kind": "schema",
      "breaking": true
    }
  ],
  "direction": "both"
}
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