# BRAINIAC Rollback Feasibility Check

> BRAINIAC Rollback Feasibility Check is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.04/call, status unknown (last checked 2026-11-14).

Analyzes service versions, migrations, and dependency compatibility to determine whether a deployment can be safely rolled back, returning a list of blockers and a feasibility verdict.

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/devops/rollback-feasibility-check?utm_source=zero.xyz
- Price: $0.04/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-rollback-feasibility-check-ffe56649
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PRTEuwTYWNy4kaQqXeAYL

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability brainiac-rollback-feasibility-check-ffe56649 -d '<json body>'
```

Example prompt: Before we deploy, check if we can safely roll back: service 'api' is moving from v1.2.0 to v1.3.0 (previous was v1.1.0), it depends on service 'db' going from v3.0.0 to v3.1.0, migration 'm42' on 'db' is a rewrite and marked irreversible, and our max acceptable RTO is 30 minutes.

## When to prefer this

Use this endpoint when you need a fast, stateless pre-flight check before deploying a set of services and want to know whether rollback is safe — especially when migrations, cross-service dependencies, or RTO constraints are involved. It is purely analytical (no deployment platform is contacted), making it safe to run speculatively. Prefer this over manual review when you have structured version and migration metadata and want a deterministic blocker report with remediation hints.

## Known failure modes

- Missing required fields (service_id, current_version, target_version) returns a validation error
- Supplying no previous_version causes a 'missing_previous_version' high-severity blocker
- Irreversible migrations generate 'irreversible_migration' high blockers that set feasible=false
- Exceeding maxItems limits (500 versions, 1000 migrations, 2000 compatibility) may cause rejection
- Payment failure via x402 prevents the call from completing
- Malformed version strings (exceeding 80 chars) or empty strings will fail schema validation

## How this service works

Pay-per-call APIs for AI agents: OFAC sanctions screening, compliance checks, token security, and Base chain data via x402. No account. Fixed USDC price. MCP-ready.

## Output

Returns a JSON object with a 'feasible' boolean verdict, a 'summary' (total services, blocker counts by severity), and a 'blockers' array — each blocker has a code (e.g. irreversible_migration, missing_previous_version), severity (high/medium), affected service_id, human-readable evidence, remediation guidance, and optional migration or compatibility IDs. Also includes explanatory notes on the feasibility logic used.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "versions": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "service_id",
     "current_version",
     "target_version"
    ],
    "properties": {
     "service_id": {
      "type": "string",
      "maxLength": 120,
      "minLength": 1
     },
     "target_version": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1
     },
     "current_version": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1
     },
     "previous_version": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1
     }
    },
    "additionalProperties": false
   },
   "maxItems": 500,
   "minItems": 1
  },
  "migrations": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "id",
     "service_id",
     "direction",
     "reversible"
    ],
    "properties": {
     "id": {
      "type": "string",
      "maxLength": 120,
      "minLength": 1
     },
     "detail": {
      "type": "string",
      "maxLength": 500,
      "minLength": 1
     },
     "direction": {
      "enum": [
       "expand",
       "contract",
       "rewrite",
       "other"
      ],
      "type": "string"
     },
     "reversible": {
      "type": "boolean"
     },
     "service_id": {
      "type": "string",
      "maxLength": 120,
      "minLength": 1
     }
    },
    "additionalProperties": false
   },
   "maxItems": 1000
  },
  "compatibility": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "id",
     "service_id",
     "depends_on_service_id",
     "compatible_with_rollback"
    ],
    "properties": {
     "id": {
      "type": "string",
      "maxLength": 120,
      "minLength": 1
     },
     "service_id": {
      "type": "string",
      "maxLength": 120,
      "minLength": 1
     },
     "max_version": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1
     },
     "min_version": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1
     },
     "depends_on_service_id": {
      "type": "string",
      "maxLength": 120,
      "minLength": 1
     },
     "compatible_with_rollback": {
      "type": "boolean"
     }
    },
    "additionalProperties": false
   },
   "maxItems": 2000
  },
  "max_rto_minutes": {
   "type": "integer",
   "maximum": 525600,
   "minimum": 0
  },
  "recovery_procedures": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "service_id",
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "summary": {
   "blockers": 4,
   "services": 2,
   "high_blockers": 3
  },
  "blockers": [
   {
    "code": "missing_previous_version",
    "evidence": [
     "Service db has no previous_version to roll back to."
    ],
    "severity": "high",
    "service_id": "db",
    "remediation": "Supply previous_version for every service in the deployment set."
   },
   {
    "code": "irreversible_migration",
    "evidence": [
     "Migration m1 is marked reversible=false (rewrite)."
    ],
    "severity": "high",
    "service_id": "db",
    "remediation": "Defer the deployment until a reversible expand/contract path exists, or accept that rollback is blocked.",
    "migration_id": "m1"
   },
   {
    "code": "missing_recovery_procedure",
    "evidence": [
     "No recovery_procedures row was supplied for db."
    ],
    "severity": "medium",
    "service_id": "db",
    "remediation": "Document a rollback procedure for this service before deploying."
   },
   {
    "code": "incompatible_with_rollback",
    "evidence": [
     "Compatibility constraint c1 sets compatible_with_rollback=false for api depending on db."
    ],
    "severity": "high",
    "service_id": "api",
    "remediation": "Keep forward-compatible contracts or stage a dual-write/dual-read window before cutting over.",
    "compatibility_id": "c1",
    "depends_on_service_id": "db"
   }
  ],
  "feasible": false,
  "explanations": [
   "Rollback feasibility uses only supplied versions, migrations, compatibility flags, and recovery procedures.",
   "feasible is false when any high-severity blocker is present. No deployment platform is contacted."
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-rollback-feasibility-check-ffe56649/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.brainiac.software](https://www.zero.xyz/host/www.brainiac.software/llms.txt)
