Read-only personal data APIs

Discord and Telegram data, ready as clean JSON.

dataz.md turns conversations, communities, contacts, and message history available to a connected account—including channels and chats the account can access but does not own—into read-only APIs and local MCP tools (Model Context Protocol, for connecting AI clients like Claude) for developers, data teams, and community operators.

Get started Try the live demo

Check the docs See pricing

Read-only by design No sending, editing, deleting, reacting, joining, or mutating account state.

Discord, Telegram, and MCP Explore APIs directly, or expose the same read-only surfaces to local MCP-compatible agents.

Tenant runtimes Each customer provisions isolated API infrastructure with its own endpoint and key.

Platforms

Two sources, one product flow

dataz.md is a hosted service that turns a Discord or Telegram account you own into read-only JSON APIs and local MCP tools. Discord and Telegram stay platform-native where it matters, while the product experience stays consistent.

Discord

Servers, channels, DMs, forums, invites

GET /guilds GET /channels/{channel_id}/logs GET /dms/{channel_id}/messages Open Discord docs Browse Discord endpoint reference

Chats, channels, contacts, topics, private messages

GET /chats GET /chats/{chat_id}/members GET /dms/{dm_id}/messages Open Telegram docs Browse Telegram endpoint reference

Live demo

Try read-only requests before creating a workspace

Switch between Discord and Telegram, choose a data surface, and inspect a friendly preview plus the raw JSON response from the configured demo APIs.

Ready to check demo account Run a Discord connection check when you are ready.

Discord

Explore community data

Server

Channel

Private surfaces

Direct messages

Explore chat data

Chat or channel

Account graph

People and private chats

Demo response

Example response

GET /guilds

Choose a read-only request to see live demo account data.

[
  {
    "id": "123456789012345678",
    "name": "Example server"
  },
  {
    "id": "987654321098765432",
    "name": "Second example server"
  }
]

Open this surface in docs Create my workspace

API docs

Browse the endpoints and test requests live

Open the interactive docs to inspect paths, parameters, response schemas, and run read-only requests from the browser.

Interactive API reference. Start with Discord or Telegram demo APIs, then switch to your tenant endpoint after onboarding.

Check the docs

MCP for agent workflows. Run dataz-mcp locally to expose the same read-only Discord and Telegram surfaces to MCP-compatible clients.

Set up MCP

Use cases

For teams that need messaging data to be queryable

Developers

Build internal search, migration scripts, enrichment jobs, AI workflows, and MCP-backed agent context without maintaining platform-specific auth and pagination.

Data teams

Extract community activity, channel history, contact graphs, invite references, member lists, and metadata for analysis.

Community managers

Understand conversations across servers, groups, channels, and private surfaces without asking moderators to export data manually.

Start

Create a workspace, select Discord, Telegram, or both, complete setup, and reveal a tenant API key once.

Get started Browse Telegram docs