> For the complete documentation index, see [llms.txt](https://help.delpha.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.delpha.io/delpha-api-and-mcp/api/asynchronous-verifications.md).

# Asynchronous verifications

Most verifications run asynchronously:

1. `POST /v1/{usecase}` validates the request, reserves credits and returns **202** with a `job_id`, a `Location` header (the poll URL) and `Retry-After` (seconds to wait).
2. `GET /v1/{usecase}/{job_id}` answers **202** while the job runs (`code: job_running`) and **200** with `result` once it is done. A terminal failure is a 4xx/5xx envelope with a `code` from the error catalog. A never-issued id, or another team's job id, is **404 `not_found`** — job ids are never an oracle for other tenants. Results are retained for 10 days.
3. `GET /v1/company` and `GET /v1/phone` are synchronous and answer in the request.

A test-mode key reserves nothing at step 1, and its job is already complete when the 202 is returned, so step 2 answers **200** on the first poll — see **Test mode**.

Typical completion times are published per operation in `x-typical-latency`; the submit/poll pairing in `x-polling`; the four MCP tool annotations in `x-mcp-annotations`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.delpha.io/delpha-api-and-mcp/api/asynchronous-verifications.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.