Repository navigation
docs: deprecate request options the API ignores - #129
Merged
Merged
Conversation
vvillait88
added a commit
that referenced
this pull request
Oct 4, 2026
## Summary Releases 0.6.4, carrying everything merged since 0.6.3: - help text for options the API ignores now says they are deprecated, including `--refresh` (#129) - quota reset documented as a UTC date rather than a timestamp (#128) Also in this PR: `@agent-score/sdk` floor raised to 2.8.1, released today. Worked with: Varun. Out of scope: no command behavior changes. ## Type of change - [ ] Bug fix (no breaking change) - [ ] New feature (no breaking change) - [ ] Breaking change (existing callers must update) - [x] Docs, tests, or internal maintenance only ## Public API none. ## Test plan `bun run lint`, `typecheck`, `test` (578 passed, 2 skipped) and `build` pass locally on this branch. ## Checklist - [x] Tests cover the new behavior, and the suite passes locally - [x] Lint, format, and type checks pass - [x] Docs and README examples updated if the public surface changed - [x] No secrets, credentials, or personal data in the diff or the tests
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
Three request options are sent to the API, which never reads them:
refreshon assess. The API stopped reading it when assessment scoring was removed; every assess is evaluated live.addressandoperator_tokenon session create.POST /v1/sessionsreads onlycontext,product_nameandkind, so a session is never pre-associated with a wallet or a credential. The README examples presented this as a way to "refresh KYC for an existing operator credential", which does nothing.These options are now marked deprecated with the reason, and the README pre-association examples are gone; the
kind: "sign_in"example stays. Nothing is removed and no signature changes, so existing callers keep compiling. pay's--refreshhelp text says the same. Found in a docs audit by comparing what each SDK sends with what the API route reads.Type of change
Public API
None removed. The options gain a deprecation note (
@deprecatedin TypeScript, a docstring line in Python, help text in pay). No release is cut for this alone.Test plan
Lint, type check and the full test suite pass locally in each repo.
Checklist