api-contract-verification skillA
api-contract-verification is agent-read markdown (skill) from nahid-sparktales/agent-dispatcher: Prove an API integration actually works by executing it — success path, documented failure paths, auth failure — and leave behind a contract test that catches the next break. Use before reporting any endpoint, client or third-party integration as working, when asked whether an integration is verified, or when checking someone else's integration work. Not for load or performance testing, not for rendered UI verification, and not a substitute for reading the provider's own documentation..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# API contract verification Code that compiles against an API is not an integration. A client that type-checks, matches the docs and reads correctly in the diff can still 404, send the wrong content type, retry a 401 forever, or pass every test against a stub nobody replaced. Keep the verbs apart, because this procedure exists to stop them merging: **created** is the code written; **executed** is a request actually sent and a response actually read; **tested** is a check that will run again without you; **reviewed** is a human or agent reading it; **deployed** is running somewhere real; **verified** is the conclusion, and it is available only after execution. ## When this fires Before any endpoint, API client or third-party integration is reported as working — your own or someone else's — and whenever a claim of "the integration works" needs backing. ## Procedure 1. **Write the contract down before calling anything:** environment and base URL, method and path, auth scheme, request shape, the success status and the fields you depend on, and the documented failure statuses. Take it from the provider's specification or current documentation, not from …
Read the whole file at its exact version.
How to install
mdr add nahid-sparktales/agent-dispatcher/api-contract-verification@git:20260919.a0d4f55mdr add nahid-sparktales/agent-dispatcher/api-contract-verification@sha256:7ee064edb23efd8aPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_3x6jb2yyxe36dvmh)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7177 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nahid-sparktales/agent-dispatcher · 49 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3x6jb2yyxe36dvmh GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/api-contract-verification GET https://markdownregistry.com/api/v1/blob/7ee064edb23efd8ad39b530ae2c4c3171ad2d9c093f04d4f1ea77a133bb9f7a2
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.