Naming policy: products, commands and package IDs
Use the identifiers that actually run
The CLI executable is yp, its package is @yetdapay/cli, and the license SDKs use @yetdapay/license-*. DevPay is the name of the developer tools, not a devpay CLI binary or @devpay/* npm scope.
Which name should I use?
| Name | Purpose | Example |
|---|---|---|
| YetdaPay | Public commerce brand | Stores, donations, feedback |
| DevPay | Developer-tooling identity | Protection workflow |
yp | CLI command | yp protect plan |
yp-mcp | Local protection MCP | tools/devpay-mcp/server.mjs |
@yetdapay/cli | CLI package name | Repository tarball, not published |
@yetdapay/license-web | Browser license SDK | Activation and proofs |
@yetdapay/license-server | Server SDK (Node 22) | Entitlement enforcement |
@yetdapay/license-nuxt | Nuxt adapter | h3 guards |
@yetdapay/sdk | Source-copy commerce UI | Donation/feedback widgets |
yetdapay_*, yetdapay:// | MCP tools and resource names | yetdapay_store_list |
YETDAPAY_* | Commerce MCP environment config | YETDAPAY_API_BASE |
YP_* | CLI environment config | YP_CONFIG_DIR |
These are existing identifiers. Do not rename them for marketing consistency: changing command names, imports, or MCP IDs would break integrations.
Wire compatibility is separate
Token issuer (iss), entitlement claims and activation URLs are covered by the Interface Contract Matrix, not branding.