Usage & Limits

Monitor your workspace from the Usage page in the left navigation. Its tabs give you different views:

• Agent usage — What each agent delivers, how much it is used, and what it costs
• Credit balance — The workspace’s credits: balance, burn rate, and where the credits went (workspace admins only)
• Member adoption — How actively your workspace members are using Abundly
• User action log — Append-only log of workspace configuration changes (audit trail; workspace admins only)

Workspace admins can view workspace-wide data and manage all limits. Team admins see agent usage and member adoption scoped to teams they administer and can manage limits for those teams’ agents.

​

Agent usage

The Agent usage tab is one table with a row per agent, answering the three questions an owner asks: what did the agent deliver, how much was it used, and what did it cost. For each agent you see its criticality and value statement, its key metrics for the period with a trend for each, how many triggers and chat conversations it handled, and the credits it used. Trends compare with the period of equal length immediately before; the percentage is left out when the previous period is too small to compare fairly, or when the agent was created inside the period. Choose a period of a week, month or quarter, and narrow the table by name, team, tag, criticality or whether the agent has key metrics; Owned by me keeps only the agents you own. When lifecycle phases are enabled the table shows production agents by default, so experiments do not swamp the review. Active filters show as filled buttons; Reset filters clears them all, including the lifecycle phase, so every agent is shown. Grouping by team adds a subtotal per team. Your view is kept in the page URL, so a filtered table can be bookmarked or sent to a colleague. Export copies or downloads the visible rows as JSON, in the same shape as the Workspace API’s /workspaceapi/agent-usage endpoint, together with the period and filters that produced them. That is the format to hand to an agent or paste into a chat. Agents with default access set to Nothing (fully private) are excluded from this view so usage analytics stay aligned with who can actually use those agents.

​

Per-agent usage

To see one agent you can access, open its Activity page and use the Usage tab. It shows the same three things over the chosen period, in more depth: each key metric with its daily records, activity by channel and who took part, and credits used broken down by what consumed them.

​

Credit balance

The Credit balance tab, for workspace administrators, is about the account rather than individual agents: how many credits are left, how fast they are going, and where they went. Per-agent figures live on the Agent usage tab.

• Current balance — Your remaining credits, and the next top-up date and amount when the workspace has a subscription
• Burn rate — Average credits used per day over the last 14 days
• Credits used — Total credits used in the current billing period, or the last 30 days without a subscription
• Credit balance history — How your balance has changed over the selected period, with the monthly allowance marked
• Credits used over time — Daily, weekly or monthly bars for a date range of your choice, stacked by team when the workspace uses teams

You can also export the credits used as a CSV file if you want to analyze spending in a spreadsheet or import it into other tools. The export uses the date range and interval shown in the chart and lets you choose the aggregation: per time period and agent, by agent total, by team and period, or by time period total. Per-agent aggregations can include extra agent details (team, admin emails, enabled, criticality, description, value statement, capabilities, tags, last activity, last updated).

​

Member adoption

The Member adoption tab shows how actively people in your workspace are using Abundly — useful for tracking rollout, identifying inactive seats, and spotting which teams have taken to the platform.

• Active members — How many workspace members were active (logged in or interacted with an agent) in the selected period
• Adoption rate — Active members as a share of total members
• Average sessions per member — Mean session count across active members
• New members — How many members joined the workspace in the period

A daily trend chart shows active members over the selected period (Week, Month or Quarter). A team filter and a paginated member table let you drill into individual people, with each row showing their last login and last activity.

​

Agent limits

The Agent limits tab on the Agent management page lets you set daily limits for your agents to prevent runaway credit usage. When an agent reaches its limit, it pauses automatically until the next day (UTC midnight).

​

Default limit

Set a default daily limit that applies to all agents without a specific limit. This acts as a safety net across your workspace. New workspaces start at 5,000 credits per agent per day, and workspaces that have already set their own default keep it. Only workspace administrators can set or change the workspace default.

​

Agent-specific limits

You can override the default limit for individual agents, for example to set a higher or lower limit. Setting the limit to 0 will effectively pause the agent. Workspace administrators can set limits for all agents. Team administrators can set limits for agents in their teams.

​

When limits are reached

When an agent hits its daily limit:

• The agent stops immediately and shows an error message
• No additional credits are consumed
• All data and configurations remain intact
• The limit resets automatically at UTC midnight

You’ll see visual indicators in the UI:

• Yellow badge when an agent approaches its limit (80%+)
• Red badge when the limit is exceeded

​

Team monthly limits

If your workspace uses teams, workspace administrators can cap how many credits each team consumes per month. When a team reaches its monthly limit, every agent that belongs to the team pauses until the limit is raised or the calendar month rolls over. Set monthly limits from the Settings tab on the Team management page. Each team card shows the current month’s usage, the configured limit (if any), and a progress bar. Team monthly limits are enforced in addition to per-agent daily limits — an agent is blocked if either its own daily limit or its team’s monthly limit is exceeded. Chat and banner messages adapt to the viewer’s role:

• Workspace admins see a message with a link to edit the limit
• Team admins are told to ask a workspace admin to raise the limit
• Members are directed to their team administrator

​

Sidebar usage widget

When you open an agent, the left sidebar can show a compact daily usage widget with:

• Credits used today
• A progress bar when the agent has a daily limit
• A quick link to that agent’s Settings → Usage & Limits

This widget auto-refreshes as new usage is recorded, including after chat responses complete and when new activity log entries arrive. To show this widget, turn on Credit details in the agent’s Settings → Usage & Limits section. Workspace admins can choose whether new agents start with credit details on under Workspace → Settings → Agent defaults; teams can override this in their own settings.

​

Resetting daily usage

You can manually reset an agent’s daily credit counter at any time. This is useful if an agent hit its limit due to a one-time spike and you want to resume normal operation without waiting for midnight UTC. To reset an agent’s usage:

1. Open the agent’s settings
2. Under Main Settings, find Usage & Limits
3. Click Reset Today

If the limit interrupted a chat conversation, a Continue button appears on the error message once the usage is reset or the limit is raised, so the agent can pick up where it left off.

​

What counts toward credits

Both LLM usage (tokens) and tool usage count toward credits:

• LLM tokens — Input, output, and reasoning tokens are converted to credits based on model-specific rates
• Tool usage — Tools like web search, document processing, and external APIs also consume credits

All agent activity counts toward the daily limit, regardless of how it’s triggered—chat conversations, scheduled jobs, webhooks, emails, or API calls.

​

FAQ

​

Learn more

​

User action log

The User action log tab gives workspace administrators an append-only audit trail of configuration changes across the workspace — useful for reviewing who changed what, spotting unexpected changes, and satisfying compliance requirements. Tracked change types include:

• Agents — created, edited, enabled/disabled, deleted, ownership and team changes
• Teams — created, edited, membership and admin changes
• Workspace settings — configuration, capabilities, model selection, notification settings
• Secrets — created, updated, deleted
• API capabilities — created, updated, deleted
• HTTP APIs and documents — created, updated, deleted

Each row shows a timestamp, actor, resource, and a CRUD-colored badge (create / update / delete). Expand a row to see the specific fields that changed. Actors are usually workspace members, but changes an agent makes through a capability tool (for example Workspace Manager) appear here too, attributed to that agent. Workspace administrators see the full workspace history. Team administrators see actions scoped to the agents, teams, and members they administer.

​

Filtering and export

Filter by date range, actor, resource type, and action type. Export the filtered view as CSV or JSONL (up to 50,000 rows per export).