# Assertline dashboard

> https://app.assertline.com is the web application of Assertline, an end-to-end testing product for web applications. This file tells language models and software agents what is here and how to work with it. The product itself is described at https://assertline.com/llms.txt

## Signing in

- Every page except the legal pages needs a signed-in account.
- People sign in on the first page with a Google account, or with an email address and a password (a new address is confirmed through an emailed link). An agent should ask its user to sign in, not attempt it.
- "Use an API key instead" on the sign-in page accepts an organization API key. A key is created by an owner or admin under Settings, API keys.
- Public pages: [Terms of service](https://app.assertline.com/terms), [Privacy policy](https://app.assertline.com/privacy), [Refund policy](https://app.assertline.com/refunds).

## Pages after sign-in

- `/`: projects, and a getting-started list for a new organization
- `/projects/{projectId}/sessions`: the recorded tests of a project
- `/projects/{projectId}/runs`: the runs of a project
- `/sessions/{sessionId}`: one recorded test: its steps and checks, and the button that runs it
- `/runs/{runId}/results`: the result of a run, one row per step with status, locator, time and screenshot
- `/runs/{runId}/report`: the shareable report of a run
- `/batches` and `/batches/{batchId}`: several tests run together, and their combined result
- `/environments`: environments and their variables, secret ones included
- `/datasets`: rows of values a test is repeated with
- `/workers`: the computers connected to run tests ("Where tests run")
- `/settings`: people, API keys, integrations and billing (owners and admins)
- `/plan`: the plan, its limits, usage this month and prepaid credits
- `/support`: a form that reaches the Assertline team

## Things an agent should leave to a person

- Upgrading or cancelling a plan, changing seats and buying credits spend money.
- Inviting or removing people, and creating or deleting API keys, change who has access.
- Deleting a project, a test or a step cannot be undone.

## API and MCP

- Documentation for people: https://assertline.com/docs
- OpenAPI 3.1 document: https://app.assertline.com/api/openapi.json
- MCP server (streamable HTTP): `https://app.assertline.com/api/mcp`. Sign-in is OAuth 2.1 with PKCE and dynamic client registration (metadata at `https://app.assertline.com/.well-known/oauth-protected-resource/api/mcp`): a person approves the app in the browser. Or send the header `Authorization: Bearer <key>`. Tools: whoami, list_projects, list_tests, get_test, run_test, list_runs, get_run, get_run_results, run_batch, list_batches, get_batch, list_environments, list_devices, get_plan_and_usage.
- The published operations find tests, run them and read results. They cannot create or change tests, manage people or keys, or pay. Requests carry `Authorization: Bearer <key>`.
- Keys are least-privilege by kind: a `ci` key (Pro) reads and runs and nothing else, which suits an agent; an `org` key acts as a member of the organization; a `worker` key runs tests on a machine and reports results.
- Errors are JSON with `ok: false`, an `error` message and often a `code` such as `PLAN_REQUIRED`, `CAP_REACHED`, `KEY_SCOPE`, `NO_WORKER` or `CREDITS_REQUIRED`.
- A run is `completed` when every step reported and none failed, and `failed` otherwise. Starting a hosted run can use paid minutes.

## Creating tests with AI

The "Create with AI" page (/agent) turns a plain-words instruction into a recorded test: an AI agent drives a browser, a person watches, steers and reviews the steps before saving. It runs in the desktop app on the person's computer, or in the cloud on Pro and Enterprise. It needs the organization's own OpenAI key (Settings, AI agent section). There is no API or MCP tool for starting an agent run; a person starts it from the page.