AI API TESTING

API tests from your spec.Contract checks on every endpoint.

Upload an OpenAPI spec (or point at your base URL) and Verity proposes the API journeys that matter — create, read, update, auth failures, edge cases — as Playwright API tests. Separately, contract checks exercise every operation automatically and report only the smallest request that breaks your documented contract.

What it checks

Request chains

Create a resource, read it back, update it, delete it — state carried between calls like a real client.

Auth and permissions

Missing or wrong tokens, forbidden actions, and the status codes your spec promises.

Contract drift

Undocumented status codes, schema mismatches and unsupported methods, with a curl command to reproduce.

Coverage by endpoint

Results grouped per endpoint, so gaps in API coverage are visible at a glance.

How it works

01
Add your OpenAPI spec
Or your API base URL. The same spec is reused for load tests — no second upload.
02
Review proposed tests
Keep the journeys you want; each is plain Playwright using the request fixture, no browser needed.
03
Run in CI
Journey tests run with your UI suite; contract checks run in a container on your runner.

tests/verity/api/orders.spec.tsEXAMPLE

import { test, expect } from "@playwright/test";

test("an order can be created and read back", async ({ request }) => {
  const created = await request.post("/api/orders", { data: { sku: "BASIL-01", qty: 2 } });
  expect(created.status()).toBe(201);
  const { id } = await created.json();

  const read = await request.get(`/api/orders/${id}`);
  expect(read.status()).toBe(200);
  expect(await read.json()).toMatchObject({ id, qty: 2 });
});

Why teams choose Verity

Two methods, one view

Example-based journeys and automatic contract checks land in one endpoint view; a failure both catch is marked double-verified.

Runs where your API lives

Internal APIs stay internal: tests run on your CI runners, not on Verity's servers.

No lock-in

Tests are Playwright files; contract checks read your existing OpenAPI document.

One place for every test type

UI, API, visual, AI-agent, load and security results share one run history and one verdict per release. Every plan includes all six.

Frequently asked questions

Can Verity generate API tests from an OpenAPI or Swagger file?

Yes. Verity reads the spec, proposes endpoint journeys and writes them as Playwright API tests. Contract checks also use the spec to exercise every operation.

Do I need a public API?

No. Generation reads your spec; execution happens in your own CI, so private and internal APIs work.

What do contract checks report?

Each operation that violates the spec — for example an undocumented 400 or a response that doesn't match the schema — with the minimal failing request and a curl command to reproduce it.

AI Playwright test generatorGenerate Playwright end-to-end tests with AI from your app's URL.Load testing in CIGenerate a load test from your OpenAPI spec and run it in CI: a smoke check on every pull request and load, stress, spike, soak or breakpoint profiles on merge.Security testing in CIScan your running app and your code on every pull request: a passive dynamic scan on PRs, a time-boxed active scan on merge, and static analysis of changed files.

Try it on your own app.

Free plan, no credit card: 15 AI-written tests a month and unlimited runs in your CI.