Veriglyph
Spec loopSandboxTriageInventory
Contact
Veriglyph
FAQCheckerInventorySpec diffsDraftsWaitlistSign inCreate your account

Veriglyph is a North Carolina company, based in Pitt County.

Veriglyph

Veriglyph / public docs

API reference

documentation
Back to site

Reference map

01
  • 01Overview
  • 02Checker
  • 03Documentation lookup
  • 04Evidence
  • 05Spec changes
  • 06Authentication & requests

Public reference material for building with Veriglyph.

public docs
API version
v1
Last updated
September 12, 2026
documentation endpoint
public · no auth

Documentation lookup

Retrieve the current Truth Score detail for one documented browser API. The response combines the overall page score with supporting signals, known discrepancies, and the evidence claims behind each signal.

GET
/api/inventory/pages/[slug]application/json response

01 / request

Path parameter

Look up one page by its required slug. URL-encode the value when it contains characters that are not safe in a path segment. This endpoint accepts no request body and has no query parameters.

Route parameters
There is no JSON body for this GET request.
FieldTypeRequiredDetails
slugstringYesRequired path segment; URL-encode as needed. No body or query parameters.

02 / success · 200

Response shape

A found page returns application/json matching InventoryPageDetail. Scores are numbers in the documented ranges; timestamps are Unix milliseconds generated from the current inventory record.

InventoryPageDetail
Top-level response fields
FieldTypeDescription
pageInventoryScoreCardOverall page identity, score, status, evidence status, verification timestamp, and discrepancy count.
signalsInventorySignalRow[]The spec, browser, examples, and compatibility signal rows.
discrepanciesInventoryDiscrepancy[]Known issues linked to an evidence claim when one is available.
evidenceInventoryEvidenceAggregate evidence status and the detailed claim records behind each signal.
page
InventoryScoreCard
slug · namestring · The requested slug and its display name.
scoreInteger from 0 to 100.
statusVerified · Drift detected · Needs review · In review · Unverified
evidenceStatusVerified · Partially verified · Not tested · Conflict detected
lastVerifiedAt · discrepancyCountUnix-millisecond integer timestamp · non-negative integer.
signals[]
InventorySignalRow
id · labelspec · browser · examples · compat · plus a display label.
score · weightScore is 0–100; weight is 0–1.
evidenceUrlOptional string; omitted when the signal has no source URL.
explainerHuman-readable explanation of how the signal was scored.
discrepancies[]
InventoryDiscrepancy
id · summaryString identifier and human-readable description.
sourceUrlstring or null.
severitydrift · additive · editorial.
claimIdspec · browser · examples · compat · or null.
evidence
InventoryEvidence
statusOne of Verified, Partially verified, Not tested, or Conflict detected.
claimsArray of InventoryEvidenceClaim records; each claim has the fields listed below.
claim id · label · status · scoreClaim id is spec, browser, examples, or compat; label is a string; status uses the evidence status enum; score is 0–100.
claim sources and detailsspecificationSource, specificationSection, specificationRevision, browserVerificationStatus, browser, browserVersion, exampleResult, compatibilityDetail, and gap are string | null. URL fields specificationLink, browserSource, exampleSource, and compatibilitySource are URL string | null. exampleLastVerifiedAt is integer | null.

03 / example

Request and response

websocket-api is a seeded example slug. The response below is an illustrative shape: score, discrepancy totals, and verification timestamps are generated from the live inventory record and can change between requests.

curl request
curl "${APP_URL}/api/inventory/pages/websocket-api"

200 application/json · illustrative
{
  "page": {
    "slug": "websocket-api",
    "name": "WebSocket API",
    "score": 87,
    "status": "Verified",
    "evidenceStatus": "Partially verified",
    "lastVerifiedAt": 1770000000000,
    "discrepancyCount": 1
  },
  "signals": [
    {
      "id": "spec",
      "label": "Specification",
      "score": 92,
      "weight": 0.3,
      "evidenceUrl": "https://example.com/source",
      "explainer": "Illustrative signal explanation."
    }
  ],
  "discrepancies": [],
  "evidence": {
    "status": "Partially verified",
    "claims": [
      {
        "id": "spec",
        "label": "Specification",
        "status": "Verified",
        "score": 92,
        "specificationSource": "Illustrative source",
        "specificationSection": null,
        "specificationRevision": null,
        "specificationLink": "https://example.com/spec",
        "browserVerificationStatus": null,
        "browser": null,
        "browserVersion": null,
        "browserSource": null,
        "exampleResult": null,
        "exampleSource": null,
        "exampleLastVerifiedAt": null,
        "compatibilitySource": null,
        "compatibilityDetail": null,
        "gap": null
      }
    ]
  }
}

04 / errors

Not found

Unknown slugs return 404 with the exact JSON error body below. No login or other authorization is required for either the successful lookup or this not-found response.

404 application/json
{
  "error": "not_found"
}