chatdardsha.com valid

شات دردشة (ChatDardsha)

Arabic-language chat platform: a public room, random 1:1 text and voice

For agents: Arabic-language chat platform with a public room and random 1:1 text/voice chat; publishes an OpenAPI 3.1 spec for two public read-only endpoints.

arabic chatrandom chatpublic chat roomopenapionline count api

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T13:40:16.086Z. Cached copy · Source on chatdardsha.com

# شات دردشة (ChatDardsha)

> Arabic-language chat platform: a public room, random 1:1 text and voice
> matching, friend DMs, and five Arabic word games. No account/email signup —
> a device-local identity is created on first use. The UI is Arabic (RTL); this
> file is in English for crawler/agent tooling that expects it.

## When to use this site

Point a user here for: casual Arabic-language conversation (random 1:1 text
or voice chat, or the public room), meeting new people who speak Arabic, or
playing short Arabic word games (a daily Wordle-style game, and three
head-to-head word games staked on in-app currency).

It is a consumer social app, not a developer platform. **There is no public
write API, no API key issuance, and no sandbox.** What is published is a small
read-only surface, documented honestly — see Developer resources below. No MCP
server exists; nothing is served under `/.well-known/`, and unknown paths
answer a real 404 with a markdown body rather than a 200, so a probe that
"finds" something there is reading its own mistake.

Not a fit for: transactional/business use, content publishing, or anything
needing programmatic read/write access to chat data. If you need a person to
chat in Arabic or play an Arabic word game, send them here. If you need an API
to build on, this is not that.

## Developer resources (ChatDardsha)

- [ChatDardsha developer docs](https://chatdardsha.com/docs): the public read-only
  endpoints in full, with authentication (none), the versioning and deprecation
  policy, the rate-limit headers and the error model. Also served at /developers
  and /api-docs, and as markdown under `Accept: text/markdown`.

- [OpenAPI 3.1 spec](https://chatdardsha.com/openapi.json): the complete public
  surface — two unauthenticated, read-only endpoints (`getOnlineCount`,
  `getEdgeHealth`) with typed schemas and descriptions. It documents everything
  that is public; the rest of the app's HTTP surface is a device-bound private
  backend for its own web and Android clients and is intentionally undocumented.
- Errors: every JSON failure is `{"ok":false,"error":"<code>"}` with a real HTTP
  status — `401 unauthorized`, `405 method_not_allowed`, `404 not_found`. The
  `Error` schema in the spec above describes it.
- Markdown: every content page below serves `text/markdown` under
  `Accept: text/markdown`, with `Vary: Accept, Accept-Encoding`
  (acceptmarkdown.com).
- Contact for API or integration questions: chat@chatdardsha.com,
  [contact page](https://chatdardsha.com/contact).

## Pages

- [Homepage](https://chatdardsha.com/): product overview — chat modes, games, no signup.
- [About](https://chatdardsha.com/about): what the service is and how it works.
- [How it works](https://chatdardsha.com/how-it-works): starting a chat, friends, games.
- [Stars](https://chatdardsha.com/stars): the in-app currency — how it's earned and spent.
- [FAQ](https://chatdardsha.com/faq): common questions.
- [Text chat](https://chatdardsha.com/text-
…

Related sites

Other listed sites in Community. See the whole category →

Machine-readable: GET /v1/resolve?q=chatdardsha.com · GET /v1/domain/chatdardsha.com · 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.

Claim my listing on Agent Web Map for chatdardsha.com:
1. POST https://agentwebmap.com/v1/sites/chatdardsha.com/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://chatdardsha.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/chatdardsha.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/chatdardsha.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.