Skip to main content
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.
Plugin (MCP) tool: inspect_quota Flags Also takes the global flags. Examples Check whether you can launch 120 runs:
Result fields 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.
Plugin (MCP) tool: list_quota_ledger Flags Also takes the global flags. Examples List the latest 20 entries as JSON:
List only grants, uses, and releases:
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.
Plugin (MCP) tool: list_notifications Flags Also takes the global flags. Examples List your unread notifications as 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.
Plugin (MCP) tool: acknowledge_notifications Flags Pass --id or --all. Also takes the global flags. Examples Mark every unread notification as read:
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.
Plugin (MCP) tool: inspect_notification_preferences Takes only the global flags. Examples Show your notification 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.

obss notifications preferences update

Change one or more of your notification preferences.
Plugin (MCP) tool: manage_notification_preferences Flags Also takes the global flags. Examples Stop experiment update emails and keep them in the app:
Turn off product news:
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