Spend caps and usage

Much of what Nuvelics does for you uses paid services: writing and scoring pitches, researching and enriching stories, writing outputs, running claim checks. Two features keep that visible and bounded: Usage shows what your workflows consumed, and spending caps stop paid work when you decide enough is enough.

What counts as your spendCopy Anchor Link

Work falls into two groups:

• Work Nuvelics pays for on your behalf. This is what spending caps count and limit.
• Work that runs on your own credentials, such as a data source using your own vendor account. Nuvelics never counts this against a cap and never stops it. A data source on your own credential keeps running even while spending is paused.

The Usage page keeps the two apart, because they answer different questions. For work Nuvelics pays for, it leads with dollars. For work on your own credentials it shows consumption such as posts or searches, one unit at a time, since different units cannot be added together. Figures are labelled as estimates unless a provider reported an exact cost, and none is a bill.

UsageCopy Anchor Link

Open Usage in the sidebar. It has two tabs, and you see the ones your role permits:

• Spend shows what your workflows cost, broken down by resource such as enrichment, pitching, outputs and checks.
• Editorial shows what your pipeline produced, as counts of pitches and enrichment runs. It never shows cost, and it does not say how well runs went: a failed run still counts as work done.

Owners and admins can see both tabs. A viewer sees neither, and a member sees neither: the page is for whoever answers for the bill and the newsroom's output.

Spending capsCopy Anchor Link

Under Settings in Spending, an owner or admin sets a Daily cap, a Weekly cap and a Monthly cap. A new organization starts with a $5 daily cap, no weekly cap and a $150 monthly cap, so no organization can run up unbounded spend before anyone has looked. These are ordinary caps, not a platform limit: you can raise, lower or clear any of them, and leaving a field empty means no cap on that window.

How the caps behave:

• Any one binding stops work. The three are checked independently, and the first one reached stops spending. A cap of $50 is where spending stops, not where it starts stopping.
• Windows are calendar-aligned, in UTC. The daily cap resets at 00:00 UTC, the weekly cap on Monday 00:00 UTC and the monthly cap on the 1st. An organization outside UTC sees its daily reset at a UTC time, not local midnight.
• The daily cap cannot exceed the weekly or monthly cap. A daily cap above them could never be the one that trips.
• A cap of $0 pauses all paid work without touching any data source or integration setting.

When a cap is reached, no new paid work starts: new pitches, enrichment and checks wait. A banner reads Spending paused, naming the window and when it resets. A cap is a ceiling, not a fuse: work already in flight is not aborted, so spend can run a little past it.

When a cap resets is your choice. Resume automatically restarts work as soon as every window is back under its cap. Wait for someone to resume keeps it stopped past the reset until an owner or admin chooses Resume spending.

Beside each cap the page shows the spend in recent complete days, weeks or months and what the cap would have done over them. It is a floor, not a forecast: spend grows as you add data sources and newsdesks.

Why it works this wayCopy Anchor Link

• A cap protects you from surprises, and does not limit your own accounts. Refusing to run your own integration over a number Nuvelics estimated for your vendor account would be the wrong failure.
• Everyone sees that spending is paused, only some see amounts. Every member sees the banner, but only roles that can read spend see figures.