The usage overview

Usage → Overview shows how one service is used: calls, errors, the share of AI, response time, the account's calls of the month, calls per day, when calls happen and who calls. This page explains every number.

Open it

1. Open the service.
2. Click the tab Usage (Nutzung).
3. The section Overview (Übersicht) is shown first. The other section is Log (Protokoll); see The call log.

Usage is recorded for published services. A draft shows "No usage yet — Usage is recorded for published services. Publish the service to see who calls it."

Only the owner of the service sees its usage.

Choose the period

At the top right, switch between 7 days and 30 days (7 Tage, 30 Tage). All numbers on the page refer to the chosen period, unless a line says otherwise. The button with the circular arrow, Refresh (Aktualisieren), loads the latest numbers.

The four tiles

Calls this month

Below the tiles one line shows where the account stands in the month:

• "Calls this month: 1,234 of 10,000 (account)" (Aufrufe diesen Monat: 1.234 von 10.000 (Konto)) with a thin bar — the calls used and the calls your plan includes per month.
• On a plan without a monthly number the line shows the calls alone: "Calls this month: 1,234 (account)".

This number belongs to the account, not to the service: it counts the calls of all your services together, by calendar month in UTC, and starts again on the 1st. It does not change with the period switch. A call refused for a missing or wrong token appears in the numbers of this page but is not counted in the calls of the month. When the calls of the month are used up, the line and the bar turn red, and calls answer HTTP 429 until the 1st or until you move to a larger plan.

The link Call limits of the plans (Aufruf-Grenzen der Pläne) opens Call limits. The calls per service are on the Analytics page.

Calls per day

The chart Calls per day (Aufrufe pro Tag) has one bar per day, split by channel:

• API — calls to the API address, from code, Excel, Google Sheets and automation tools.
• AI (KI) — calls by AI assistants: over the service's MCP address or by an AI connected to the account.
• Web app (Web-App) — calculations made in the service's web app or in one of its web snippets, on public and on token-protected services alike.

The channel says how a call arrived. It does not depend on whether the call carried a token.

The legend shows the channels that had calls in the period. Days are counted in UTC, so a call late in the evening or early in the morning can fall on the neighbouring day in your time zone. Without calls the chart says "No calls in the last 7 days." (or 30).

When it is called

When it is called (Wann aufgerufen wird) is a grid of weekdays (Monday first) and the 24 hours of the day, in your own time zone. The darker a field, the more calls came in that hour; point at a field to read the number. Use it to see whether a service is used during office hours, by a nightly job, or around the clock.

The grid appears as soon as there are calls in the period.

Who is calling

The table Who is calling (Wer ruft auf) lists the callers of the period with one row per caller and channel, the row with the most calls first. A token that calls over the API and through an AI assistant has two rows, each with its own numbers.

Click a row to open the call log filtered to that caller.

How callers are named:

• A token name — the call carried a valid token of this service. Give each client its own named token and you see each one separately. See Tokens and access.
• An AI connection's name — an AI connected to your account ran the service. See The AI agents page.
• Public (no token) (Öffentlich (ohne Token)) — the call carried no token. Public calls are listed once per channel, so there can be one line for the API and one for AI.
• Web app (Web-App) — calculations made in the service's web app or a web snippet.
• Invalid token (Ungültiger Token) — the call carried a token that is not a valid token of this service: mistyped, or belonging to another service. On a protected service such a call is refused.
• A name with "(revoked)" ((widerrufen)) — the call carried a token you revoked. It is named for 30 days after the revocation, so you see which client still uses the old token and can move it to a new one.
• Unnamed (Ohne Namen) — a token or connection without a name.

All calls in the log → opens the call log without a filter.

The number of calls shown for a token under API → Access counts the same calls as this table: every calculation made with the token, refused ones included.

The line at the bottom

• "In this period, … of … successful calls (… %) were answered from the cache." appears when at least one call of the period was answered from the cache. The second number is the calls of the period minus its errors. See Caching and performance.
• "Days in the chart are counted in UTC. Input and result values are not recorded."

What counts as an error here

An error is a call that reached the service and did not return a result: a missing or invalid input, a missing or wrong token on a protected service, or a calculation that failed. The text of each is in the call log.

Calls that answer 404 (not published) or 429 (a limit) are not part of these numbers.

What to do with the numbers

• Many errors from one caller: open the log, read the error text, and tell that caller what to correct. See Input errors and Token errors.
• A row "Invalid token" or "… (revoked)": a client still sends an old or wrong token. Give it a current token. See Token errors.
• Many "Public" calls on a service that should be private: protect it with tokens. See Security overview.
• Calls close to the plan's number: the line Calls this month shows the account's standing; which service uses the most is on the account's analytics page. See Account analytics and Call limits.
• A high response time: see Caching and performance.

For developers and agents

• The page shows 7 or 30 days, today last. Days and the daily split are UTC; the weekday-and-hour grid is converted to the viewer's time zone.
• Channels: api, ai, app (web app).
• Totals of the period: calls, errors, calls per channel, the average duration of the successful calls in milliseconds, and the successful calls answered from the cache.
• The web app and the web snippets mark their calls with the query parameter _channel=app. The mark only names the channel in the usage; it has no effect on access, inputs or the result.
• A caller is identified by the token of the service that the call carried, by the AI connection, as the web app, or as public per channel. A token that is not a valid token of the service is "invalid"; a revoked one is named for 30 days. A token is shown by its name only; its value is never shown or stored with the usage.
• Callers are counted per caller and channel.
• The calls of the month are the account's: all services, calendar month in UTC, with the number the plan includes or none.
• Input and output values of calls are not recorded anywhere in the usage.
• The usage of a service is available to its owner only.
• An agent connected to the account works through its own actions; see What an agent can do for what it can read.

FAQ

Where do I see how often my service is called?

Open the service and click Usage (Nutzung). The tile Calls shows the calls of the last 7 or 30 days and, below, all calls since publishing.

Why does the Usage tab say "No usage yet"?

Usage is recorded for published services, and this service is not published. Publish it and the numbers appear with the first calls.

What counts as an error in the usage overview?

A call that reached the service and returned no result: a missing or invalid input, a missing or wrong token, or a failed calculation. Calls answered 404 or 429 are not included.

What does "Public (no token)" mean?

The calls carried no token, so the caller is not known by name. On a public service this is the normal case; give callers named tokens if you want to tell them apart.

How can I see which customer or system calls my service?

Create one token per customer or system and give each a name. Who is calling then lists each name with its calls, errors and last call.

Where do I see the calls of the month on the Usage tab?

Below the four tiles: "Calls this month: … of … (account)". It counts all services of the account in the current calendar month (UTC) against the calls of your plan. That is why it can be higher than the calls of this service.

What does "By AI" mean?

It is the share of the calls in the period that came from AI assistants, over the service's MCP address or from an AI connected to your account. The line below gives their number.

Why do the days not match my time zone?

The bars of Calls per day are counted in UTC. The grid When it is called uses your own time zone.

How is the average response time calculated?

It is the average duration of the successful calls in the chosen period, over all channels, in milliseconds. Refused calls are not part of it.

Can I see more than 30 days?

The page shows the last 7 or the last 30 days. The tile Calls also shows the total since publishing.

Why is the number of calls higher than I expected?

Every call that reaches the service counts, on every channel, refused ones too. Check Who is calling and the call log to see where the calls come from.

Can other people see the usage of my service?

No. Only the owner of the service sees its Usage tab.