Sync the skill body: the latency preference and what it costs - #11
Merged
Merged
Conversation
Mirrors getanyapi-com/anyapi#879. The "Latency and request deadlines" section taught an agent to read a SKU's published p50/p95/p99 and then offered nothing to do about a slow one. Every SKU has accepted an optional preferLatencyUnderMs since anyapi#874. The paragraph carries the default (omit it and routing is unchanged), the warning that sending it can raise the price, quote_api as the free way to see that difference first, and the two cases where the field is inert so an agent does not read a deliberate no-op as a failure. Body-only sync, produced by `npm run sync-skills` in the anyapi repo. 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.
Body-only sync of
getanyapi-com/anyapi#879, which is live. Produced bynpm run sync-skills, so the body matchessrc/lib/agentSkill.tsexactly.The skill's "Latency and request deadlines" section taught an agent to inspect a SKU's published
p50Ms/p95Ms/p99Msbefore picking a timeout, and then dead-ended: it offered nothing to do about a 12-second median. Every SKU has accepted an optionalpreferLatencyUnderMssinceanyapi#874.The added paragraph carries four things:
anyapi#877put the same warning in the field's own published description, for the same reason: on x402 and MPP the agent signs the raised floor before the callquote_apias the free way to see that difference before spending, plus the two cases where the field is inert (a single-source SKU, and pages after the first on a paginated walk) so an agent does not retry into a deliberate no-opbash scripts/check.shpasses: skills checks passed (1 manifest-listed skill).