# DataXAPI Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## DataXAPI

Read public RedNote, Douyin and WeChat data from your AI agent

- Record: https://musedirectory.ai/connector/dataxapi
- Category: Research & Data
- Developer: DataXAPI Team (https://dataxapi.com)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 190ms, checked 2026-11-21T17:15:44Z
- Endpoint: https://api.dataxapi.com/mcp
- Auth: Needs an access key; Pricing: freemium
- Screening: Screened, no issues found (2026-11-21T02:19:56Z)
- Source: Submitted by its builder and screened before listing

REST API, SDKs and a remote MCP server for public data from Douyin, Xiaohongshu, WeChat, TikTok and X. Pay per call; failed calls are free. Remote MCP server at https://api.dataxapi.com/mcp with API key auth. Five tools let an agent find an endpoint from a plain-language need, call it and read long results.

Example request: "Find recent public posts about a brand on Xiaohongshu and summarize their engagement."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use DataXAPI to help me. It is a free service with an MCP server at https://api.dataxapi.com/mcp. It needs an API key from DataXAPI Team; ask me to enter it through your secure credential prompt. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- find: Find the capability for a need in plain words, English or Chinese: up to 5, each with its required parameters, price and a ready call. Free, no key. Given a post's link or share text, the capabilities that take it as url: its files for words like download, its transcript for tran
- describe: The contract of 1 to 5 capabilities: each parameter with its meaning and values, fields per view, paging, price and the most a call can cost, examples. Free, no key. Use when unsure of a parameter.
- call: One page from one capability, charged per call, per item or per minute; errors are free. Give only the parameters `describe` lists for it. The result's first line gives the charge, the balance and how to go on: `cursor` for the next page (charged), `read_more` for the rest of a r
- read_more: The rest of a result `call` cut, or it in another view. Free, nothing is fetched again; kept 24 hours. Needs the key that made the call.
- account: balance: balance, key budget and spending. receipt: what one call was charged. usage: calls and charges by day or capability. status: which capabilities are up (no key). Free.

Screening checks:
- MCP handshake: pass (Answered in 100ms)
- Domain against threat feeds (Cloudflare security DNS): pass (api.dataxapi.com, dataxapi.com not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (5 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (scrapes public social platform data, possible platform terms of service issues)
