DOCUMENT OPS

Validate ReadMe code samples against the live API

On a nightly schedule, extracts the request examples from your ReadMe guides, replays them against a staging API.

CategoryDocument Ops
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNightly at 2am
  • ActionExtract request samples from ReadMe guidesReadMeReadMe
  • ActionReplay each sample against staging APIHTTP webhook
  • LogicCompare actual vs. documented responses
  • OutputFile a Linear bug per broken sampleLinearLinear

What it does

Catches the subtlest doc drift: examples that still look right but no longer work. It harvests the runnable request samples embedded in your ReadMe guides, executes each against a staging endpoint, and compares the real response to what the docs claim.

When to use it

Use it when broken copy-paste examples are eroding developer trust and reviewing them by hand isn't scalable. Nightly runs surface regressions the morning after they ship, before customers hit them.

How it works

  1. 1A nightly schedule trigger starts the run.
  2. 2The workflow pulls all guides from ReadMe and extracts each documented request sample with its expected status and response shape.
  3. 3An HTTP step replays every sample against the staging API base URL with test credentials.
  4. 4A logic step compares actual status codes and response shapes to the documented expectations and isolates mismatches.
  5. 5For each failing sample it opens a Linear bug with the guide URL, the request, and the actual vs. expected response.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ReadMeAPI docs, changelog, auth.
  2. 2
    Connect HTTP webhookTrigger any URL on agent actions.
  3. 3
    Connect LinearIssues, projects, cycles, triage.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.