Features / Platform

Platform · You don't pay for what you didn't get.

The owner can cap how many tasks a Co-Editor spends each cycle.

See pricingSolo and Team

A Co-Editor spends from the owner's shared task pool. Set a limit per billing cycle on a person and a run that would go past it is refused. Leave it blank and they draw on the whole pool.

What it does

On Team, a Co-Editor has no balance of their own. Their runs spend the account's tasks. Under What they may spend the owner can set a limit per person.

Before a run is paid for, Adamiro checks what that person has already spent this cycle. A run that would take them over the limit is refused.

Why

Several people spending from one pool can drain it without anyone noticing. A cap on one person keeps the others' work funded.

What it won't do

  • It doesn't cap a Co-Editor unless the owner sets a limit. Blank means the shared pool.

How to use it

Open the Platform guide in your dashboard, or start a trial to try it.

Log in Start the trial

Related

Signals / Radar

A briefing that cannot be read is not sent and tasks come back.

If the write-up of a Signals or Radar briefing cannot be read, no briefing email goes out and the run's tasks are returned to you. The articles are offered again on the next run.

Read entry

Signals / Radar

A run that finds nothing new, or nothing relevant, is not charged.

If your sources published nothing since the last briefing, or nothing was relevant to your profile, no briefing is made and the run is not charged. The timeline says "Run not charged".

Since 6 Oct 2026Read entry

Signals

Reviews you paste into Buyers are read at no task cost.

Paste a competitor's reviews on the Buyers tab, one per paragraph, and Signals reads them. It takes up to 50 a paste and 200 a week. Nothing you paste is published.

Since 13 Sep 2026Read entry