> For the complete documentation index, see [llms.txt](https://docs.complycube.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.complycube.com/documentation/api-reference/master.md).

# Overview

Explore the ComplyCube API for KYC, AML, and identity verification, with guides for authentication, checks, errors, and integration.

[ComplyCube](https://www.complycube.com/) is a cloud-based API platform for automating Identity Verification (ID\&V), Anti-Money Laundering (AML), and Know Your Customer (KYC) compliance workflows.

Our API follows REST principles, with predictable resource-oriented URLs and standard [HTTP response codes](/documentation/api-reference/errors.md#http-status-codes). All responses, including [errors](/documentation/api-reference/errors.md), are returned in JSON.

We’ve designed our documentation to be easy to follow. It is grouped by resource type and offers practical examples.

If you’re just getting started, begin with the [user guide](https://docs.complycube.com/documentation/) for an overview of the core concepts and workflows.

{% hint style="info" %}
As a general guideline, if a property has an empty or null value, we drop it from the JSON unless there’s a strong semantic reason for its existence.
{% endhint %}


---

# 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://docs.complycube.com/documentation/api-reference/master.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.