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.
What you can do (2)
What you can do
Available commands: 2 (2 read, 0 write). Enable only the commands your application needs.
| Command | Effect |
|---|---|
List Baremetrics data sources — baremetrics.sources.list |
Read |
Read a Baremetrics daily metric — baremetrics.metrics.get |
Read |
Connect and use
Open the integration'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.
Get your provider credentials
Follow these steps for Baremetrics, then enter the issued values in the connection form below.
- 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.
Where to enter credentials
In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.
| Connection field | Requirement |
|---|---|
| Baremetrics API key | Required |
Open API keys and create a Tooluse.net key for the enabled commands.
Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.
Configure Claude Code, Codex or Cursor once
Permissions and results
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's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.
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.
Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.
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.
Call from your client
Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.
Configure Claude Code, Codex or Cursor once
Discover your enabled tools
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.
curl 'https://api.tooluse.net/v1/tools' \
-H "Authorization: Bearer $TOOLUSE_API_KEY"
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.
HTTP call
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": {}
}'
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.
Commands
List Baremetrics data sources — baremetrics.sources.list
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.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
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.
This tool has no input parameters.
Full JSON Schema
Example input
{}
At most 1 provider requests per invocation; timeout: 30 seconds.
Read a Baremetrics daily metric — baremetrics.metrics.get
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.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
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.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
path |
object | Required | additionalProperties: false |
|
path.metric |
string | Required | The account-wide daily metric to read. | enum: ["mrr","arr","net_revenue","active_customers","active_subscriptions"] |
query |
object | Required | additionalProperties: false |
|
query.start_date |
string | Required | First included UTC calendar date, YYYY-MM-DD. | pattern: "^\\d{4}-\\d{2}-\\d{2}$"; format: "date" |
query.end_date |
string | Required | Last included date, at or after start_date and no more than 30 days later. | pattern: "^\\d{4}-\\d{2}-\\d{2}$"; format: "date" |
Full JSON Schema
Example input
{
"path": {
"metric": "mrr"
},
"query": {
"start_date": "2026-11-01",
"end_date": "2026-11-05"
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Errors
Check the key's expiry, revocation, workspace and allowed operations.
Reuse the same idempotency key only for the same request.
The connection or provider limit has been reached. Check the receipt before retrying.
Test the connection
Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client'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.