# MQL5.com

> Public MQL5 and MetaTrader documentation, articles, source code, forum discussions, products, and other community content.

For MQL5 language and API behavior, prefer the official documentation. Identify articles, CodeBase entries, forum posts, blogs, and Market listings by their source type rather than presenting them as documentation.

For questions about this content, use the public MQL5 Search API following the guide below. Use the language of the user's current conversation as the default search language; if the user explicitly names another language, use that language instead. Set `hl` and language-specific modules accordingly. Do not search additional languages unless the user explicitly requests a multilingual search. If the selected language is unsupported, say so rather than silently switching languages.

For requests to find or list matching pages, use the API results to identify matches and link directly to their source URLs, preserving any comment anchor. Do not open each result page merely to confirm a search hit, and do not bulk-fetch result pages. Open only a small number of source pages when the user asks for analysis that needs more context than the search-result text provides. For requests about posts by a named user, use the guide's `author` filter and check `results[].info.author_login` when present.

When the user asks for all matching results, paginate as described in the guide and deduplicate by `(module, id)`. "All" means all matching results in the selected language and modules, limited by the search index. State these limits; do not expand to other languages without an explicit request.

## Search

- [MQL5 Search API guide](https://search.mql5.com/llms.txt): Follow this guide to search MQL5.com content.
- [OpenAPI specification](https://search.mql5.com/openapi.json): Machine-readable API contract.