# Introduction

The Traces API is organized around REST architectural style. Our API has predictable resource-oriented URLs, JSON-encoded responses, standard HTTP response codes, and key-based authentication.

If you are our current customer your version of Traces API may differ from this reference as we continuously release new versions and tailor functionality for your individual needs. Follow your cluster URL or log in to the Knowledge Сenter to see documentation customized to your version of the API, with your API keys and data.

{% hint style="info" %}

### **Data migration has not finished yet!**

Please refer to the Knowledge Center for the latest documentation.

**TODO**

* [x] Add Counting API
* [x] Add FAF API
* [ ] Add People Search API
  {% endhint %}


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.traces.cloud/master.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.