Evaluations and upgrades
This section describes the system-first staging preview. Production follows the eligibility and allowance shown in your account until the matching release is deployed.
POST /api/evaluation-runs/system with {"ai_system_id": 123}. The server resolves the component list, checks access to every repository and shares one Free allowance across the group. Paid plans retain per-prompt metering. The legacy prompt-start endpoint still permits only one prompt per Free request.
On Free, one account credit is reserved for the system bench. It is consumed only when every prompt in the group completes with saved scores. A failed, canceled or partial group releases that reservation. Failed provider calls cannot count as a successful evaluation. A fully cached group does not consume another credit. API-key execution caps still apply; failed attempts do not refund a key’s cap.
Choose Get more evaluations to review the next plan’s benefits. Existing subscribers are directed to a subscription-update confirmation, not a second subscription checkout. Review the price, taxes and proration in secure billing before confirming payment. View all plans opens the full comparison.
Model-provider selection for improvement suggestions requires active Growth or Enterprise access. It does not change the original model under test or evaluation judges. Existing saved provider restrictions are retained after a downgrade.
Data and retention
Only connect data you are authorized to share. The connection flow links to the applicable processing information. Connecting is an instruction to analyze selected data, not a claim that every legal agreement has been executed. Imported connector evidence defaults to 30-day retention. That limit does not currently describe every document, dataset, evaluation artifact, backup or third-party copy. Remove context through Manage sources and review the applicable DPA and privacy terms for the full processing scope. Removing an AI system deletes its structure, saved context and attached datasets. Previous evaluation records and source repositories are retained. Manage GitHub access opens GitHub’s installation settings; removing systems inside Bench does not revoke the GitHub App itself.Technical controls and a website page alone do not establish GDPR compliance. Organizational responsibilities, executed agreements, subprocessors, transfer safeguards, retention operations and data-subject procedures must also be verified.