# credyt

Sets up usage-based billing for an AI product from inside Claude: products, pricing, customer wallets. Needs a Credyt API key.

- plugin · `type=plugin` · Claude Code · ★ 52
- Author: credyt
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/credyt/ai-tools
- Updated: 2026-05-13
- HTML: https://affpapa.org/en/nevibecode/plugins/credyt

## What it does

Three slash commands cover the path from picking a monetization model to shipping the integration. `/credyt:billing-setup` walks you through a conversation about how you charge, creates products, assets and prices in Credyt over MCP, then runs a full billing cycle on its own. `/credyt:billing-verification` exercises that cycle for one product: it spins up a test customer, tops up the wallet, fires a usage event and checks whether the charge landed. `/credyt:billing-integration` puts billing into your application code.

Four skills sit behind the commands: `pricing-strategy`, `billing-setup`, `billing-verification`, `billing-integration`. The first one is for deciding on prices before you configure anything. The other three are also exposed as plugin slash commands.

An API key is required — you get one in the Credyt dashboard after signing up. The commands talk to Credyt through an MCP server, so wire that up first with `npx add-mcp`, pointing at `https://mcp.credyt.ai` and passing the authorization header. The same skills install through `npx skills add credyt/ai-tools`, which suits agents that speak MCP but gives you no slash commands.

## Install

### Claude Code (native platform)

**Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add anthropics/claude-plugins-community
```
In the agent chat (not a shell):
```text
/plugin install credyt@claude-community
```

## When to use it
- create products, assets and prices in Credyt from a conversation
- confirm a usage event actually triggers the charge
- add customer creation and usage tracking to app code
- settle on a pricing model before touching billing tooling
- debug a payment that never gets charged

## Example prompts
- Set up billing for my AI product with `/credyt:billing-setup`
- Run `/credyt:billing-verification` against the `pro-plan` product
- Wire Credyt into my app code: `/credyt:billing-integration`

## Similar
- [voltagent-biz](https://affpapa.org/en/nevibecode/plugins/voltagent-biz.md) — plugin · ★ 26065
- [voltagent-domains](https://affpapa.org/en/nevibecode/plugins/voltagent-domains.md) — plugin · ★ 26065
- [payment-processing](https://affpapa.org/en/nevibecode/plugins/payment-processing.md) — plugin · ★ 41729
- [blockchain-web3](https://affpapa.org/en/nevibecode/plugins/blockchain-web3.md) — plugin · ★ 41729
- [business-operations-skills](https://affpapa.org/en/nevibecode/plugins/business-operations-skills.md) — plugin · ★ 28733

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md