Repository navigation
0.3.7: docs say APIs are free, and stop pinning v0.1.17 - #71
Merged
Merged
Conversation
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
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.
Two problems in the docs.
1. They were stale in a way that hurt installs. Every README and
llms-install.mdtold people to run a pinnedv0.1.17tarball URL — 15 releases old, noupload, no agent self-setup — and stated that "the npmlatesttag currently serves v0.1.14 while trusted publishing is being enabled", which is no longer true now that npm serves 0.3.6. 102 stale references across 11 files are gone: install commands arenpx -y @sandbaseai/cli@latest, the hard-coded 0.1.17 SHA-256 is replaced by a pin-and-verify snippet that reads the current version, and the MCP Registry links no longer point at/versions/0.1.17.2. They said everything costs money. Verified against the live catalog: every sampled
type=apitool isbase_price: 0(28 tools across 13 queries), while models stay paid (DeepSeek $0.3/$1.2 per 1M tokens, video $1–1.8/call). So:base_price: 0means free, and an agent must not ask the user to approve a cost for a 0-priced call. That was the real bug — the Skill said "paid per call", so agents gated free API calls behind cost confirmations.inspectas the source of truth instead of hard-coding a promotion, so a Skill cached on someone's machine cannot go stale if pricing changes.Also: every README now leads with
set up https://www.sandbase.ai/SKILL.md, which was missing from all of them, and the MCP tools table gainssandbase_run_cancel.Tests: 180, 179 pass, 1 skip.