Grade infrastructure config hardening API

Grade a caller-supplied Dockerfile, Kubernetes YAML document, or Terraform JSON file for root execution, exposed ports, missing resource limits, and insecure defaults. Parsing stays in memory. The file is not applied, fetched, or stored.

The Grade infrastructure config hardening operation is part of the Infrastructure Config Hardening API on BRAINIAC.software. Grade a caller-supplied Dockerfile, Kubernetes YAML document, or Terraform JSON file for root execution, exposed ports, missing resource limits, and insecure defaults. Parsing stays in memory. The file is not applied, fetched, or stored. It is exposed as POST /api/v1/devops/config-hardening-grade 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 YAML, or Terraform JSON processed locally Limitations: The grade is a baseline document check. It is not a cluster scan, image scan, or proof that a deployment is safe. Kubernetes is read as a YAML subset: maps, lists, scalars, and block scalars. Anchors, tags, and tabs are not expanded. Terraform is read as JSON. HCL is not parsed. A missing field is an omitted setting in the supplied file. It is not a live cluster default. No cloud API, cluster, or registry is contacted. 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 the other resources on the product page. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.04 USDC
/api/v1/devops/config-hardening-grade

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/devops/config-hardening-grade" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "config": "FROM ubuntu:latest\nUSER root\nEXPOSE 22\nRUN curl https://example.com/install.sh | sh\nCMD [\"bash\"]\n"
}
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

    Infrastructure Config Hardening APIFull docsHow it works