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

# News Monitoring Languages

#### Full List of Languages Covered by News Monitoring

{% columns %}
{% column %}
Afrikaans

Albanian

Arabic

Armenian

Azerbaijani

Basque

Belarusian

Bengali

Bosnian

Bulgarian

Catalan

Chinese

Croatian

Czech

Danish

Dutch

English

Estonian

Finnish

French

Georgian

German
{% endcolumn %}

{% column %}
Greek

Gujarati

Hebrew

Hindi

Hungarian

Icelandic

Indonesian

Italian

Japanese

Kannada

Kazakh

Korean

Latvian

Lithuanian

Macedonian

Malayalam

Maltese

Modern Greek

Nepali

Norwegian

Norwegian Bokmål

Panjabi
{% endcolumn %}

{% column %}
Persian

Polish

Portuguese&#x20;

Romanian

Russian

Serbian

Slovak

Slovenian

Somali

Spanish

Swahili

Swedish

Tagalog

Tamil

Telugu

Thai

Turkish&#x20;

Ukrainian

Urdu

Vietnamese
{% endcolumn %}
{% endcolumns %}


---

# 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.vcheckglobal.com/products/monitoring/news-monitoring-languages.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.
