Data Hub Domain List
Retrieve the platforms currently supported by Data Hub Search and their usable domain mappings.
Overview
When you need to limit where Data Hub searches, the platform name alone is not enough: search scopes expect a supported domain value. This catalog provides the current mapping between each Data Hub platform identifier and the domain values that can be used to define those scopes.
Using a shared catalog reduces inconsistent naming across teams and prevents platform identifiers from being mistaken for executable domain filters. It is useful as reference data for search strategies, source policies, and configuration libraries that need a stable, machine-readable relationship between a platform and its searchable entry points.
Data notes
The data comes from the catalog of platforms currently enabled for Data Hub Search. Each record represents one usable domain and its corresponding platform identifier. Results are deduplicated by usable domain. A platform may appear in multiple records when it supports more than one searchable domain.
Use the Usable domain value when building include or exclude scopes. The Platform identifier is a classification label and should not be substituted for the domain. The catalog covers only platforms already connected to Data Hub Search; unsupported or retired platforms do not appear.
Example results
Each record represents one domain that can be used to constrain a Data Hub search source.
| Usable domain | Platform identifier |
|---|---|
| xiaohongshu.com | XIAOHONGSHU |
| douyin.com | DOUYIN |
| weibo.com |
Use cases
- When configuring a targeted search, select entries by Usable domain to create an explicit inclusion scope and avoid ineffective platform-name filters.
- When maintaining exclusion rules, store Usable domain values in the blocked-source list and use Platform identifier to verify which platform each rule covers.
- When reviewing platform coverage, group Usable domain records by Platform identifier to identify platforms with multiple searchable entry points.
- When maintaining shared team configurations, use Usable domain as the execution value and Platform identifier as the display category so business rules and platform classifications stay aligned.
Scope and boundaries
Returns the current complete mapping in one call; default limits are 10 calls per second and 100,000 calls per day, covering only platforms enabled for Data Hub Search.
- Good for
- Use when you need to confirm which platforms Data Hub Search currently supports.
- Use when you need valid domain values for an include or exclude search scope.
- Do not use for
- Do not use to search for posts, products, or other business records; use the relevant search Data App instead.
Failure handling
Failure and retry behavior declared by the author. We recommend including it in your system prompt when integrating.
- 1If the list is empty, retry the same call later; if it remains empty, check service availability.
- 2Authentication failures are not retryable until a valid API key is configured.
- 3After a rate-limit response, reduce request frequency before retrying; retry server errors after a short delay.
Input
Parameters required to call this App, generated from the input.schema in manifest.json.
| Field | Business name | Type | Required | Default | Enum / Constraints | Example | Description |
|---|---|---|---|---|---|---|---|
| request_note | Request note | string | No | — | — | — | Optional business note for this catalog retrieval. It does not filter or change the returned mappings. |
Output
Field structure of a single record, generated from the output.schema in manifest.json.
| Field | Business name | Type | Example | Description |
|---|---|---|---|---|
| domain | Usable domain | string | xiaohongshu.com | Domain value to use in Data Hub Search include or exclude scopes. |
| platform | Platform identifier | string | XIAOHONGSHU | Data Hub platform identifier associated with the domain. |
Record schema
Output is returned record by record. detail.output.idFieldHint
{
"type": "object",
"properties": {
"domain": {
"type": "string",
"title": "Usable domain",
"description": "Domain value to use in Data Hub Search include or exclude scopes.",
"prefill": "xiaohongshu.com"
},
"platform": {
"type": "string",
"title": "Platform identifier",
"description": "Data Hub platform identifier associated with the domain.",
"prefill": "XIAOHONGSHU"
}
},
"required": [],
"additionalProperties": false
}Integration
This App can be integrated via MCP, API, SDK, or file export. All channels share the same capabilities and pricing. Every request authenticates with the Authorization: Bearer header using an API key (long-lived, created in the Data Hub Console); MCP clients can also sign in with OAuth, no key required. More options such as CLI and Skill are on the way.
With the MCP (Model Context Protocol), you can call this App directly from AI clients like Claude and Cursor. Pick your client and auth mode, then copy the config below.
Client config
Replace the value after Bearer with your long-lived API key. Works in any client, CI, or headless environment.
{
"mcpServers": {
"meme_today__data-hub-domains": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=meme_today/data-hub-domains",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}Let AI set it up for you
Don't want to edit configs by hand? Copy the install prompt and paste it into any AI client. It will complete the setup its own way. (The prompt asks the AI to request your API key from you, so credentials never end up in chat history or shared configs.)
detail.access.mcp.composeHint
Pricing
Charged once per submitted run, regardless of how many records are returned.
Multiple billing events accumulate independently. See each item for details. Failed runs are not charged.
View creditsTry it now
Fill in the parameters and run. Results come from a real call.