Nullgap.dev Docs

Administration

Usage

Understand the review quota, seats, credits and the monthly usage ceiling, and read them from the console or the API.

Nullgap meters four things: pull request reviews, review seats, automation credits and pentest credits. This page explains how each is counted and what happens when one runs out.

It describes the mechanisms only. What a seat, a review or a credit costs, how many reviews a seat includes, and how long a trial lasts are set out in your agreement with Nullgap and shown on the Billing page.

#Where to look

PageShows
UsageThe current period: reviews used and included, reviews by developer, fix runs, automation credits used, pentests
BillingYour plan, seats, the review pool, the switch for extra reviews, credit balances and the credit ledger

Every member can see both pages. Any API key can read the two endpoints behind them.

#The period

Usage is counted per calendar month in UTC. periodStart is the first instant of the month and periodEnd the first instant of the next. Counters start again from zero at periodEnd; nothing carries over.

#Review quota

Reviews are drawn from one pool shared by the whole organisation.

  • The size of the pool is the highest number of seats held at any point this period, multiplied by the number of reviews each seat includes. It is returned as reviewsIncluded. Removing a seat late in the month does not shrink the pool for that month.
  • A review counts against the pool when it is queued, running or completed. Skipped, failed and cancelled reviews do not count. The count is returned as reviewsUsed.
  • The pool is not divided between developers: one busy developer can use reviews that another did not.

#When the pool is used up

What happens next depends on the Allow extra reviews switch on the Billing page (the overage setting, which an admin can change):

overageEffect
Off (the default)New pull requests are skipped, with the reason "The pooled review quota for this month is used up. Turn on overage or give more members a seat to resume reviews." Reviews resume at the start of the next month, when a seat is added, or when the switch is turned on
OnReviews continue. Reviews beyond the pool are counted as overageReviews and charged as agreed for your workspace

A skipped review is listed under PR reviews with its reason. If checks are on, the pull request gets a neutral check titled "Review skipped"; if comments and notices are on, it also gets a notice. A skipped review never fails the check.

A workspace billed under an agreement (set up by Nullgap without metering) is not subject to the pool: reviewsIncluded is null and overageReviews is 0.

To turn extra reviews on through the API (an admin-scope key):

curl -s -X PATCH -H "Authorization: Bearer $NULLGAP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"overage":true}' \
  "$NULLGAP_URL/api/orgs/$NULLGAP_ORG/settings"

#Seats

A seat belongs to one member of the workspace. Only members take a seat. seatsBilled is the number of members holding a seat right now; People and Billing show the same number.

  • The person who creates the workspace holds the first seat. An admin can assign and remove seats for members on the People page, and a member with a linked code-host login gets one automatically with their first reviewed pull request.
  • Pull requests from bots and outside contributors are reviewed too and take no seat: they draw on the shared pool.
  • Each seat adds to the review pool at once.

Who gets a seat is explained under review seats.

byDeveloper in the usage answer lists every author who had a review this month, with the number of reviews and whether the member with that code-host login holds a seat (false for bots and people who are not members).

#Automation credits

Automation credits pay for the Nullgap AI work of fix runs (producing and verifying a fix for a finding) and of AI app tests (see what an AI app test costs). Both follow the rules below.

  • The balance is automationCredits. What a run used is recorded on the run and summed for the month as automationCreditsUsed.
  • When a run starts it sets aside the most it may be charged: the smaller of the credits left (less what runs under way have set aside) and the per-run limit of the automation that started it. A run is never charged more than that, so the per-run limit always holds, also when several runs go at once. What it does not use is released when it ends.
  • A run that fails on Nullgap's side, or that Nullgap stops, is not charged. A run you cancel is charged for the work done before it stopped.
  • With no credits left, starting a fix is refused with 402 no_credits, and an automation that would have started one records automation.skipped in the audit log instead.
  • Dependency fixes can still run with an empty balance.

See verified fixes.

#Pentest credits

Pentest credits are a prepaid balance for pentests, for workspaces that pay per pentest and have no payment method on file.

  • The balance is pentestCredits.
  • Starting a pentest takes its price from the balance. If the balance does not cover it, the start is refused with 402 payment_required and nothing is taken.
  • A retest is included in the pentest it re-checks and takes nothing.
  • A pentest that fails because of an error on Nullgap's side, or that Nullgap stops, is refunded to the balance, once.
  • A pentest you cancel is charged for the share of its work done before it stopped, never more than its price; the rest is refunded to the balance. Resuming it charges only what is left of its price. See what a cancelled pentest costs.

Ask for an estimate before you start one: see scoping a pentest.

#The ledger

Every change to a credit balance is an entry in the Credit ledger on the Billing page, returned as ledger (the most recent 100 entries).

