Make grepping the OpenAPI spec the default for unobvious API questions#10
Merged
Conversation
…API questions Triggered by a ZDR lookup that wandered through docs pages and the model catalog before finding the answer was a `route.data_handling.zdr.status` field exposed via `GET /v3/models?include=route`. The spec had it all along. - opper-api: lead the "source of truth" section with the rule, add the ZDR lookup as a worked example, and document `include=maker|route|benchmarks` on `/v3/models` with the compliance fields `route` exposes. - opper (router): promote the same rule into Ground rules so agents loading just the entry skill know to grep the spec for any unobvious API question.
Jose-Sabater
marked this pull request as draft
May 28, 2026 14:42
Jose-Sabater
marked this pull request as ready for review
May 28, 2026 14:42
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.
Summary
route.data_handling.zdr.statuson each model, surfaced viaGET /v3/models?include=route. The spec had it all along.opper-api/SKILL.md: lead the "source of truth" section with the rule, add the ZDR lookup as a worked example, and documentinclude=maker|route|benchmarkson/v3/modelswith the compliance fieldsrouteexposes (ZDR, residency, retention, training opt-out, third-party access, GDPR/DPA).opper/SKILL.md(router): promote the same rule into Ground rules so agents loading just the entry skill know to grep the spec for any unobvious API question.Test plan
scripts/validate-skills.shpasses (also runs in the push pre-receive)curl -s -H "Authorization: Bearer $OPPER_API_KEY" "https://api.opper.ai/v3/models?include=route" | jq '.models[0].route.data_handling.zdr'