Sample data. These figures are not a customer bill.Learn more
parezenparezen
Harbour
Scale · Sample · cloud
Home
  • Get startedSoon
  • Audits
  • Overview
Analyse
  • Spend
  • Cost per task
  • Agents
  • Model comparisonSoon
  • Budgets
  • AlertsSoon
  • Reports
  • PR cost checksSoon
  • AdvisorsSoon
  • Spend analysis
Optimise
  • RecommendationsSoon
  • Routing policiesSoon
  • Shadow testsSoon
  • CachingSoon
  • TrimmingSoon
  • BatchSoon
  • Waste detectorSoon
Gateway
  • SetupSoon
  • ProvidersSoon
  • ModelsSoon
  • API keysSoon
  • DeploymentsSoon
  • PlaygroundSoon
  • LogsSoon
Savings & billing
  • Savings history
  • Savings ledger
  • Bill match
  • Billing
  • Invoices
Settings
  • Data & privacySoon
  • OrganisationSoon
  • ProjectsSoon
  • TeamSoon
  • RolesSoon
  • SSOSoon
  • Audit logSoon
Plan: Scale · Sample ↗
DocsHelp

Sample data. Not a customer bill.

Harbour/Agent budgets

Agent budgets

Planned

Per-agent and per-workflow spend, loops and kill-switch status.

Figures follow the shell: Last 30 days · All projects · All environments.

Loops are detected, not re-explained here
Agent budgets bound the bill. Loop detection and the kill switch live with the waste detector, which reads the same waste events and request flags. Open the waste detector
Agent spend
$0$0
Agents
0
Loop signals
0
Waste events and waste flags in this view
Kill switches holding
0

No agent traffic in this view

This project, environment and range have no rollup rows. Change the filters in the header.

Clear filters

Workflow budgets

The plan asks for a budget per workflow, with the same soft alert and hard stop as an agent.

This organisation has no workflow budgets in the sample.