Is this document still current, or superseded by a newer one?

$0.005 USDC per call · Business, finance and compliance · POST /api/v1/document-supersession · Id document-supersession

Given the target document id, the supplied set of documents (id, effective date, which ids each one supersedes, withdrawn flag) and a reference date, reports whether the target is superseded or withdrawn as of that date, following supersession chains, and names the superseding document and its date. For an agent about to rely on a standard, price list, policy or datasheet revision. It can only see the documents supplied: 'current' requires the caller to declare the list complete, otherwise the answer is unknown. Does not fetch documents or compare their text.

What you get

Stops an agent citing a withdrawn or superseded revision.

Call it

Send the JSON body below to https://agents.writerslogic.com/api/v1/document-supersession. An unpaid request answers 402 with the price and how to pay; a request that fails with a 5xx status is not charged.

curl -i -X POST https://agents.writerslogic.com/api/v1/document-supersession \
  -H 'content-type: application/json' \
  -d '{"target":"SPEC-2023-04","documents":[{"id":"SPEC-2023-04","effectiveDate":"2023-04-01"},{"id":"SPEC-2025-01","effectiveDate":"2025-01-15","supersedes":["SPEC-2023-04"]},{"id":"SPEC-2026-09","effectiveDate":"2026-09-01","supersedes":["SPEC-2025-01"]}],"asOf":"2026-11-04","listComplete":true}'

Input

Field	Type	Required	Description
`target`	string; length 0..200	yes	Id of the document being relied on.
`documents`	array<object>; max 200 items	yes	The documents the caller knows of, including the target.
`asOf`	string; length 0..40	yes	Reference date: a superseding document counts only if effective on or before it.
`listComplete`	boolean	no	The caller asserts documents holds every document that could supersede the target. Required for a pass.

Example request body

{
  "target": "SPEC-2023-04",
  "documents": [
    {
      "id": "SPEC-2023-04",
      "effectiveDate": "2023-04-01"
    },
    {
      "id": "SPEC-2025-01",
      "effectiveDate": "2025-01-15",
      "supersedes": [
        "SPEC-2023-04"
      ]
    },
    {
      "id": "SPEC-2026-09",
      "effectiveDate": "2026-09-01",
      "supersedes": [
        "SPEC-2025-01"
      ]
    }
  ],
  "asOf": "2026-11-04",
  "listComplete": true
}

Result

The response is { "data": ..., "_provenance": ... }. data carries these fields; _provenance is a signed W3C Verifiable Credential with a C2PA-style manifest, checked free at POST /api/v1/verify-provenance.

Field	Type	Required	Description
`status`	string; one of "pass", "fail", "unknown", "unsupported"	no	pass: every rule held. fail: a rule was violated (see witnesses). unknown: the input lacks the evidence to decide. unsupported: outside what this engine covers. Missing evidence is never a pass.
`requirements`	array<object>	no
`counts`	object	no	Non-optional requirements by state; optional ones are counted separately.
`current`	one of	no	true when pass, false when superseded or withdrawn, null when undecidable.
`supersededBy`	array<object>	no	Documents effective by asOf that replace the target, directly or through a chain.
`scheduled`	array<object>	no	Superseding documents that take effect after asOf.
`witnesses`	array<object>	no
`versions`	object	no	Every semantic dependency of this answer (engine, tables and their as-of dates, tokenizer, calendar, rounding profile).
`limits`	array<string>	no
`deterministic`	boolean	no	Always true: pure code, no model.

Pay and connect

Available through: x402 (USDC on Base), MCP. MCP clients reach it through the compliance-evidence-kit package.

Machine-readable

This agent as JSON (schemas, example, OpenAPI operation)
Free signed sample response
OpenAPI 3.1 · Catalog · Index of every agent