Skip to content
Promenaut

Promenaut joins forces with HSBC as strategic investor and design partner.Read More

For finance and finops

What does each run cost, and who holds the budget?

The questions a review asks of Promenaut, answered from the platform itself, and everything built for them.

01Your review

The questions, in the order they come.

At the model call. Every call is recorded with its input and output tokens, latency, success or failure, and the organisation and workflow it belongs to.

  • Model usage meteringEvery model call that completes is recorded with input and output tokens, latency, and the organisation and workflow it belongs to.
  • Per-run cost attributionCost is recorded per model call and as cost legs per stage of work, so spend attributes to the agent and the run that incurred it rather than arriving as one undifferentiated bill.

The full answer is in How Promenaut Accounts for Every Run.

In credits, set by the agents rather than by the tokens they consume.

  • A run is charged by its agents' tiers, not its tokensEach completed agent run is charged a fixed number of credits whatever tokens it consumed: one, three, seven or fifteen set by the agent's tier, or a whole number of credits an administrator has set for that agent, which takes the place of the tier.
  • Agent credit tiersEvery agent carries a credit tier, so the cost of running a workflow can be reasoned about from its composition before it runs rather than only after.
  • Credit ledgerConsumption is recorded against a credit ledger, so an organisation is charged in credits rather than in raw model spend.

The full answer is in How Promenaut Accounts for Every Run.

02Everything built for it

What the platform does for you, layer by layer.

Identity and access

  • Separated finance permissions
  • Least-privilege reporting access

Approvals, decisions and containment

  • Runaway agents are suspended automatically
  • Automatic step-up of containment for a runaway agent

Model risk

  • One cost figure for each run and agent, with its parts by kind

Credits and budgets

  • Model usage metering
  • Per-run cost attribution
  • Agent credit tiers
  • Credit cost calculation
  • Credit ledger
  • What this will cost, before you run it
  • A business unit out of credits stops its work
  • Spend limits by person, project or business unit, per day, week or month
  • Budgets allocated to business units
  • An agent's cost tab: observed spend and its credit rate
  • A run is charged by its agents' tiers, not its tokens
  • A completed run that missed billing is billed later
  • Credits move between the pool and business units as paired entries
  • A warning when a business unit reaches its threshold
  • The pool is funded on the contract's schedule
  • Credits provisioned from a signed file
  • Estimates learn from completed runs
  • A module's model calls are attributed to its run
  • What a run has spent, while it runs

FinOps reporting

  • Spend that bought nothing
  • Is this agent on the model it needs
  • The optimisation surfaces need populated cost to show anything
  • FinOps reporting surfaces
  • Owner chargeback statement
  • Renewal forecast and tier recommendation
  • Credits and money reported side by side
  • Per-enterprise credit currency
  • Chargeback by cost centre
  • The credit usage report, exportable
  • Model prices held in the model registry
  • Cost and capacity at a glance
More on Control →

Weighing us against the tools you already know? See how we compare, with sources →

03The pack

The full answers, written for you.

How Promenaut Accounts for Every RunAbout 15 minutes

Get the finance pack

Bring the numbers you need.

Cost a real workflow before it runs, and see where the spend of each run lands.

Cost a workflow with us