drevo-info.ru valid
Automatically discovered from public files. Ownership management is optional. Inclusion does not imply endorsement or publisher participation.
Manage this listing — optional · Visit publisher ↗
Verify with your agent
Paste this into your coding agent and it claims the listing for you. Verified sites are listed by name in our llms-full.txt, the file agents read, and get a private dashboard for listing controls, file health, measured activity and score history.
Claim my listing on Agent Web Map for drevo-info.ru:
1. POST https://agentwebmap.com/v1/sites/drevo-info.ru/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://drevo-info.ru/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/drevo-info.ru/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/drevo-info.ru).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory. Ownership management is optional.
Drevo — Open Orthodox Encyclopedia
Russian-language wiki encyclopedia on the history of Orthodox Christianity: saints,
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-21T15:34:18.112Z. Cached copy · Source on drevo-info.ru
# Drevo — Open Orthodox Encyclopedia
> Russian-language wiki encyclopedia on the history of Orthodox Christianity: saints,
> churches, monasteries, dioceses, people and events. Articles are written and edited
> by project contributors. Site: https://drevo-info.ru
Content addresses follow fixed templates: an article is `/articles/<id>`, a news item
is `/news/<id>`, an image is `/pictures/<id>`. Suffixless URLs are canonical; the legacy
suffixed form (`/articles/<id>.html`) answers 301 to the canonical address, so clients
must follow redirects.
Search lives at `/search?q=<query>`. Results are rendered by Google CSE on the client
side: they are absent from the HTML response, so the page must be rendered with
JavaScript enabled. No other search API exists — addresses such as `/find/articles?q=`,
`/search/index?q=` and `/search/index/text/<query>` are not routed and answer 404.
To enumerate articles, start from `sitemap.xml`: it is a `<sitemapindex>` pointing at
`sitemap1.xml`, `sitemap2.xml`, … — the chunks hold the canonical `/articles/<id>` and
`/forum/<id>` addresses, which is cheaper than guessing titles.
Some sections exist but are closed to automated clients by `robots.txt` — the calendar
among them. Guessed forms of those addresses (`/calendar/day/<date>`, `/days/<name>`)
are not routed at all and answer 404.
Usage rules: respect `robots.txt` — service sections (editing, revision history, revision
diffs, personal pages, statistics) are closed to automated crawling. The material belongs
to the project and its authors; when quoting, credit the source as «Открытая православная
энциклопедия "Древо"» (Open Orthodox Encyclopedia "Drevo") with a link to the specific
article. Keep a reasonable request rate: this is a non-commercial project on modest hosting.
Questions and feedback: pravbeseda@yandex.ru
## Sitemap
- [sitemap.xml](https://drevo-info.ru/sitemap.xml): full list of articles for crawling
- [robots.txt](https://drevo-info.ru/robots.txt): sections closed to automated clients
## Examples
- [Article "Сильван"](https://drevo-info.ru/articles/1296): a typical encyclopedia article
- [Search for "Сильван"](https://drevo-info.ru/search?q=Сильван): a Google CSE results page
Help agents understand your site
Optionally manage your description, publish terms for agents, review file health, measured discovery requests, publisher clicks and score history. Confirm domain control in your browser using a fresh token in your llms.txt, DNS, meta tag or well-known file. No backlink is required.
Manage this listing → · Agent and API instructions
Machine-readable: GET /v1/resolve?q=drevo-info.ru · GET /v1/domain/drevo-info.ru · this page as Accept: application/json or text/markdown · MCP lookup_domain