---
title: "Baremetrics"
description: "Read connected data-source identities and daily account metrics from Baremetrics using your API key. Inspect MRR, ARR, net revenue and active customer/subscription counts over an explicit range of at most 31 days. Moneta"
---

> Documentation Index
> Fetch the complete documentation index at: https://help.tooluse.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Baremetrics

<p>Read connected data-source identities and daily account metrics from Baremetrics using your API key. Inspect MRR, ARR, net revenue and active customer/subscription counts over an explicit range of at most 31 days. Monetary values remain in provider cents. These reads exclude customer-level attribution, emails, charge details, imports, writes and managed OAuth.</p>

<details data-command-index><summary>What you can do (2)</summary>
<h2>What you can do</h2>
<p>Available commands: 2 (2 read, 0 write). Enable only the commands your application needs.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Command</th>
<th>Effect</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://help.tooluse.net/integrations/baremetrics#command-baremetrics-sources-list">List Baremetrics data sources</a> — <code>baremetrics.sources.list</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/baremetrics#command-baremetrics-metrics-get">Read a Baremetrics daily metric</a> — <code>baremetrics.metrics.get</code></td>
<td>Read</td>
</tr>
</tbody></table>
</div>
</details>
<h2>Connect and use</h2>

<p><a href="https://www.tooluse.net/tools/integrations/baremetrics">Connect and use</a></p>
<p>Open the integration&#39;s connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.</p>
<h2>Get your provider credentials</h2>
<p>Follow these steps for Baremetrics, then enter the issued values in the connection form below.</p>
<ol>
<li>Sign in to the Baremetrics account whose subscription data you want to read. Open its API settings and copy an API key, choosing read-only access when that option is available. Enter it in Baremetrics API key in this connection. It is sent as a Bearer credential and inherits that account’s access; this form does not perform OAuth authorization. Select sources.list or metrics.get, save and create an Tooluse.net API key scoped to those reads for your client. For metrics.get choose a supported metric and explicit start_date/end_date within 31 inclusive days. Monetary results stay in cents, while customer/subscription metrics are counts. Replace or revoke the key in Baremetrics API settings and update this connection when rotating.</li>
</ol>
<p><a href="https://developers.baremetrics.com/reference/authentication">Official credential setup</a></p>
<h2>Where to enter credentials</h2>
<p>In the integration page, sign in, choose your workspace and open Connect. If a <strong>Credentials</strong> choice is shown, select <strong>Use my credentials</strong>. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Connection field</th>
<th>Requirement</th>
</tr>
</thead>
<tbody><tr>
<td>Baremetrics API key</td>
<td>Required</td>
</tr>
</tbody></table>
</div><p>Open API keys and create a Tooluse.net key for the enabled commands.</p>
<p>Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.</p>
<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Permissions and results</h2>

<p>If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net&#39;s existing permissions. Disabling a connection or revoking a key immediately prevents new calls.</p>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<p>Your connection&#39;s daily allowance and key permissions also apply. Adding a connection does not make a provider request.</p>

<p>Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.</p>

<h2>Call from your client</h2>

<p>Use the shared MCP configuration. Refresh your client&#39;s tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.</p>

<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Discover your enabled tools</h2>

<p>List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.</p>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"
</code></pre>

<p>Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.</p>

<h2>HTTP call</h2>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {}
}'
</code></pre>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<h2>Commands</h2>

<details id="command-baremetrics-sources-list">
<summary><span>List Baremetrics data sources — <code>baremetrics.<wbr>sources.<wbr>list</code></span></summary>
<p>Read connected payment-provider/API source IDs with provider and name when supplied. Source IDs identify the origin of subscription data. This is a single provider collection, not automatic pagination. No customer emails, charges or source changes are exposed.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/baremetrics?command=baremetrics.sources.list">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<p>This tool has no input parameters.</p>

<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/baremetrics/commands/baremetrics.sources.list">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-baremetrics-metrics-get">
<summary><span>Read a Baremetrics daily metric — <code>baremetrics.<wbr>metrics.<wbr>get</code></span></summary>
<p>Read daily values for mrr, arr, net_revenue, active_customers or active_subscriptions over an explicit date range of at most 31 days inclusive. Monetary values remain in provider units (cents) without conversion or rounding. Preserves daily date/value and supplied comparison value/change. No customer-level attribution, cohort expansion or automatic follow-up requests.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/baremetrics?command=baremetrics.metrics.get">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.metric</code></td>
<td>string</td>
<td>Required</td>
<td>The account-wide daily metric to read.</td>
<td><code>enum: [&quot;mrr&quot;,&quot;arr&quot;,&quot;net_revenue&quot;,&quot;active_customers&quot;,&quot;active_subscriptions&quot;]</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.start_date</code></td>
<td>string</td>
<td>Required</td>
<td>First included UTC calendar date, YYYY-MM-DD.</td>
<td><code>pattern: &quot;^\\d{4}-\\d{2}-\\d{2}$&quot;; format: &quot;date&quot;</code></td>
</tr>
<tr>
<td><code>query.end_date</code></td>
<td>string</td>
<td>Required</td>
<td>Last included date, at or after start_date and no more than 30 days later.</td>
<td><code>pattern: &quot;^\\d{4}-\\d{2}-\\d{2}$&quot;; format: &quot;date&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/baremetrics/commands/baremetrics.metrics.get">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "metric": "mrr"
  },
  "query": {
    "start_date": "2026-11-01",
    "end_date": "2026-11-05"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<h2>Errors</h2>

<p>Check the key&#39;s expiry, revocation, workspace and allowed operations.</p>

<p>Reuse the same idempotency key only for the same request.</p>

<p>The connection or provider limit has been reached. Check the receipt before retrying.</p>

<h2>Test the connection</h2>

<p>Open the integration&#39;s commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client&#39;s tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.</p>

<p><a href="https://developers.baremetrics.com/reference/sources">Official provider documentation</a></p>

Source: https://help.tooluse.net/integrations/baremetrics/index.mdx