# obss quota and notifications - Obss

CLI
obss quota and notifications
Check your organization’s run balance and its history, and list, acknowledge, and set your notifications from the terminal.
Check your organization’s
run balance
before you launch, and manage your
notifications
. Buying runs stays in the dashboard:
obss quota inspect
returns the
Usage & billing
link.
obss quota inspect
Show the run balance, and whether it covers a launch of a given size.
obss
quota
inspect
[flags]
Plugin (MCP) tool:
inspect_quota
Flags
Flag
Type
Default
Description
--requested-runs
integer
Check whether the balance covers this many runs. At most 1,000,000.
Also takes the
global flags
.
Examples
Check whether you can launch 120 runs:
obss
quota
inspect
--requested-runs
120
Result fields
Field
Meaning
remainingRuns
Runs you can still use
reservedRuns
Runs held for work in progress
usedRuns
,
totalRuns
Runs used, and the total
remainingBreakdown
planRuns
,
topUpRuns
,
otherRuns
, and
planResetsAt
state
unlimited
,
active
,
exhausted
,
expired
, or
none
readiness
canLaunch
,
requestedRuns
,
shortfallRuns
, and a
reason
:
unlimited
,
covered
,
insufficient
,
exhausted
,
expired
, or
not_provisioned
billingUrl
The
Usage & billing
page, where you subscribe or top up
Notes
Plan runs reset each billing period and don’t roll over, and top-up runs never expire. A launch also checks the balance before it starts.
obss quota ledger
List the run balance history: every grant, hold, use, release, expiry, and adjustment.
obss
quota
ledger
[flags]
Plugin (MCP) tool:
list_quota_ledger
Flags
Flag
Type
Default
Description
--type
string
Comma-separated types:
grant
,
reserve
,
capture
,
release
,
expire
,
adjust
.
--limit
integer
50
Results per page, up to 100 (default 50).
--cursor
string
The
nextCursor
from the previous page.
Also takes the
global flags
.
Examples
List the latest 20 entries as JSON:
obss
quota
ledger
--limit
20
--output
json
List only grants, uses, and releases:
obss
quota
ledger
--type
grant,capture,release
Result fields
Each entry has a
qtx_
transactionId
, its
type
, the
amount
of runs,
effectiveAt
,
expiresAt
,
source
, and the
experimentId
that caused it, if any.
hasMore
and
nextCursor
page the list.
obss notifications list
List your notifications in the current organization.
obss
notifications
list
[flags]
Plugin (MCP) tool:
list_notifications
Flags
Flag
Type
Default
Description
--status
all
,
unread
all
Every notification, or only unread ones.
--limit
integer
25
Results per page, up to 50 (default 25).
--cursor
string
The
nextCursor
from the previous page.
Also takes the
global flags
.
Examples
List your unread notifications as JSON:
obss
notifications
list
--status
unread
--output
json
Result fields
Each item has
notificationId
,
insertedAt
,
status
, and
title
. A schedule’s paused, skipping, and short-of-runs notices, and the problem notices of experiments it launched, also carry a
scheduleId
that you can read with
obss schedules get
. When notifications aren’t available,
reason
says why.
obss notifications acknowledge
Mark one notification, or a page of unread ones, as read.
obss
notifications
acknowledge
(--id
<
notification-i
d
>
|
--all
) [flags]
Plugin (MCP) tool:
acknowledge_notifications
Flags
Flag
Type
Default
Description
--id
string
Mark this notification as read.
--all
boolean
false
Mark up to
--limit
unread notifications as read.
--limit
integer
500
Notifications in one
--all
call, up to 500 (default 500).
Pass
--id
or
--all
. Also takes the
global flags
.
Examples
Mark every unread notification as read:
obss
notifications
acknowledge
--all
Result fields
The result gives
acknowledgedCount
and, with
--all
,
hasMore
.
Notes
You can run the command again safely. Repeat
--all
while
hasMore
is true.
obss notifications preferences
Show your
Email
and
In-app
choice for each notification category.
obss
notifications
preferences
[flags]
Plugin (MCP) tool:
inspect_notification_preferences
Takes only the
global flags
.
Examples
Show your notification preferences:
obss
notifications
preferences
Result fields
Each category has a cell for each channel: enabled, disabled, required, or not used.
manageUrl
links
Profile → Notifications
. Your choices apply in every organization.
Key
Category
Channels you can change
experiment-updates
Experiment updates
email
,
in-app
billing-updates
Billing and runs
email
,
in-app
connection-alerts
Connections and model providers
email
,
in-app
product-marketing
Product news and marketing
email
account-sign-in
Account and sign-in
None (required)
operational-alerts
Operational alerts
None (required)
obss notifications preferences update
Change one or more of your notification preferences.
obss
notifications
preferences
update
--patch
<
jso
n
>
[flags]
Plugin (MCP) tool:
manage_notification_preferences
Flags
Flag
Type
Default
Description
--patch
string
Required. JSON keyed by category. Each value is
true
,
false
, or an object with
email
and
in-app
.
Also takes the
global flags
.
Examples
Stop experiment update emails and keep them in the app:
obss
notifications
preferences
update
--patch
'{"experiment-updates":{"email":false,"in-app":true}}'
Turn off product news:
obss
notifications
preferences
update
--patch
'{"product-marketing":false}'
Notes
The patch takes the four categories you can change:
experiment-updates
,
billing-updates
,
connection-alerts
, and
product-marketing
, which has only
email
. Name at least one category, and at least one channel in each object. A category you leave out keeps its setting.
Next steps
Runs and billing
Plans, top-ups, and how runs are counted.
Notifications
The header inbox and Profile → Notifications.
obss experiments
Preflight and launch once the balance covers it.
obss schedules
Read the schedule a notice names.
agents and models
Ask Obss
Powered by
This documentation is built and hosted on Mintlify, a developer documentation platform