mcpField
B
billing-verification

billing-verification

github.com/credytTesting & quality52336 installsUpdated 24w ago
Repository

About billing-verification

A Credyt skill that runs a full billing-cycle check for a selected product and reports pass or fail at each step. It is intended for verifying setup changes or investigating billing issues independently of billing setup.

Key features

  1. 01Run end-to-end billing checks
  2. 02Select a product to verify
  3. 03Inspect event and usage settings
  4. 04Track results step by step
  5. 05Guide troubleshooting on failure

Use cases

  1. 01Check billing after dashboard changes
  2. 02Troubleshoot a product billing issue
  3. 03Verify product pricing and event setup

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/credyt/ai-tools --skill billing-verification

After installing, type/billing-verificationin Claude Code to confirm it loaded.

Bundled filesreferences/procedure.md

Details

From the project README

Credyt Verify

Run a full billing cycle test against a product to confirm everything is wired up correctly. Produces a clear pass/fail result for each step.

This is the standalone version of the verification that runs automatically at the end of /credyt:billing-setup. Use this when you want to verify a product on its own — for example, after making changes in the Credyt dashboard, or to troubleshoot a billing issue.

Determine what to verify

If the user specified a product (e.g., /credyt:billing-verification image_gen_std), use that. The $ARGUMENTS value is the product code or name.

If no product was specified, call credyt:list_products and ask which one to test:

"Which product do you want to verify? Here's what you have set up: [list products]"

Once a product is identified, retrieve its details with credyt:get_product and determine:

  • The event type it expects
  • The usage type (unit, volume, or both)
  • The asset it charges in (USD, credits, etc.)
  • Any required dimensions or volume fields
  • The expected price per event

Summarize this to the user before proceeding:

"I'll test '[Product Name]'. It expects an event of type '[event_type]' and should charge [price] per [unit/volume]. Let me run through the full cycle..."

Run the verification

Follow the six-step procedure in skills/billing-verification/references/procedure.md. Execute each step, track pass/fail, and stop to troubleshoot if any step fails.

After all steps pass, add:

Your billing is configured correctly. Run /credyt:billing-integration when you're ready to wire this into your app.

If any step failed, suggest running /credyt:billing-setup to correct the configuration, then /credyt:billing-verification again.

Cleanup note

"The test customer will stay in your account — since you're in test mode, this won't affect anything. You can delete it from the Credyt dashboard if you want."

Comments

Markdown supported