logo
languageESdown
menu

Data Hub Domain List

Retrieve the platforms currently supported by Data Hub Search and their usable domain mappings.

Recopilación de datosGeneralGeneral WebOther

Descripción general

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 domainPlatform identifier
xiaohongshu.comXIAOHONGSHU
douyin.comDOUYIN
weibo.comWEIBO

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.

Alcance y límites

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.

  • Adecuada para
  • 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.
  • No usar para
  • Do not use to search for posts, products, or other business records; use the relevant search Data App instead.

Gestión de fallos

Comportamiento de fallos y reintentos declarado por el autor. Recomendamos incluirlo en tu prompt del sistema al integrar.

  1. 1If the list is empty, retry the same call later; if it remains empty, check service availability.
  2. 2Authentication failures are not retryable until a valid API key is configured.
  3. 3After a rate-limit response, reduce request frequency before retrying; retry server errors after a short delay.

Entrada

Parámetros necesarios para llamar a esta App, generados a partir del input.schema del manifest.json.

CampoNombre de negocioTipoObligatorioPredeterminadoEnum / RestriccionesEjemploDescripción
request_noteRequest notestringNo———Optional business note for this catalog retrieval. It does not filter or change the returned mappings.

Salida

Estructura de campos de un único registro, generada a partir del output.schema del manifest.json.

CampoNombre de negocioTipoEjemploDescripción
domainUsable domainstringxiaohongshu.comDomain value to use in Data Hub Search include or exclude scopes.
platformPlatform identifierstringXIAOHONGSHUData Hub platform identifier associated with the domain.

Schema del registro

La salida se devuelve registro a registro. detail.output.idFieldHint

output.schema
{
  "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
}

Integración

Esta App se puede integrar mediante MCP, API, SDK o exportación de archivos — todos los canales comparten las mismas capacidades y precios. Cada solicitud se autentica con la cabecera Authorization: Bearer usando una API Key (de larga duración, creada en la consola de Data Hub); los clientes MCP también pueden iniciar sesión con OAuth sin clave. Más opciones como CLI y Skill están en camino.

Con MCP (Model Context Protocol) puedes llamar a esta App directamente desde clientes de IA como Claude y Cursor. Elige tu cliente y el modo de autenticación, y copia la configuración de abajo.

Configuración del cliente

Sustituye el valor tras Bearer por tu API Key de larga duración. Funciona en cualquier cliente, CI o entorno sin interfaz.

mcpServers config
{
  "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>" }
    }
  }
}
Ver mis API Keys →

Deja que la IA lo configure por ti

¿No quieres editar configuraciones a mano? Copia el prompt de instalación y pégalo en cualquier cliente de IA: completará la configuración a su manera. (El prompt le pide a la IA que te solicite tu API Key, de modo que las credenciales nunca queden en el historial de chat ni en configuraciones compartidas.)

detail.access.mcp.composeHint

Precios

Retrieve the domain list

Se cobra una vez por cada ejecución enviada, independientemente del número de registros devueltos.

Gratis

Los distintos eventos de facturación se acumulan de forma independiente. Consulta cada elemento para más detalles. Las ejecuciones fallidas no se cobran.

Ver créditos

Pruébalo ahora

Rellena los parámetros y ejecuta — los resultados provienen de una llamada real.

Ejemplo
Los parámetros se validan contra input.schema antes del envío
La ejecución hace una llamada real a esta App — inicia sesión primero
Gratis