RichAPI warns you about credits by email, not in the dashboard. RichAPI sends one alert at 90% of credits used and one alert at a zero balance, to the organization owner only. When auto-reload is on, RichAPI sends neither email.

This article names the automatic messages RichAPI sends about credits and usage, and every failure it stays silent about. Read the silent list before you put a RichAPI integration into production.

RichAPI sends the automatic emails below. The dashboard has no notification bell and no in-app inbox, so no alert about credits, usage, or billing appears there.

The organization owner is one person: an Owner of the oldest workspace in the organization. Credits belong to the organization, so these emails cover every workspace in it.

A workspace invitation is one more email. A member starts it by hand, and the invited address receives it. Read Managing Workspace Members and Permissions.

RichAPI checks the credit balance after every API call that succeeds and charges credits. RichAPI compares the balance against the cycle baseline. The cycle baseline is the balance right after the last credit top-up, not the lifetime total of credits ever bought.

RichAPI sends each alert one time per cycle. A credit top-up raises the cycle baseline to the new balance and clears both alert markers. The next cycle can then send both alerts again.

An organization buys 1,000 credits. The cycle baseline becomes 1,000 credits.

One credit costs $0.02, so 1,000 credits cost $20.00.

CAUTION: A single large call can take the balance from 500 credits to zero. In that case RichAPI sends the 0-balance alert only. The 90% alert never arrives, because the balance passed both thresholds in one step.

RichAPI runs the credit check inside the API call path. If a workspace sends no API calls, RichAPI runs no check and sends no alert. The alert arrives on the call that crosses the threshold, and not before.

Auto-reload switches off both credit alert emails. RichAPI reads the auto-reload setting first. When auto-reload is on, RichAPI stops the check and sends no email at 90% and no email at zero.

CAUTION: Turn auto-reload on and both credit alert emails stop at once. RichAPI gives no warning that the emails stopped, and the dashboard shows no change.

This is a deliberate design. RichAPI treats an auto-reload workspace as a workspace that refills itself, so it sends no depletion warning. The design holds only while the saved card works.

Read Enabling Auto-Reload for Credits for the threshold, the reload pack, and the 24-hour cooldown.

When an auto-reload charge fails, RichAPI sends no message. RichAPI records the failure in its own logs and returns the API response as normal. No email reaches the owner, and the dashboard shows nothing.

WARNING: A workspace with auto-reload on and a declined card receives no warning of any kind. The credit alert emails are off, and the failed charge is silent. The first signal is a 402 error on live API calls.

These four auto-reload failures are all silent:

Read Tracking Credit Usage and Billing for the GET /usage endpoint and the usage dashboard.

No. The dashboard has no notification bell and no in-app inbox. RichAPI delivers every credit warning by email, so watch the inbox of the organization owner, not the dashboard.

The monthly usage report is one email per organization per month. RichAPI sends it on the 1st of the month at 09:00 UTC, to the organization owner. The report covers the month before and adds up every workspace in the organization. The subject line reads RichAPI usage — July 2026, with the real month.

RichAPI sends no report to an organization that made zero API calls in that month.

All figures in the report are aggregated in UTC. If your own records use a local time zone, expect an off-by-one-day difference at the edges of the month.

The report carries a CSV attachment. The file is named richapi-usage-<workspace>-<year>-<month>.csv. The file holds one row for each combination of date, endpoint, and API key. The file carries no totals row.

A very large month produces more than 50,000 rows. In that case RichAPI replaces the attachment with a download link inside the email. That link works for 7 days.

When the figures do not reconcile, the credit ledger section disappears. The usage totals stay correct in that case. Read the balance on the Usage & Credits page instead.

Plan your own monitoring around this list. Each row is a real event that produces no email and no in-app notification.

RichAPI sends the credit alert emails to one person: an Owner of the oldest workspace in the organization. RichAPI uses the email address on that account. Other members receive no credit alert.

RichAPI emails the organization owner at 90% of credits used and again at a zero balance. When auto-reload is on, both emails stop. The dashboard shows no in-app warning.

No. When an auto-reload charge fails, RichAPI sends no email and shows no in-app notification. The first visible signal is a 402 error on your API calls.

No. The dashboard has no notification bell and no in-app inbox. RichAPI sends every credit alert by email.

RichAPI sends the monthly usage report on the 1st of the month at 09:00 UTC. The report covers the month before and goes to the organization owner. An organization with zero API calls in that month receives no report.

No. The 90% and 100% thresholds are fixed and are not configurable in the dashboard. To warn yourself at a different level, read credits_remaining from GET /usage on a schedule.

No. RichAPI has no billing-contact field and no per-member email preference, so every credit alert goes to the owner address alone. Set a forwarding rule on the owner mailbox to copy a shared inbox.

Next: Understanding Rate Limits and Quotas