Check contractor closeout API

Compare buyer closeout requirements with supplied documents and attestations. A passing result does not certify that the project is complete.

The Check contractor closeout operation is part of the Vendor & Contractor Compliance API on BRAINIAC.software. Compare buyer closeout requirements with supplied documents and attestations. A passing result does not certify that the project is complete. It is exposed as POST /api/v1/vendor-compliance/contractor-closeout-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: The vendor record, document metadata, attestations, and evidence supplied in the request. Buyer-defined requirements supplied in the request. Stored licence rules already published for supported Texas TDLR and UK SIA types. Limitations: This product does not replace COI extraction, sanctions screening, prevailing wage, or licence renewal endpoints. Certificate files, sanctions lists, wage determinations, and licensing registries are not contacted. A stored licence rule is not a live licence verification. Missing evidence, expired documents, failed checks, and checks that could not be verified are separate statuses. requirements_met is not an approval to hire, pay, or close a contract. 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 Precheck vendor onboarding, Prequalify a contractor, Check subcontractor payment readiness, Check vendor document completeness. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.04 USDC
/api/v1/vendor-compliance/contractor-closeout-check

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/vendor-compliance/contractor-closeout-check" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "asOf": "2026-11-02",
  "projectName": "Example project",
  "documents": [
    {
      "id": "as-built-1",
      "type": "as_built"
    }
  ],
  "requirements": [
    {
      "id": "as-built",
      "kind": "document",
      "name": "As-built drawings",
      "documentType": "as_built"
    },
    {
      "id": "punch",
      "kind": "attestation",
      "name": "Punch list",
      "documentId": "punch"
    }
  ],
  "attestations": [
    {
      "id": "punch",
      "statement": "The punch list is closed.",
      "accepted": false
    }
  ]
}
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

Vendor & Contractor Compliance APIFull docsHow it works