---
layout: tap
site_name: creem
tap_name: create-product
description: "Create a Creem product with subscription pricing"
intent: write
columns:
  - name
  - id
  - price
  - product_url
  - mode
args:
  - name: key
    type: string
    description: "Creem API key"
  - name: name
    type: string
    description: "Product name"
  - name: price
    type: number
    description: "Price in cents (900 = $9.00)"
  - name: description
    type: string
    description: "Product description"
  - name: billing
    type: string
    default: every-month
    description: "Billing period: every-month, every-year"
args_json: |
  {"key":{"type":"string","required":true,"description":"Creem API key"},"name":{"type":"string","required":true,"description":"Product name"},"price":{"type":"number","required":true,"description":"Price in cents (900 = $9.00)"},"description":{"type":"string","default":"","description":"Product description"},"billing":{"type":"string","default":"every-month","description":"Billing period: every-month, every-year"}}
health_json: |
  {"min_rows":1,"non_empty":[]}
example_args: "--key creem_test_xxx --name 'My Product' --price 900"
source_url: https://github.com/LeonTing1010/tap-skills/blob/main/community/creem/create-product.plan.json
license: MIT
---

<section>
  <h2>What it does</h2>
  <p>Create a Creem product with subscription pricing</p>
</section>

<section>
  <h2>Install Taprun once</h2>
  <p>Taprun ships as a single MCP server exposing a catalog of compiled taps. One-time setup on macOS / Linux:</p>
  <pre><code>brew install LeonTing1010/tap/taprun
tap mcp connect</code></pre>
  <p>Or drop this into your <code>claude_desktop_config.json</code> (works identically in Claude Code, Cursor, Cline, Windsurf — any MCP host):</p>
  <pre><code>{
  &quot;mcpServers&quot;: {
    &quot;tap&quot;: {
      &quot;command&quot;: &quot;tap&quot;,
      &quot;args&quot;: [&quot;mcp&quot;, &quot;start&quot;]
    }
  }
}</code></pre>
</section>

<section>
  <h2>Call <code>creem/create-product</code></h2>
  <p>Terminal, once installed:</p>
  <pre><code>tap run creem/create-product --key creem_test_xxx --name 'My Product' --price 900</code></pre>
  <p>From the MCP host — exact same compiled plan, deterministic replay, zero LLM tokens:</p>
  <pre><code>tap.run({ site: &quot;creem&quot;, name: &quot;create-product&quot;, args: {&quot;key&quot;:&quot;creem_test_xxx&quot;,&quot;name&quot;:&quot;My Product&quot;,&quot;price&quot;:900} })</code></pre>
</section>

<section>
  <h2>Why compile it once</h2>
  <p>This plan was forged once — the AI read <code>creem</code>, picked stable structural addresses (JSON-LD, ARIA, RSS, or declared API endpoints, in that priority order), and saved them to a <code>.plan.json</code>. Every replay since then has used zero LLM tokens. When <code>creem</code> ships a site change that breaks the extraction, <code>tap verify</code> surfaces it before your data goes stale — not after your pipeline silently writes garbage for a week.</p>
</section>

<section>
  <h2>Related creem taps</h2>
  <table><thead><tr><th>tap</th><th>description</th></tr></thead><tbody>
    <tr><td><a href="/taps/creem/validate-license"><code>creem/validate-license</code></a></td><td>Validate a Creem license key and check activation status</td></tr>
    <tr><td><a href="/taps/creem/products"><code>creem/products</code></a></td><td>List all Creem products with status, price, and subscriptions</td></tr>
    <tr><td><a href="/taps/creem/transactions"><code>creem/transactions</code></a></td><td>List recent Creem transactions (payments)</td></tr>
    <tr><td><a href="/taps/creem/subscriptions"><code>creem/subscriptions</code></a></td><td>List all Creem subscriptions with customer, product, and status</td></tr>
  </tbody></table>
</section>