# prisma-next db verify (/docs/cli/next/db-verify)

> For the complete Prisma documentation index, see [llms.txt](https://www.prisma.io/docs/llms.txt). A markdown version of any docs page is available by appending `.md` to its URL.

Verify a database against the current Prisma Next contract.

Location: CLI > Next > prisma-next db verify

`prisma-next db verify` checks whether the database marker and live schema match your emitted contract.

Use it in CI and deployment checks before application code that depends on a contract reaches users.

## Usage [#usage]

```bash
prisma-next db verify --db "$DATABASE_URL"
```

## Options [#options]

| Option            | What it does                                                                |
| ----------------- | --------------------------------------------------------------------------- |
| `--db <url>`      | Connects to the database.                                                   |
| `--config <path>` | Reads a specific `prisma-next.config.ts` file.                              |
| `--marker-only`   | Checks only the database marker.                                            |
| `--schema-only`   | Checks only whether the live schema satisfies the contract.                 |
| `--strict`        | Fails if the database includes schema elements not present in the contract. |
| `--json`          | Prints machine-readable output.                                             |

## Examples [#examples]

```bash
prisma-next db verify --db "$DATABASE_URL"
prisma-next db verify --db "$DATABASE_URL" --strict
prisma-next db verify --db "$DATABASE_URL" --schema-only
prisma-next db verify --db "$DATABASE_URL" --marker-only
```

Use JSON output in automation:

```bash
prisma-next db verify --db "$DATABASE_URL" --json
```

## What failures mean [#what-failures-mean]

| Failure            | Meaning                                                                                      |
| ------------------ | -------------------------------------------------------------------------------------------- |
| Marker mismatch    | The database was not signed for the emitted contract, or the contract changed after signing. |
| Schema mismatch    | The live database does not satisfy the emitted contract.                                     |
| Strict mismatch    | The database has extra schema elements not present in the contract.                          |
| Extension mismatch | The contract requires an extension that is not wired in the config.                          |

Fix the database or contract, emit again if needed, then verify again.

## Related pages

- [`CLI configuration`](https://www.prisma.io/docs/cli/next/configuration): Configure Prisma Next CLI commands with prisma-next.config.ts and global flags.
- [`prisma-next contract emit`](https://www.prisma.io/docs/cli/next/contract-emit): Emit Prisma Next contract artifacts.
- [`prisma-next contract infer`](https://www.prisma.io/docs/cli/next/contract-infer): Infer a starter contract from an existing database.
- [`prisma-next db init`](https://www.prisma.io/docs/cli/next/db-init): Initialize a database from the current Prisma Next contract.
- [`prisma-next db schema`](https://www.prisma.io/docs/cli/next/db-schema): Inspect a live database schema.