Skip to main content
A project’s Verifications tab lists every verification run of the project: Open Projects, click a project, and select its Verifications tab; a project opens on Code review. The card’s Verifications row also opens it. Click a row to open the run’s verification detail page. A project's Verifications tab with Run instant verification, the date range, the Statuses, Results and Triggers filters, name search, and runs from Vercel, Netlify, the CLI and the API A project's Verifications tab with Run instant verification, the date range, the Statuses, Results and Triggers filters, name search, and runs from Vercel, Netlify, the CLI and the API
  • The date range at the top of the page shows runs started in that window. Pick Last 24 Hours, Last 7 Days, Last 30 Days, Last 90 Days, or a Custom Range down to the hour. On a project’s Verifications tab, it sits with Run instant verification beside the page title, and both move to the end of the tab row when you scroll down.
  • Statuses, Results and Triggers narrow the list. Search name… matches run names from 3 characters.
  • Clear filters resets them.

Columns

You can sort by Name, Status and Started. The newest runs come first. Times follow the Time Format in Settings.

Status


Result


Callbacks

A run reports its result back to where it came from and to the repository it verified:
  • A run started by Vercel or Netlify reports to the provider.
  • A run bound to a commit or a pull request of a repository that the GitHub App, a connected GitLab group or a connected Bitbucket workspace covers also reports to the host: a check, a build status, or a pipeline status where IronBee writes one (Merges), on the commit, and the findings and a summary on the pull request or merge request. That covers Vercel and Netlify runs, and runs on IronBee from the GitHub Action, the GitLab component, the Bitbucket Pipe, ironbee verify and the API. See What appears on the pull request.
  • A run started with Run instant verification, a scenario run, and a run without the repository (--no-repo, ironbee_bind_repository: false) report nowhere.
The Callbacks column shows one entry per destination (Vercel, GitHub, GitLab, Bitbucket or Netlify):

Credits

Every verification run on IronBee uses credits by the minutes it runs. The Credits column shows: A run that ended without being charged shows 0. Hover it to see why: “not charged: the run never started”, or “not charged: IronBee’s own failure” when something on IronBee’s side failed before the agent started working. The Status, Result, Started, Duration and Credits columns of the verification list, with a running run's upper bound, ended runs' credits and dashes for CLI cycles The Status, Result, Started, Duration and Credits columns of the verification list, with a running run's upper bound, ended runs' credits and dashes for CLI cycles What a run costs, and the team’s credits this month, are on Credit usage.

Run instant verification

Owners, admins and members can start a one-off verification of a deployed environment from the console. Billing admins don’t see the button.
  1. On the project’s Verifications tab, click Run instant verification.
  2. Type a name in the Name field, which reads Enter an instant verification name while it’s empty. This is how the run shows up in the list.
  3. Pick the Environment to run against. The dialog opens on the first environment, in the order of Settings > Environments, that has a URL. The run starts at the environment’s URL property.
    • If the environment has no URL, the dialog says No URL to start from. with an Add one link to its settings. A Domain property alone isn’t enough.
    • Below the picker, a line sums up what the run is given, for example 3 variables and 4 secrets, or No variables or secrets. These are the project-wide variables and secrets plus the environment’s own. The environment’s own one wins when both share a name.
    • Click the line to expand it: Variables with their values, Secrets by name and type with the values hidden, and the environment’s URL, OpenAPI and Domains properties that are set.
  4. Verification type is always Web.
  5. Write the Prompt: what the run should check, the way you’d tell a teammate. It can use the environment’s variables and secrets by name. The counter below the prompt shows its length.
  6. Click Run verification. The dialog closes and the run opens on its verification detail page, where you can follow it live. If the run can’t start, the dialog stays open and says why.
Run verification stays disabled until the run has a name, a prompt that isn’t empty or over the length the counter allows, and an environment with a URL. The note next to it says how the run uses credits: for each started minute of the run. See What uses credits. Run instant verification dialog with a name, the staging environment, the Web verification type, the expanded list of 3 variables and 4 secrets with the environment URL, a prompt, and the Run verification button Run instant verification dialog with a name, the staging environment, the Web verification type, the expanded list of 3 variables and 4 secrets with the environment URL, a prompt, and the Run verification button The run appears in the list with the Console trigger.
  • The button is disabled on an archived project, and on an API project: API verifications can’t be started from the console yet. Hover it to see the reason.
  • The button is also disabled when the team’s credits for this month are used up. Hover it to see the date they reset. See When credits run out.
  • The environment needs a URL that a cloud run can reach. A local or private address is refused.
  • If the project has no environments yet, the dialog says so and links to them with Open environments. Add one with the URL to verify. See Environments.
An instant verification runs once. To run the same flow again and again, step by step, write it as a scenario.

CLI verification cycles

When your AI coding agent verifies a change with the IronBee CLI, each verification cycle appears in the list with the CLI trigger. Its detail page shows the recording, the actions and the verdict of that cycle. The recording arrives when the cycle finishes; see The recording. How the CLI verifies, the platforms it uses and the retry behavior are covered in the CLI docs.

What’s next?

Verification detail

Read a run: the recording, the actions, the network and the result.

Environments

The deployments a project is verified against.