FieldMeaning
kindautomation or pentest
amountPositive for a top-up or a refund, negative for a spend
reasonWhat it was for, in plain words: the pentest's repository, the finding a fix was for, a refund and why
refIdThe pentest or fix run the entry belongs to, when there is one
atWhen

A balance is the sum of its entries. It never goes below zero: a spend is only written if the balance covers it, or is capped at what is left where a partial spend is allowed.

Changes made by Nullgap's staff to a balance also appear in your audit log, with the reason they gave.

#The monthly usage ceiling

Nullgap can set a monthly ceiling on AI processing for a workspace. It is a safety limit that sits above the review pool and the credit balances, and it covers every use of Nullgap AI together: reviews, pentests, fix runs, skill runs, AI app tests, threat-model regeneration, sign-in checks for live testing, and questions to Nullgap AI in Slack. Runs that go at the same time share what is left instead of each counting on all of it. Most workspaces never reach it. It is not shown in the usage or billing answers.

When the ceiling is reached:

WhatEffect
New pull requestsSkipped, with the reason "This workspace has reached its monthly usage limit. Contact Nullgap support to raise it." This applies to reviews asked for by hand as well
Starting a pentest, a fix run, a threat-model regeneration or a sign-in checkRefused with 402 usage_limit
Questions to Nullgap AI in SlackAnswered with a note that the limit is reached; the /nullgap commands keep working
A run already in progressLimited to what remained under the ceiling when it started. If that runs out, the run ends with part of the work not done and says so; it is never reported as a clean pass
Reading findings, triage, exportsNot affected

The ceiling resets at the start of the next calendar month (UTC). To have it raised sooner, contact Nullgap; a change to it is recorded in your audit log as platform.limits_changed.

#Trial

A new organisation has no plan until the trial is started or a plan is agreed. Without an active plan, pull requests are skipped with "No active trial or subscription. Start a trial or subscribe to resume reviews."

  • An admin starts the trial on the Billing page by accepting the terms of service. It can also be started while creating the organisation.
  • An organisation gets one trial. A second attempt is refused with 409 trial_used.
  • A person gets one free trial in total, across all workspaces. A person is known by their e-mail address (for Gmail addresses, dots and a "+tag" do not make a new address) and, when they sign in with GitHub, their GitHub account. Someone who already had a trial creates a new workspace without a plan and is told "You've already used your free trial. Contact us or choose a plan to continue."; starting the trial on Billing is refused with 409 trial_used_by_person. Deleting a workspace does not give the trial back. A trial Nullgap sets up or extends for you is not affected.
  • The trial is started by a signed-in person, in the console; an API key cannot start it.
  • plan is trial and trialEndsAt says when it ends. Reviews stop at that moment unless a plan is active by then.
  • Starting the trial is recorded in the audit log as billing.trial_started.

plan is one of none, trial, pro or enterprise.

If Nullgap suspends a workspace, everything stays readable, nothing new runs, and anything that changes state answers 403 org_suspended.

#Read usage through the API

curl -s -H "Authorization: Bearer $NULLGAP_API_KEY" \
  "$NULLGAP_URL/api/orgs/$NULLGAP_ORG/usage"
{
  "periodStart": "2026-11-01T00:00:00.000Z",
  "periodEnd": "2026-12-01T00:00:00.000Z",
  "reviewsIncluded": 600,
  "reviewsUsed": 214,
  "byDeveloper": [
    { "login": "dana-acme", "reviews": 41, "seat": true },
    { "login": "renovate[bot]", "reviews": 12, "seat": false }
  ],
  "automationRuns": 9,
  "automationCreditsUsed": 6.4,
  "pentests": 1
}
FieldMeaning
reviewsIncludedThe size of the pool this period (null under an agreement)
reviewsUsedReviews that count against it this month
byDeveloperOne entry per author or seat holder, busiest first
automationRunsFix runs started this month
automationCreditsUsedAutomation credits those runs used
pentestsPentests started this month

#Read billing through the API

curl -s -H "Authorization: Bearer $NULLGAP_API_KEY" \
  "$NULLGAP_URL/api/orgs/$NULLGAP_ORG/billing"

The answer carries the fields described on this page: plan, trialEndsAt, seatsBilled, reviewsIncluded, reviewsUsed, overage, overageReviews, automationCredits, pentestCredits, hasPaymentMethod and ledger. The full shape is in the billing and usage reference.

#What you will not find

  • What a run cost Nullgap to produce. Reviews and pentests carry no processing figures in the console or the API; you are charged in seats and credits.
  • A way to buy credits or add a payment method in the console. Card payments are not available yet: contact Nullgap to move to a paid plan or to add credits.

Nullgap documentation