Harvest first-party OpenAPI from documentation → 3 specs at 3.2.0 - #1
Open
kinlane wants to merge 1 commit into
Open
Harvest first-party OpenAPI from documentation → 3 specs at 3.2.0#1kinlane wants to merge 1 commit into
kinlane wants to merge 1 commit into
Conversation
Retrieved the provider's own published OpenAPI from their documentation host, refined into one document per tag at OpenAPI 3.2.0, and registered each in apis.yml. Every spec carries x-source-url, x-documentation-url and x-last-validated provenance in info. No spec here is derived or inferred — all operations come from the provider's published contract. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This provider carried a Documentation URL and zero machine-readable contract in the catalog. Their documentation host publishes one — it just wasn't at a path our detector probed.
What landed
apis.yml— oneapis:entry per per-tag specopenapi/_original/Provenance
Each document carries
x-source-url,x-documentation-url,x-last-validated: 2026-08-10andx-provenance: first-partyininfo. Every operation comes from the provider's published contract — nothing derived or inferred. Refine reported 0 errors and 0 dangling $refs.Source: readme.io API registry. Three published SecureKey Hub documents overlapped heavily; refine merged them by tag into 3 per-tag specs.
Review notes
Not rescored — Kin Score waits on the apis.io rebuild.
🤖 Generated with Claude Code