# MetaTrader.com

> MetaTrader Markets: market symbols, brokers, trading ideas, economic calendar events, and financial news on www.metatrader.com.

For questions about this site's content, use the public MQL5 Search API described below. Search only the MetaTrader.com modules listed here. Other modules in the shared API cover other websites and are outside this site's search scope.

Identify each result by its module. Trading ideas and third-party news are not official MetaTrader documentation.

Use the language of the user's current conversation as the default search language. If the user explicitly requests another language, use that language instead. Supported languages for these modules are `en`, `ru`, `zh`, `es`, `pt`, `ja`, `de`, `ko`, `fr`, `it`, and `tr`. Set both `hl` and the module language to that code. Do not search other languages unless the user explicitly requests a multilingual search. If the requested language is unsupported, explain that limitation rather than silently switching languages.

## Search modules

Replace `{lang}` with one of the supported language codes:

- `mt.{lang}.symbols` — market instruments and symbol pages.
- `mt.{lang}.brokers` — broker listings.
- `mt.{lang}.ideas` — trading ideas and charts.
- `mt.{lang}.calendar` — economic calendar event pages.
- `mt.{lang}.news` — financial news indexed for this site.

Choose only the modules relevant to the user's question. For a general search across this site, join all five codes with `|` in one `module` parameter. Do not add modules for MQL5.com, MetaTrader5.com, MetaQuotes.net, or other sites.

Send a GET request to `https://search.mql5.com/api/query` with `keyword`, `hl`, and an explicit `module`; omitting `module` returns an empty response. URL-encode query values, including `|` as `%7C`. The search is over indexed content; an empty response means no matching indexed results in the selected language and modules, not that the subject does not exist on the website. For a request about content by a named user, use the `author` filter when relevant and check `results[].info.author_login` when present.

For requests to find or list matching pages, the API results are sufficient: use `results[].info.title`, `date`, `text`, and `results[].info.url` to answer. Link directly to `info.url`, preserving any fragment. Do not open each result page merely to confirm a search hit, and do not bulk-fetch result pages. Search-result `text` may be an excerpt, so describe it as such. Open only a small number of source pages when the user asks for analysis that the search-result text cannot support. The search index does not establish current prices, quotes, or event outcomes; check a current source when those facts are required.

Start with `count=10` for a short answer. If the user asks for all matching results, paginate the API itself with a larger `count` (for example, `100`), advancing `from` by the requested page size until the reported `total` is covered; deduplicate by `(module, id)`. "All" means all matching results in the selected language and modules. State that completeness is limited to the search index and the language and modules searched.

## API reference

- [Search API guide](https://search.mql5.com/llms.txt): Parameters, module codes, language support, examples, pagination, and response handling.
- [OpenAPI specification](https://search.mql5.com/openapi.json): Machine-readable API contract.
- [Human search page](https://www.metatrader.com/en/search): Interactive site search.

Example: [English search for gold in symbols and ideas](https://search.mql5.com/api/query?hl=en&module=mt.en.symbols%7Cmt.en.ideas&keyword=gold&from=0&count=10).