# Assertline > Assertline is an end-to-end testing product for web applications. A person records a flow by clicking through their application in Chrome; Assertline keeps every step, lets them add checks, and replays the flow to give a pass or fail verdict with a screenshot for every step. No test code is written. This file is a plain-text summary of https://assertline.com for language models and software agents. The pages it links are static HTML and readable without JavaScript. ## Pages - [Home](https://assertline.com/): what the product does, the kinds of checks, where tests run - [Pricing](https://assertline.com/pricing): plans, limits, the plan comparison table and billing questions - [Download](https://assertline.com/download): the desktop app for Windows and Mac - [Questions and answers](https://assertline.com/faq): plain-language answers on starting, running tests, limits, privacy and billing - [API and MCP](https://assertline.com/docs): run tests and read results from a program or an AI assistant - [Dashboard](https://app.assertline.com/): the web application; sign-in required - [Terms of service](https://app.assertline.com/terms), [Privacy policy](https://app.assertline.com/privacy), [Refund policy](https://app.assertline.com/refunds) ## What it does - Recording: a Chrome extension records clicks, typing, navigation, uploads, dialogs and key presses as steps. - Checks: text and element checks on the page, checks on network requests and responses (status, headers, JSON fields, timing, number of calls), and design checks against a Figma file (styles and spacing). - Variables: environments, secret variables and datasets replace values at run time. Passwords and card numbers typed while recording are stored encrypted, never as step values. - Results: every run reports one result per step with the locator used, the time taken and a screenshot; reports can be shared and exported as PDF. - Teams: organizations with owner, admin and member roles; batches run several recordings together; finished runs can be sent to Slack (Pro). ## Where tests run - In the person's own Chrome, through the extension. - On their own computer, through the desktop app (Windows and Mac) or a command-line runner, also on a schedule. - In a CI pipeline, through the command-line runner with a CI key; the command exits non-zero when a test fails (Pro). - On Assertline's hosted browsers (Pro). - Across browsers on the customer's own BrowserStack account: Chrome, Edge, Firefox and Safari's engine (Pro). - At phone and tablet screen sizes, by choosing a device profile for a run. Hosted browsers identify themselves honestly as automation. A site that blocks automated browsers is reported as blocked, never as passed. ## Creating tests with AI - On the "Create with AI" page of the dashboard a person writes what to test in plain words. An AI agent does it in a browser step by step and records each step as an ordinary Assertline test. The person watches, can stop it or send it a message at any moment, and reviews the steps before anything is saved. - In the desktop app the agent uses a visible browser on the person's own computer (every plan). On Pro and Enterprise it can also run in Assertline's cloud from the dashboard; that browser cannot reach private or internal addresses, and one cloud agent run per organization runs at a time. - It needs the organization's own OpenAI key, added by an owner or admin under Settings. Assertline does not charge for agent runs; OpenAI bills the key's owner. Cloud browser time counts as hosted minutes. - Private values (logins, card numbers) are given by name and written in the instruction as {{NAME}}; the agent types the real value, the model is told only the name, and the saved test keeps the value encrypted. The model sees pictures of the page, so a value typed into an ordinary (non-password) field is visible to it. - It cannot pass captchas or codes sent to a phone (it pauses for a person), does not record steps inside iframes, and sites that refuse automated browsers refuse it too. ## Plans (US dollars, before tax) - Free: $0. Up to 3 people and 2 projects, unlimited recordings and checks, runs in the browser, the desktop app and the command line, screenshots from the desktop app and the command line stay on the device (a run in the browser stores its screenshots with the results at Assertline), 30 days of history. No hosted cloud runs. - Pro: $29 per editor a month, or $24 per editor a month billed yearly ($288). Unlimited people and projects, hosted cloud runs (3 at a time), 100 hosted minutes and 5 GB of evidence storage per editor each month pooled across the team, CI keys, cross-browser runs on the customer's BrowserStack account, Slack notifications, 1 year of history. - Enterprise: from $500 a month, by contract (support@assertline.com). 10 hosted runs at a time, 5,000 hosted minutes and 100 GB of evidence included each month, history kept without limit. - Beyond the included amounts: hosted minutes cost $0.06 each ($0.04 on Enterprise) and storage $0.50 per GB a month, paid from prepaid credits bought in packs of $10, $25, $50 or $100. Nothing is charged automatically; without credits a hosted run does not start. - Runs on the customer's own machines and browsers are free and unlimited on every plan. - Payments are processed by Paddle, the merchant of record. ## Desktop app - Windows 10 and 11 (64-bit): new; not yet signed with a Windows certificate (Windows asks for confirmation on first opening) and without automatic updates yet. - Mac: macOS 11 or later, Apple chip and Intel chip builds, signed and notarized with Apple, updates itself. - Apple silicon: https://assertline.com/downloads/Assertline-mac-arm64.dmg - Intel: https://assertline.com/downloads/Assertline-mac-intel.dmg - The current version and file checksums: https://assertline.com/downloads/latest.json ## Access for agents - Reading these pages needs no account and no JavaScript. - With an API key an agent can find recorded tests, run them and read results: through the API (OpenAPI document at https://app.assertline.com/api/openapi.json) or the MCP server at `https://app.assertline.com/api/mcp`. An assistant app can also connect to the MCP server without a key: it is given the address, a person signs in to Assertline in the browser and allows it (OAuth 2.1 with PKCE, dynamic client registration). For a key, a person creates one in the dashboard under Settings, API keys. Details: https://assertline.com/docs - Tests are recorded by a person in Chrome; the API and the MCP server do not create or change tests. - The dashboard needs a signed-in person: sign-in is with a Google account or with an email address and a password (the address is confirmed by an emailed link). An agent should ask its user to sign in rather than try to. - Starting a paid plan, buying credits and inviting people are decisions for the account's owner or an admin.