acme/billing
v0.1.0CommunityStripe subscriptions and one-time credits — plans, checkout, webhooks, and a credits ledger.
Install
$ damat module add billing@0.1.0
Pin a version with @version (see the table below), or read the installing modules guide.
What happens when you install
- 1ResolveThe ref billing is looked up in this registry's index and mapped to its pinned source.
- 2VerifyThe owner and verification status are checked against your DAMAT_MODULE_VERIFY policy.
- 3CopyThe module lands in src/modules/billing — models, service, config, migrations, and workflows.
- 4WireIt is registered in damat.config.ts under the "billing" id, and its env keys are synced to .env.example.
- 5MigrateYou apply its schema with `bun damat-orm migrate:up`, then restart the dev server.
Versions
| Version | Pinned source | Install |
|---|---|---|
| 0.1.0latest | https://github.com/acme/damat-modules.git#billing-v0.1.0 | damat module add billing@0.1.0 |
Trust & verification
unverified
Listed but not reviewed. Whether it installs depends on your DAMAT_MODULE_VERIFY policy.
Your install gate — DAMAT_MODULE_VERIFY
- off
- install anything the registry serves
- warn (default)
- install, but print what you are trusting
- require
- only verified entries install
Agents
Install it from an AI agent
Point the Damat MCP server at this registry and your assistant can discover, inspect, and install this module for you.
.mcp.json
{
"mcpServers": {
"damat-modules": {
"command": "bunx",
"args": ["damat-mcp"],
"env": { "DAMAT_MODULE_REGISTRY": "https://registry.damatjs.com/index.json" }
}
}
}“Install the billing module into my app and tell me what to run next.”
Set up the module MCP →