---
title: "Authentication"
url: https://docs.agentsverify.dev/authentication
---

# Authentication

Sign in to the [API key page](https://app.agentsverify.dev/dashboard/api-keys) and copy your workspace’s key. Store it in your server environment as `AGENTS_VERIFY_API_KEY`.

Send it in the `X-API-Key` header on requests to `https://api.agentsverify.dev`:

```
curl --fail-with-body 'https://api.agentsverify.dev/v1/credits' \  --header "X-API-Key: ${AGENTS_VERIFY_API_KEY:?Set your API key}"
```

Keep keys out of URLs, logs, chat replies and application browser bundles. Your API key grants access to your workspace’s credits and verifications. Revoke a key in the dashboard if it is exposed.

## Try a request in the reference

[](https://docs.agentsverify.dev/authentication#try-a-request-in-the-reference)

Open the [API reference](https://docs.agentsverify.dev/api-reference), enter your key in its authentication field and select an operation. These requests use your actual workspace and normal credit rules. The reference does not persist your key across page reloads or send requests through a third-party proxy.

Creating a verification returns a separate storage upload URL. The reference does not automatically upload a CSV. Follow the [quickstart](https://docs.agentsverify.dev/quickstart) for the complete two-stage transfer.

## Storage uploads

[](https://docs.agentsverify.dev/authentication#storage-uploads)

Send raw CSV bytes to the `upload.url` returned by creation. **Do not send `X-API-Key` or an `Authorization` header to storage.** Treat that upload URL as private. Use it only for its assigned file and exact byte length.

## Authentication errors

[](https://docs.agentsverify.dev/authentication#authentication-errors)

HTTP `401` means the API credentials were missing or rejected. Check the key and header before retrying. The customer API uses API keys; dashboard sign-in is managed separately.