Baremetrics API

What authentication does the Baremetrics API use?

Baremetrics uses HTTP bearer authentication with a workspace-scoped token in the Authorization header. When called through Jentic, the bearer token is held encrypted in your Jentic One instance and injected at execution time so the agent's context never sees the raw secret.

Can I push subscription events from a custom billing system into Baremetrics?

Yes. POST /sources to register a custom source (or use an existing one), then POST /customers, POST /plans, and POST /subscriptions to push event records. Charges and refunds follow the same pattern via /charges and /refunds, and Baremetrics then derives MRR, churn, and LTV from those records.

What are the rate limits for the Baremetrics API?

Baremetrics enforces per-account rate limits that are not exposed as a single published number; for bulk historical backfills, batch operations and back off on 429 responses. Read endpoints (/customers, /subscriptions) tolerate higher polling rates than write endpoints.

How do I get current MRR through Jentic?

Install the Jentic SDK with pip install jentic, search for 'get current mrr from baremetrics', and execute the matched metrics or account operation. Jentic injects the bearer token, returns the JSON response, and the agent extracts the MRR value for downstream use.

Does Baremetrics expose cancellation reasons via the API?

Yes. The Cancellation Insights resource exposes structured churn reasons and free-text feedback for cancelled customers. Pull the data, group by reason, and feed it into save offers, retention sequences, or quarterly reviews.

Can I limit what my agent is allowed to do with the Baremetrics API?

Yes. Because you run Jentic One yourself, your own rules decide which Baremetrics operations and credentials the agent can use, so you can grant only read calls like GET /customers and GET /subscriptions while withholding everything else. Baremetrics takes its targets in the request body rather than in the URL path, so scoping happens at the operation level: write operations such as POST /customers, POST /subscriptions, and POST /plans are excluded unless you explicitly add them to the agent's allowed set. This lets an operator expose metric and customer reads for a revenue analyst agent without ever letting it create or modify billing records.