telegram.org valid
Telegram Core
Developer documentation for the Telegram platform: the Bot API (HTTP interface for bots), Mini Apps, and the lower-level Telegram API (MTProto) used by full clients and TDLib.
- Authority
- 72 reach 26 · trust 10 · quality 21 · freshness 15
- Tier
- featured
- llms.txt
- https://core.telegram.org/llms.txt
- Sections
- 4
- Links
- 30
- Size
- 4518 bytes
- Popularity rank
- #176
- Registered
- 2003-12-15
- Country
- — Location unknown
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-18T14:18:43.682Z
- Last checked
- 2026-10-26T00:48:53.420Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-26T00:48:52.366Z. Cached copy · Source on telegram.org
# Telegram Core
> Developer documentation for the Telegram platform: the Bot API (HTTP interface for bots), Mini Apps, and the lower-level Telegram API (MTProto) used by full clients and TDLib.
Almost every page has a Markdown version at the same URL with a `.md` suffix. Prefer the `.md` pages: the HTML pages are large and are truncated by most fetch tools. Pages without a Markdown version return 404 for the `.md` URL.
## Bot API
- [Bot API reference index](https://core.telegram.org/bots/api.md): how to make requests, get updates, and one line per method with a link to its page; read this first to find the page you need
- [Method pages](https://core.telegram.org/bots/api/methods/sendmessage.md): one page per method at `/bots/api/methods/<method-name-in-lowercase>.md`, e.g. `sendmessage.md`, `editmessagetext.md`
- [Type index](https://core.telegram.org/bots/api/types.md): one line per type with a link to its page
- [Type pages](https://core.telegram.org/bots/api/types/message.md): one page per type at `/bots/api/types/<type-name-in-lowercase>.md`, e.g. `message.md`, `messageentity.md`
- [Formatting options](https://core.telegram.org/bots/api/formatting.md): MarkdownV2, HTML and Markdown parse modes and message entities
- [Rich messages](https://core.telegram.org/bots/api/rich-messages.md): rich message methods, types, limits and formatting rules
- [Bot API changelog](https://core.telegram.org/bots/api-changelog.md): all versions with the methods and fields each one added or changed; use it to check whether a feature exists in a given version
## Bots: guides
- [Introduction to bots](https://core.telegram.org/bots.md): what bots are, how they are created and what they can do
- [Bot features](https://core.telegram.org/bots/features.md): BotFather, commands, inline mode, keyboards, payments, privacy mode, and other platform features in detail
- [Tutorial](https://core.telegram.org/bots/tutorial.md): from BotFather to a working bot, with code
- [Serverless](https://core.telegram.org/bots/serverless.md): hosting bot and Mini App backends on Telegram: projects and modules, the database, the SDK and the CLI
- [Bot FAQ](https://core.telegram.org/bots/faq.md): common questions about limits, updates and behaviour
- [Mini Apps](https://core.telegram.org/bots/webapps.md): JavaScript apps launched inside Telegram; the `Telegram.WebApp` client API, launch methods, theming and authorization
- [Payments](https://core.telegram.org/bots/payments.md): accepting payments through bots, invoices, providers and Telegram Stars
- [Inline bots](https://core.telegram.org/bots/inline.md): bots that work in any chat via @username queries
- [Games](https://core.telegram.org/bots/games.md): HTML5 games launched from bots
- [Sample code](https://core.telegram.org/bots/samples.md): example bots and libraries by language
## Telegram API (MTProto)
- [Telegram API overview](https://core.telegram.org/api.md): the API used by official and third-party clients, organized by featu
…Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| bots.business | Bots.Business - Help | documentation Developer tools No-code and automation | — | 46 | ✓ | ✓ | |
| green-api.com | GREEN-API | interface Communications APIs and SDKs | NL | 59 | ✓ | ||
| chat-sdk.dev | Chat SDK Documentation | documentation Developer tools APIs and SDKs +1 | US | 48 | ✓ | ✓ | |
| tganalytics.xyz | Telegram Mini Apps Analytics SDK | interface APIs and SDKs Data and analytics +1 | — | 52 | ✓ | ✓ | |
| langbot.app | LangBot Documentation | interface AI agents and MCP APIs and SDKs +1 | — | 50 | ✓ | ✓ | |
| sendblue.com | Sendblue API | interface Communications APIs and SDKs | US | 56 | ✓ | ||
| vibebot.gg | VibeBot | documentation Developer tools | — | 51 | ✓ | ✓ | |
| idosgames.com | iDos Games Docs | interface Gaming APIs and SDKs | — | 46 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=telegram.org · GET /v1/domain/telegram.org · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage telegram.org, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for telegram.org:
1. POST https://agentwebmap.com/v1/sites/telegram.org/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://telegram.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/telegram.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/telegram.org).
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.