ChartMogul API
Browse all Chartmogul APIs★ Only Publicly Available OpenAPI DocumentAnalyticsBusiness Intelligencebasic13 EndpointsREST
For Agents
Read SaaS subscription metrics — MRR, ARR, ARPA, churn, LTV — plus customers, plans, and invoices from ChartMogul. Basic-auth REST API with 13 endpoints.
Use for: Get the current MRR for my SaaS business, Retrieve ARR trend over the last 12 months from ChartMogul, List all customers in ChartMogul, Check the customer churn rate for last quarter
Not supported: Does not handle invoice generation, payment processing, or dunning — use for reading SaaS subscription metrics and billing data already imported into ChartMogul only.
Jentic publishes the only available OpenAPI specification for ChartMogul API, keeping it validated and agent-ready. ChartMogul is a subscription-analytics platform that turns billing data into SaaS metrics like MRR, ARR, ARPA, customer churn rate, LTV, and customer count. The API uses HTTP basic authentication (API key as username, empty password) and exposes 13 endpoints covering account info, data sources, customers, plans, invoices, and the core metric series.
Install Jentic One Beta
Connect the ChartMogul API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ChartMogul API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with ChartMogul API.
Retrieve current account info and connected data sources via /account and /data_sources
Pull MRR and ARR time series from /metrics/mrr and /metrics/arr for revenue dashboards
Track customer churn rate and customer count over time via the /metrics/customer-* endpoints
Fetch ARPA and LTV trends to monitor unit economics
List customers, plans, and invoices to reconcile billing data with revenue metrics
Delete a data source connection when sunsetting an integration via DELETE /data_sources/{data_source_uuid}
Retrieve a single data source by UUID to verify status before relying on its metrics
Use Cases
Patterns agents use ChartMogul API for, with concrete tasks.
★ Power an executive SaaS metrics dashboard
Pull MRR, ARR, ARPA, churn rate, LTV, and customer count from the metrics endpoints to populate a weekly executive dashboard. ChartMogul already normalises billing data from Stripe, Recurly, and other sources, so a single agent can refresh six headline metrics with six API calls and avoid building any of the math from raw invoices.
Call /metrics/mrr, /metrics/arr, /metrics/arpa, /metrics/customer-churn-rate, /metrics/ltv, and /metrics/customer-count for the last 13 weeks and emit the values as a single JSON payload
Reconcile billing data with revenue metrics
List customers, plans, and invoices then cross-check counts against /metrics/customer-count and the MRR series to spot data-source drift. This is the right sanity check after a billing migration or when ChartMogul numbers diverge from the internal source of truth.
List customers and invoices for the last 30 days, then call /metrics/customer-count and /metrics/mrr for the same window and report any deltas greater than 5%
Sunset a deprecated billing data source
When migrating from one billing provider to another, list /data_sources to identify the deprecated connection and call DELETE /data_sources/{data_source_uuid} once cutover is complete. The agent can verify by re-listing data sources and confirming the deprecated entry is gone.
List ChartMogul data sources, find the one named 'Stripe (legacy)', call DELETE /data_sources/{data_source_uuid}, and confirm it no longer appears in the list
Answer SaaS-metric questions inside an AI agent
An AI agent uses Jentic to discover ChartMogul's metric endpoints, loads the schema for /metrics/mrr, and answers questions like 'what was MRR last Friday?' or 'is churn rising?' without bespoke code. Because basic auth is handled by Jentic's vault, the API key never enters the agent's prompt.
Search Jentic for 'get chartmogul mrr', load the operation schema, retrieve the MRR series for the last 90 days, and report whether MRR grew or shrank week over week
Key Endpoints
13 endpoints — jentic publishes the only available openapi specification for chartmogul api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/metrics/mrr
Retrieve MRR time series
GET
/metrics/arr
Retrieve ARR time series
GET
/metrics/customer-churn-rate
Retrieve customer churn rate
GET
/metrics/ltv
Retrieve LTV
GET
/metrics/customer-count
Retrieve customer count
GET
/customers
List customers
GET
/invoices
List invoices
GET
/data_sources
List data sources
GET
/metrics/mrr
Retrieve MRR time series
GET
/metrics/arr
Retrieve ARR time series
GET
/metrics/customer-churn-rate
Retrieve customer churn rate
GET
/metrics/ltv
Retrieve LTV
GET
/metrics/customer-count
Retrieve customer count
GET
/customers
List customers
GET
/invoices
List invoices
GET
/data_sources
List data sources
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
ChartMogul API keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive a scoped basic-auth credential at execution time — the raw key never enters the agent's prompt context.
Intent-based discovery
Agents search by intent (e.g., 'get chartmogul mrr' or 'list chartmogul customers') and Jentic returns the matching ChartMogul operations with their input schemas.
Time to first call
Direct ChartMogul integration: half a day to wire up basic auth and parse the metrics response shape. Through Jentic: under 30 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
Stripe API
Stripe is a common upstream billing source for ChartMogul.
Use Stripe to read raw payments and subscriptions; use ChartMogul to read pre-computed SaaS metrics derived from those payments.
FAQs
Specific to using ChartMogul API through Jentic.
Why is there no official OpenAPI spec for ChartMogul API?
ChartMogul does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ChartMogul API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the ChartMogul API use?
The ChartMogul API uses HTTP basic authentication. Send your ChartMogul API key as the username and an empty string as the password. Through Jentic, the API key is stored in the encrypted MAXsystem vault and injected at execution time so it never enters the agent's prompt.
Can I retrieve MRR with the ChartMogul API?
Yes — call GET /metrics/mrr. The endpoint returns an MRR series for the requested date range. Pair it with /metrics/arr, /metrics/arpa, /metrics/customer-churn-rate, /metrics/customer-count, and /metrics/ltv to populate a complete SaaS-metrics dashboard.
How do I delete an old billing data source?
List data sources with GET /data_sources to find the UUID, then call DELETE /data_sources/{data_source_uuid}. ChartMogul will stop ingesting from that source going forward; historical metrics derived from it remain in the underlying record.
How do I get ChartMogul metrics through Jentic?
Run pip install jentic, set JENTIC_AGENT_API_KEY, then search 'get chartmogul mrr'. Jentic returns the /metrics/mrr operation with its query parameter schema, so the agent can supply start-date and end-date and execute without browsing the docs.
Are there documented rate limits for the ChartMogul API?
The OpenAPI spec does not declare per-key rate-limit quotas. ChartMogul publishes limits in its developer documentation rather than the spec; build retry-with-backoff logic for 429 responses and read any RateLimit headers the live service returns.
GET STARTED