---
title: "Stale Scan"
method: POST
path: "/artifacts/stale-scan"
tags: ["impact"]
---

# Stale Scan

`POST /artifacts/stale-scan`

## Request

- Base URL: `https://api.specproof.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.specproof.ai/artifacts/stale-scan`
- Auth: none declared

Flag this org's artifacts affected by a spec moving on — a version bump, or an RFC being
obsoleted by another.

Three outcomes per artifact, and the distinction matters:
  · the clause was **reworded**  -> stale, and we record where it now lives, so it can be
    regenerated in one click;
  · the clause was **removed**   -> stale, and NOT regenerable: there is nothing to write a
    test against, so we say so instead of inventing a target;
  · the clause was **carried over** into a new document (only possible across an RFC
    obsolescence) -> stale only because it now lives in a different RFC; regenerating
    re-anchors the test to its new home.

## Headers

- `X-Org-Id` string, nullable
- `authorization` string

## Request body

- StaleScanRequest
  - `spec_base` string, nullable
  - `from_version` string, nullable
  - `to_version` string, nullable
  - `from_doc` integer, nullable
  - `to_doc` integer, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/specproof/apis/specproof-portal-api.md) · [All operations](https://skmtc.dev/specproof/apis/specproof-portal-api/llms.txt) · [OpenAPI document](https://skmtc.dev/specproof/apis/specproof-portal-api/revisions/228b03caa929?raw)