ANTE User Manual

AI Usage Logs

AI Usage Logs give you a complete, request-by-request record of every AI call made across the system, so you can review what was sent, what came back, how many tokens it used, and whether it succeeded.

⚠️ Developer Access Only

This page lives in the Developer portal and is only available to users with developer privileges.

Overview

Whenever the system uses AI — for example to chat, extract information from a document, read an image, or summarize text — a log entry is created. The AI Usage Logs page lets you browse all of these entries across companies, search and filter them, and open any single call to see its full details.

This is useful for:

  • Reviewing how AI is being used across companies and users
  • Checking token consumption
  • Investigating failed AI calls and reading their error messages
  • Confirming exactly what was sent to and returned from the AI

AI Usage Logs vs. AI Statistic — Use AI Usage Logs (this page) to drill into individual AI calls, one row at a time. Use the AI Statistic page for the analytics view: totals, credential-source breakdowns, and the heaviest companies and users.

Where to Find It

In the Developer portal sidebar, open the System group and click AI Usage Logs.

Summary Cards

At the top of the page, four summary cards show totals across all logged AI activity:

CardDescription
Total CallsTotal number of AI calls recorded
Total TokensTotal tokens used across all calls
Prompt TokensTotal tokens used for the input (prompt) side
ErrorsNumber of calls that ended in an error (highlighted when greater than zero)

The Logs Table

Below the summary cards, every AI call is listed in a table, newest first. Each row shows:

ColumnDescription
DateWhen the call was made
CompanyThe company the call belongs to (shows "-" if none)
UserThe user who triggered the call (shows "-" if none)
OperationThe kind of AI action — shown as a colored tag
ProviderThe AI provider used
ModelThe specific AI model used
TokensTotal tokens used by the call
PromptTokens used for the input (hidden by default)
CompletionTokens used for the response (hidden by default)
DurationHow long the call took (shown in milliseconds or seconds; "-" if not recorded)
StatusWhether the call succeeded or failed

The Prompt and Completion columns are hidden by default. You can turn them on using the table's column options.

Operation Types

The Operation column uses colored tags to show what kind of AI action was performed:

OperationMeaning
ChatA conversational AI request
ExtractPulling structured information out of content
VisionReading or interpreting an image
SummarizeCondensing text into a summary
EmbeddingsGenerating numeric representations of text
StreamA streamed AI response

Status

The Status column shows one of:

  • Success — the call completed normally
  • Error — the call failed (shown in red)

Searching and Filtering

Use the search box to look up logs by keyword. You can search by:

  • Operation
  • Provider
  • Model

Filters

You can narrow the list using these filters:

FilterOptions
OperationChat, Extract, Vision, Summarize, Embeddings, Stream
ProviderOpenAI, Gemini, Claude, Grok
StatusSuccess, Error

You can also sort the table by Date, Operation, Provider, Model, Tokens, or Duration.

Viewing a Single Log

Click any row in the table to open its detail page. The detail page is titled AI Log # followed by the log number, with a status badge in the top right. Use the back arrow to return to the list.

Request Details

FieldDescription
OperationThe kind of AI action
ProviderThe AI provider used
ModelThe specific model used
StatusSuccess or Error
DateThe full date and time of the call
DurationHow long the call took

Company & User

FieldDescription
CompanyThe company associated with the call
UserThe name of the user who made the call
User EmailThe email address of that user

Token Usage

FieldDescription
Prompt TokensTokens used for the input
Completion TokensTokens used for the response
Total TokensCombined token total

Error Message

If the call failed, an Error Message section appears showing the full error text returned by the AI.

Input Data

The Input Data section shows what was sent to the AI — for example, the chat messages or prompt. Long text is shown in readable blocks, and chat messages are grouped by their role. If an image was sent, it is shown as a placeholder rather than the raw image data. A Truncated tag appears if the input was shortened to save space.

Output Data

The Output Data section shows what the AI returned. A Truncated tag appears if the output was shortened to save space.

Metadata

If the call recorded any extra information, it appears in a Metadata section at the bottom.

Note: Images sent to the AI are not stored in full. When a log includes an image, you will see a placeholder noting that the image data was not kept to save space.

Common Tasks

Reviewing Recent AI Activity

  1. Go to DeveloperAI Usage Logs
  2. Check the summary cards for overall totals
  3. Browse the table, which lists the most recent calls first

Investigating a Failed AI Call

  1. Go to DeveloperAI Usage Logs
  2. Set the Status filter to Error
  3. Click the failed call to open its detail page
  4. Read the Error Message section
  5. Review the Input Data to see what was sent

Checking Token Usage by Operation or Provider

  1. Go to DeveloperAI Usage Logs
  2. Use the Operation or Provider filter to narrow the list
  3. Sort by the Tokens column to see the heaviest calls

Inspecting What Was Sent and Returned

  1. Open a log from the table
  2. Review the Input Data section to see the request
  3. Review the Output Data section to see the AI's response

Tips

  • Errors first — Use the Errors summary card and the Error status filter to quickly surface problems.
  • Watch token use — Sort by Tokens to find unusually large calls.
  • Use the detail view — The list gives a quick overview, but the detail page shows the full request, response, and any error.

💡 Note: AI Usage Logs are recorded automatically for every AI call. Truncated input or output indicates the content was shortened to save storage space.