Integrations, data and usage
How answers get in, what deleting a project removes, how long data is kept, and how usage is counted.
Integrations
What it is. The ways answers reach a project. All of them end in Live events, scored by the same policy.
Why it matters. Use what your app already has, and change method without changing how you are scored.
How it relates. Each needs a key with Log answers. From Python, environment labels and dataset runs work with every method except OpenTelemetry, set on the call or once with variably.context().
Where you see it. Project configuration › Integration & keys › Log events.
Example.
| Method | Use it for |
|---|---|
observe() | Any Python app, the quickest start: no client to create, and it never raises into your app |
log() | The same fields from a client you create; raises on a mistake, for test scripts and CI |
| LangGraph | One instrument() call; only node runs with something to evaluate are sent |
| Google ADK | A plugin on the runner, including Vertex AI Agent Engine |
| OpenTelemetry | Traces you already produce, from any language through the Collector |
| MLflow | Recorded traces with log_traces(), or live ones |
| CI | Dataset runs and variably gate |
Deleting a project
What it is. Permanently removes the project and everything in it: answers, scores, claims, verdict history, sessions, datasets, runs, reviews, alerts, collection rules, policy versions and their audit, data definitions, experiments, prompts, flags and gates. Its API keys are revoked at once.
Why it matters. When a project is gone, its data is gone, not hidden.
How it relates. Owner only, confirmed by typing the project name. Kept: your organisation, members and other projects; usage for the period as daily totals with no content; a record of who deleted which project and when.
Where you see it. Project configuration › Delete project. See Delete a project.
Example. Export Live events rows, dataset items and the policy YAML, move apps to another key, then delete pilot-benefits.
Data retention
What it is. Answers, scores and verdicts are kept until you delete them, which today means deleting the project.
Why it matters. Your history stays available for comparison, review and re-scoring.
How it relates. During a pilot, ask us and we delete your data on request.
Where you see it. Project configuration › Delete project.
Example. At the end of a 30-day pilot, delete the pilot project, or ask us to.
Usage, SEUs and plans
What it is. Usage is counted in SEUs. 1 SEU covers one evaluation across all 49 dimensions, up to 10,000 claim-tokens; longer answers or sources use more. Every mode costs the same.
Why it matters. One unit to plan around, whatever you turn on.
How it relates.
| Plan | Price | Included | Beyond that |
|---|---|---|---|
| Free | $0 | 500 SEUs / month | Upgrade for more |
| Starter | $49 / month | 5,000 SEUs / month | $0.010 / SEU |
| Business | $249 / month | 30,000 SEUs / month | $0.010 / SEU |
| Enterprise | Custom | Customized | From $0.005 / SEU |
Upgrades take effect immediately. Moves to a lower plan start on the 1st of next month, with no refund. Owners change the plan.
Where you see it. Organization › Usage & billing (evaluations this month, SEUs used of included, Projected invoice) and Usage details and plan changes →.
Example. 3,200 of 5,000 SEUs used on Starter: projected invoice $49, no overage.