Stop requiring verificationStatus in the signup response - #18
Merged
Merged
Conversation
The gateway retired the agent-key claim flow (getanyapi-com/anyapi#1307) and will drop verificationStatus, claimToken, and claimUrl from POST /agent/signup once the SDKs and this CLI release. The CLI never read claimToken or claimUrl; SignupResponse.verificationStatus is now optional so the type matches a response without it. The CLI never validated the field at runtime, so the new test (a signup response with none of the three fields saves the trial key) also passes without the type change; it guards the tolerance the gateway drop relies on. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
kev1n
added a commit
that referenced
this pull request
Sep 26, 2026
Agent signup no longer requires verificationStatus in the response (#18), so the CLI keeps working when the gateway stops sending it and the retired claimToken and claimUrl fields. Co-Authored-By: Claude Opus 5.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.
What changes
SignupResponse.verificationStatus(src/types.ts) is now optional. The CLI still saves it to~/.anyapi/config.jsonwhen the gateway sends it, and simply leaves it out when the gateway doesn't.claimTokenorclaimUrl, so there was nothing to remove for those.verificationStatus,claimToken, orclaimUrlstill saves the trial key and its config.The CLI never checked this field at runtime: the signup body is cast, not validated. So the published 0.9.0 already handles a response without it, and the new test passes with or without the type change. The test locks in the behavior the gateway drop depends on. The type change keeps the declared shape accurate.
Why
AnyAPI retired the agent-key claim flow in getanyapi-com/anyapi#1307.
POST /agent/signupstill returnsverificationStatus,claimToken, andclaimUrlonly for the benefit of published clients, and the gateway will drop them once the clients stop requiring them.Release order
Release to npm before the anyapi gateway PR that drops these fields merges (step 4 in getanyapi-com/anyapi#1307, "Ecosystem follow-ups").
Checks
npm run build: passes.npm test: 11 files, 101 tests pass.🤖 Generated with Claude Code