API credits
The API credits page shows the credit balance of the workspace, your own credit cap and a log of the API and MCP requests that spent credits.
API credits pay for requests to the VitalSentinel API and MCP server. These requests come from API keys and connected apps, such as AI assistants. The workspace API credits page shows how many credits are left this cycle and who spent them.
Before you start
- To open the page, go to the workspace Settings and click API credits in the Workspace Settings sidebar.
- Every role can open the page. A member sees only the requests from their own API keys and connected apps.
- Credits belong to the workspace. The allowance depends on your plan. See Plans and limits.
- For the credit cost of each request, see API credits for developers.
Balance
The Balance card shows three figures for the current billing cycle:
| Figure | Meaning |
|---|---|
| Remaining | Credits left this cycle. |
| Used | Credits charged so far this cycle. |
| Allowance | Credits that the plan gives each cycle. |
A bar below the figures shows what is left. Remaining is green, amber when 25% or less of the allowance is left, and red at 0. When no credits are left, VitalSentinel refuses billable API and MCP requests until the next cycle.
Hover over the information icon of the Balance card to see Cycle ends and the date. The allowance refills when the cycle ends. Unused credits do not roll over.
Your own cap
If the owner set a credit cap for you, the Balance card shows it, for example Your own cap: 120 of 500 used. You can spend the smaller amount: what is left of your cap, or what is left of the workspace balance.
If your cap is 0, the card shows Your workspace owner has blocked your API and MCP access. Requests from your API keys and connected apps are refused. The rest of the workspace is not affected. Ask the owner to raise the cap.
Messages on the Balance card
- No API allowance on this plan: the plan gives no credits, and charging is not on yet, so requests are not charged.
- API and MCP requests are being blocked: the plan gives no credits, so VitalSentinel refuses every billable request. Contact support to add an allowance.
- "Credit charging is not switched on yet, so nothing has been billed.": VitalSentinel counts the credits but does not charge them yet.
Spending log
The Spending log card lists every request billed to the workspace this cycle, newest first. A member sees the card as Your spending, with only their own requests.
| Column | Meaning |
|---|---|
| When | The time of the request. |
| Credential owner | The member who created the API key or connected the app. Owners and admins only. |
| What they called | The API endpoint in plain words. A chip such as ×6 groups repeated requests. |
| Result | Empty for a success. A status chip for a failed request. |
| Credits | The credits charged, or Free. |
A request costs 0 credits (Free) when it failed, when VitalSentinel answered from its cache, or when the endpoint is free.
If nothing was billed this cycle, the card shows No API requests this cycle.
Cap what one person can spend
When the workspace has more than one person, the owner sees the link "Cap what one person can spend on the Members page". Credit caps are set on the Members page.
Data access log link
The API credits page answers "where did our credits go" for this billing cycle. For a full record of every request over a longer period, with a CSV export, click Data access log. See Data access log.
Troubleshooting
Why are my API requests refused?
If Remaining is 0, the workspace has no credits left this cycle. Wait for the cycle to end, or upgrade the plan. If the Balance card shows Your workspace owner has blocked your API and MCP access, ask the owner to raise your cap.
Why does a request show Free?
VitalSentinel does not charge a request that failed, a request answered from its cache, or a free endpoint.
Why do I see only my own requests?
If you are a member, the Spending log shows only the requests from your own API keys and connected apps. Owners and admins see every request.
Related
- API access - create API keys
- Connected apps - apps that use the API for you
- Members - set a credit cap for each person
- API credits for developers - credit cost of each request
Integrations
Connect Google accounts to a workspace for Google Search Console and Indexing Monitoring, and connect Slack channels and webhooks for alerts.
Data access log
The Data access log records every request that an API key or connected app made to read workspace data, with a date filter and a CSV export.
