Compliance Checking

What is compliance checking?

Compliance checking answers a simple question: “Does our project documentation satisfy this requirement?”

You provide a requirement (e.g., “The site must have a documented fire safety plan”) and Pyramid Check searches your project documents for evidence, then delivers a verdict: compliant or non-compliant, with citations.

Two ways to check

Quick Verify — one requirement at a time

POST /api/v2/check/verify

Submit a single requirement and get an immediate verdict. The fastest way to check something.

Requirement: "Emergency exits must be clearly marked"
        │
        ▼
┌──────────────────────────────────────────┐
│ Search project documents for evidence     │
│ Analyze whether the requirement is met    │
│ Generate verdict with citations           │
└──────────────────────────────────────────┘
        │
        ▼
Verdict: Compliant
Confidence: 92%
Evidence: "Section 4.3 of the Safety Plan states..."
Sources: Safety-Plan-2026.pdf, page 12

Response structure:

1
{
2
  "data": {
3
    "verdict": "compliant",
4
    "confidence": 0.92,
5
    "evidence": "Section 4.3 of the Safety Plan states that all emergency exits...",
6
    "explanation": "The project documentation includes a detailed emergency exit marking plan...",
7
    "recommendation": null,
8
    "sources": [
9
      { "title": "Safety-Plan-2026.pdf", "relevance": 0.95 }
10
    ]
11
  }
12
}

Best for: Spot checks, quick lookups, integrating compliance into other workflows (e.g., an Excel column that shows pass/fail).

Compliance Runs — many requirements at once

For audits and systematic reviews, use compliance runs to check dozens or hundreds of requirements in a single batch.

The workflow:

1. Create a run          2. Trigger processing       3. Get results
   (define requirements)    (start the checks)          (per-requirement verdicts)
POST /check/runs         POST /check/runs/{id}       GET /check/runs/{id}
                              /trigger                GET /check/runs/{id}
                                                           /requirements

$
curl -X POST https://api.pyramid-ai.com/api/v2/check/runs \
>
  -H "Authorization: Bearer pai_live_YOUR_KEY" \
>
  -H "Content-Type: application/json" \
>
  -d '{
>
    "project_id": "YOUR_PROJECT_ID",
>
    "name": "Q2 2026 Fire Safety Audit",
>
    "requirements": [
>
      "The site must have a documented fire safety plan",
>
      "Fire extinguishers must be inspected monthly",
>
      "Emergency evacuation routes must be posted on every floor",
>
      "Fire drills must be conducted quarterly"
>
    ]
>
  }'

$
curl -X POST https://api.pyramid-ai.com/api/v2/check/runs/RUN_ID/trigger \
>
  -H "Authorization: Bearer pai_live_YOUR_KEY" \
>
  -H "Content-Type: application/json" \
>
  -d '{}'

$
curl https://api.pyramid-ai.com/api/v2/check/runs/RUN_ID \
>
  -H "Authorization: Bearer pai_live_YOUR_KEY"

1
{
2
  "data": {
3
    "status": "processing",
4
    "total_requirements": 4,
5
    "processed_requirements": 2,
6
    "passed_requirements": 1,
7
    "failed_requirements": 1
8
  }
9
}

$
curl https://api.pyramid-ai.com/api/v2/check/runs/RUN_ID/requirements \
>
  -H "Authorization: Bearer pai_live_YOUR_KEY"

Best for: Quarterly audits, tender compliance reviews, systematic gap analysis, regulatory reporting.

When to use which

Understanding confidence scores

The confidence score tells you how certain the AI is about its verdict:

Tips for better compliance results

• Write clear requirements — “Fire exits must be marked with illuminated signs” is better than “fire exit compliance”
• Upload the right handbooks — if you’re checking against a specific standard, make sure that standard’s document is in the project
• One requirement per item — don’t combine multiple checks into one requirement. “Fire exits must be marked AND inspected monthly” should be two separate requirements
• Use runs for audits — individual verify calls are great for spot checks, but runs give you a structured report