mocop
Browse · Docs · Guide · Analyze

Incident Library API

API by Benchlet · rest

Public post-incident reports, written up one case at a time and reviewed, for engineers who are looking at a failure right now and for AI tools that answer them. Every case has a stable id (IL-0001 and so on), a title, the organisation and date, the symptoms as the engineers saw them, the trigger, the root cause, the components involved, the contributing factors, what was done, what the organisation changed afterwards, the lessons, and links to the original write-up and an archived copy. Texts come in English and, where the reviewers wrote it, Korean. Start with GET /search?q= and a sentence describing what you see. Results come best match first, each with url, the page a person would read. The facets count the results by root cause, component, symptom and contributing factor, each with the case ids, so "what usually caused this" is in the same answer. To narrow by a vocabulary value you do not know the slug of, call GET /vocab?q= with a few words. To read everything about…

Endpoint: https://incidentlib-api.benchlet.com/

Verification: observed. Source: crawl.

Capabilities (18)

  • Approved cases filtered by vocabulary slugs newest first one page at a time
  • Every field of one approved case
  • Cases with the same root cause and at least one shared component
  • Every component with its case count and date range most cases first
  • One component its cases (most severe first) and what those cases involved
  • Every contributing factor with its case count and date range most cases first
  • One contributing factor its cases and what those cases involved
  • The values a sentence names without searching
  • This description as JSON
  • This description as YAML
  • Every organisation that published a case with its case count and date range …
  • One organisation its cases and what those cases involved
  • Every root cause with its case count and date range most cases first
  • One root cause its cases and what those cases involved
  • Find cases from a sentence describing the symptoms
  • Every symptom with its case count and date range most cases first
  • One symptom its cases and the root causes behind them
  • Every slug with its names or the slugs nearest to a few words
About · Contact · Privacy