Modbot Docs
AI

Call log

Every AI call Modbot made — feature, model, tokens, cost, time taken and what went wrong — and what the model was sent for the calls that flagged something.

Every time Modbot asks an AI model anything, it writes down what happened. Settings → AI → Call log is that list.

It is the place to look when a feature has gone quiet, when the bill is higher than you expected, or when you want to know exactly what the model saw before it flagged somebody.

What each row says

ColumnWhat it is
WhenWhen the call was made
FeatureModeration, Insights (which includes the sentence on an alert), Chat or Connection test
ModelThe model that answered, marked Fallback when it was the second one
OutcomeSee below, with the error underneath when there was one
In, Cached, OutTokens sent, tokens the provider had already cached, tokens written back
CostWhat the call cost, or a dash when the model has no price
TookHow long the provider took
Asked byThe person who pressed the button, when a person did

Outcomes

OutcomeWhat happened
AnsweredThe model answered.
Timed outThe provider did not answer within the feature's time limit.
ErrorModbot could not reach the provider, or what came back was not an answer it could read.
RefusedThe provider answered with an error — a bad key, a model it will not run, a rate limit.
LimitedOne of your own spend limits, or a team member's monthly allowance, stopped the call. Nothing was sent and nothing was charged.

A call that did not answer and could have gone better on another model is tried once more on your fallback model. Both attempts get their own row, so the log always shows which model actually wrote the answer.

Filters

Filter by feature, by outcome, by model, and by a time range. Flagged only narrows the list to the calls that produced a flag. Show more loads the next hundred rows.

Seeing what the model was sent

Rows with an Open button keep the whole prompt and the whole answer. Those are:

  • calls that produced a flag
  • calls you started yourself: the Test button, Try it on AutoMod, Generate now on insights, and AI briefs, which are listed under Chat

Every other call keeps counts only. The prompt of a routine moderation check is somebody's profile text or Discord message, and keeping a copy of every check would build a second copy of your members that nobody asked for.

On the Flags page, a flag that came from an AI topic links straight to the call behind it.

Who can see it

WhatPermission
The list, with counts, models, costs and errorsSee operational log
The prompt and the answer behind one callChange settings

They are different permissions because they are different things to show. The counts are Modbot's own record of what it did. The prompt and the answer are a member's own words — so reading them needs the same permission that decides where those words get sent in the first place.

See roles and permissions.

How long rows are kept

Thirty days by default. Change it with Keep the call log for (days) on Settings → AI → Connection; 0 keeps them for ever. Modbot deletes older rows once a day.

Where to next

Modbot is not endorsed by or affiliated with VRChat Inc. or Discord Inc. VRChat is a trademark of VRChat Inc. Discord is a trademark of Discord Inc. SteamVR is a trademark of Valve Corporation. Windows is a trademark of Microsoft Corporation. Docker is a trademark of Docker, Inc. PostgreSQL is a trademark of the PostgreSQL Community Association of Canada. Railway is a trademark of Railway Corp. Other names are trademarks of their respective owners; see Legal. Modbot and its logo are trademarks of the Modbot project. Open source under AGPL-3.0.

On this page