Detect construction delay events API

Collect recorded delay rows and daily-report delay wording, and separately label impacts inferred from baseline versus actual dates. Liability is not determined.

The Detect construction delay events operation is part of the Construction Site Operations API on BRAINIAC.software. Collect recorded delay rows and daily-report delay wording, and separately label impacts inferred from baseline versus actual dates. Liability is not determined. It is exposed as POST /api/v1/construction-site-operations/delay-event-detect 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 daily reports Baseline and actual schedules RFIs Site instructions Delivery records Limitations: Dates, parties, and quantities are copied only from labeled fields. Recorded events are distinguished from inferred schedule impact. Delays, entitlements, and liability are never invented or decided. Unresolved RFIs and missing deliveries use supplied due/expected dates only. No construction account or project system is accessed. 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 Parse construction daily reports, Analyze site progress, Track requests for information, Extract site instructions. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.04 USDC
/api/v1/construction-site-operations/delay-event-detect

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/construction-site-operations/delay-event-detect" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "asOf": "2026-11-10",
  "activities": [
    {
      "id": "A-1",
      "name": "Foundations",
      "baselineEnd": "2026-11-05",
      "actualEnd": "2026-11-08"
    }
  ],
  "delays": [
    {
      "id": "D-1",
      "date": "2026-11-03",
      "activityId": "A-1",
      "days": 2,
      "reason": "rain stoppage",
      "recorded": true
    }
  ],
  "reports": [
    {
      "id": "DR-1",
      "date": "2026-11-03",
      "text": "Work delayed by rain",
      "activityId": "A-1"
    }
  ]
}
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

Construction Site Operations APIFull docsHow it works