feat: explicit billing-integration handoff in billing-setup#56
Merged
benfoster merged 2 commits intoMay 13, 2026
Conversation
Prevents agents from improvising integration code after setup completes. Adds a "Next step" section to billing-setup that prohibits hand-rolling SDK calls and names the billing-integration skill as the required successor. Adds a canonical-path notice at the top of billing-integration so even agents that arrive there directly get the same signal. Co-authored-by: Ben Foster <benfoster@users.noreply.github.com>
benfoster
commented
May 13, 2026
|
|
||
| If the skill is not available and the user has not explicitly asked you to write integration code, stop here and wait for them to install it. Do not hand-roll fetch calls or invent API endpoints. | ||
|
|
||
| The SDK packages are `@credyt/api-client` (TypeScript/Node.js) and `credyt-api` (Python). These are the only supported ways to call the Credyt API from application code. |
Contributor
Author
There was a problem hiding this comment.
These are the preferred ways - the user may opt into HTTP direct calls but we should lead with the SDKs
|
|
||
| # Credyt Integrate | ||
|
|
||
| > **This is the only supported way to wire Credyt into application code.** Do not hand-roll `fetch` calls, invent API endpoints, or guess authentication headers — use the SDK (`@credyt/api-client` for TypeScript, `credyt-api` for Python). If you arrived here without running `billing-setup` first, stop and ask the user to run that skill before proceeding. |
Contributor
Author
There was a problem hiding this comment.
The SDKs are preferred but the user can opt into HTTP calls if for example they're not using typescript or python.
|
Claude finished @benfoster's task in 50s —— View job Changes applied
Both changes now lead with the SDKs as the recommended path while explicitly acknowledging HTTP as a valid opt-in for non-TypeScript/Python stacks. |
Co-authored-by: Ben Foster <benfoster@users.noreply.github.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.
Prevents agents from improvising integration code after setup completes.
Adds a "Next step" section to billing-setup that prohibits hand-rolling SDK calls and names the billing-integration skill as the required successor. Adds a canonical-path notice at the top of billing-integration so even agents that arrive there directly get the same signal.
Closes #55
Generated with Claude Code