Usage

Jsonify counts rows. Each workspace has a monthly collection cap, and every row the workspace collects in a calendar month (UTC) counts towards it. This page covers where to see those counts. Setting the cap and paying for rows above the free 100 are on Billing.

Free

100 rows per workspace per month

Counted

Rows collected in the calendar month (UTC)

Resets

First of the month, 00:00 UTC

Per

Workspace, not person or organisation

What counts as a row

Two things count:

• Rows a live run publishes into a dataset. The rule of thumb: you pay for rows that passed the pipeline’s checks and arrived where your team reads them.
• Collected records Jason hands you directly instead of through a pipeline run: a table or list of records in a chat, a CSV, JSON or Excel file it made for you, or an email attachment. The chat shows N rows counted toward your monthly quota with a short reason, and the step appears as Count rows.

Not counted:

• retries, blocked pages and failed fetches,
• test runs that verify a change before it is activated,
• rows held back by a check instead of published,
• repairs and the runs that resume after them (the resumed run’s published rows count once),
• dashboards, alerts, exports and queries built from rows already counted,
• data you uploaded yourself, and plain answers to a question in chat.

If a request to Jason would need more rows than the workspace has left, Jason says the monthly cap is reached instead of delivering the data.

The rows-left meter

The card at the bottom of the sidebar reads N rows left over a thin bar showing how much of the month’s allowance has been used. It is grey and purple normally, amber once you pass 80% of the cap, and red when the cap is reached. When collapsed, the sidebar shows a gauge icon with a coloured dot in the warning states.

Click it for the Monthly usage dialog:

Line	Meaning
N rows left	Cap plus grants, minus rows collected this month, with a progress bar.
Collected	Rows collected since the month began.
Monthly cap	Your workspace’s cap. Reads Monthly allocation on an enterprise agreement.
Once-off row grants	Extra rows added to this month, shown when you have any.
Cap reached. Collection is paused.	Shown when nothing is left.
Resets Mon d (UTC)	When the month’s allowance starts again.
Daily chart	Rows collected on each day of the month.

Manage usage → opens Settings → Usage.

Settings → Usage

Headed Usage — Rows collected in this workspace, month by month. The Previous month and Next month arrows beside the month name change the month for the whole tab. The current month is the latest.

For the current month, the headline reads n of total rows collected, with a progress bar that turns amber from 80% of the cap. Under it: n remaining · Manage collection cap (which opens Billing) and Resets Mon d, yyyy (UTC). A past month shows only the total, n rows collected.

The daily chart has one bar per day. Hover a bar for Mon d · n rows; click it for that day’s breakdown by pipeline, 25 pipelines per page. Before anything has been collected in the month, the tab reads No rows collected this month — Usage appears here after a completed collection.

By pipeline

The month’s pipelines with a proportional bar and the number of rows each collected. Each name links to its pipeline. With nothing collected: No collection this month.

Activity

Every event that changed the workspace’s rows in the chosen month.

Filter	Values	Default
Event type	All events, Collection, Once-off row grants, Cap changes, Monthly resets	All events
Pipeline	All pipelines, or any pipeline that collected rows that month	All pipelines
More filters	From and To dates, Minimum rows and Maximum rows	the whole month, no row limits

Columns are Date, Event, Details and Rows. Date and Rows sort when clicked. The table shows 25 events per page, with n events · Page n and Previous / Next.

Event	Details	Rows
Collection	The run, linked.	Rows published.
Ad-hoc request	The Jason chat that delivered the rows, linked, and the reason Jason gave.	Rows delivered.
Once-off row grant	The grant’s note and Expires or Expired date.	+n
Cap change	The old and new cap.	—
Monthly reset	The start of the new month’s allowance.	—

Collection in the Event type filter includes ad-hoc requests. With nothing matching: No activity matches these filters.

Usage warnings

Signal	When
Amber meter, amber progress bars	Rows collected reach 80% of the cap plus grants.
Red meter; Cap reached. Collection is paused. in the dialog	100%.
You have already collected more than this cap allows. Saving pauses further collection.	Lowering the cap below current usage on the Billing tab.

Alert rules can also watch runs; see Alert rules.

Out of rows

When nothing is left, a red banner appears above every page in the workspace: This workspace is out of rows. Pipelines are paused until Mon d, when your monthly allowance resets. with View usage.

While the banner shows:

• scheduled live runs do not start,
• Run Pipeline on a pipeline page opens Monthly collection cap reached instead of the run dialog, with Adjust monthly cap,
• Run on the pipelines list replies Out of rows — top up to keep running,
• runs triggered by webhook are not started,
• Jason does not hand over newly collected records in chat.

Everything else keeps working: datasets, dashboards, share links, exports, alerts on existing data, and chats with Jason. Test runs that verify a pipeline change are not affected. Collection resumes on its own when the month resets, or as soon as the cap is raised or a grant is added.

A failed payment also pauses collection on a self-serve workspace. That shows a different banner; see When billing needs attention.

What’s next