Publish optional price extras in the agent skill - #19
Merged
Merged
Conversation
Regenerated from the live catalog after the gateway shipped price add-ons: an offer may now carry `addons`, charged flat on top of `maxUsd` when the caller switches on the named input field. The catalog count moves with it. 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.
Regenerated with
npm run sync-skillsafter anyapi#1153 shipped price add-ons to production.An offer may now carry
addons: optional extras, each{id, label, field, usd}, charged flat on top ofmaxUsdwhen the caller sets the named input field to true. Without this an agent readsmaxUsdas the ceiling and under-quotes a hosted call.The catalog count moves 363 -> 369 in the same regeneration.
🤖 Generated with Claude Code