Whale Data Center External Docs

External docs are for data consumers. They explain which platforms Whale covers, which data types are available, and how authorized consumers query and retrieve data through APIs. These pages focus on what can be queried, how to query it, and how to interpret results. They do not explain internal collection, ingest, or operations implementation.

Collector registration, capability declaration, task dispatch, ingest contracts, internal OpenAPI, and operations are protected engineering materials and are not exposed on the public site.

OrderPageAudienceQuestion answered
1QuickstartAPI integratorsRun the first authenticated query
2Portal and SubscriptionsOrganization owners and developersUnderstand applications, subscriptions, keys, and scope
3Platform CoverageProduct and solution teamsUnderstand platforms, content types, and fields
4Data AccessAPI integrators and data engineersSearch, filter, and retrieve details
5Production GuideEngineering and operationsApply timeouts, retries, and compatibility rules
6MCP IntegrationAI application developersConnect Whale search tools to an MCP host
7Public API ReferenceDevelopersBrowse consumer endpoints and schemas online

Documentation Modules

ModuleDescription
Platform CoverageSupported platforms, content types, common fields, and platform-specific mapping
Data AccessHow consumers query, search, and retrieve authorized data with API keys
Versions and SnapshotsHow body changes, transcript changes, and metric updates are represented
Metrics DimensionsHow platform, dataset, content type, time windows, and metric semantics are interpreted

External consumers do not need to understand collector registration, task dispatch, ingest internals, databases, object storage, OpenSearch, Milvus, or internal queues.

Capability Boundary

CapabilityExternal meaning
Platform coverageWhale returns unified data by platform enum and preserves platform-specific fields
Keyword searchExact keywords, brands, people, URLs, and topics
Semantic searchSimilar meaning, cross-language, and weak keyword scenarios
Hybrid searchRecommended default, combining keyword, vector, quality, and recency
Detail loadingLoad full content, versions, parts, facts, and snapshots by document_id
MetricsObserve volume, platform distribution, metric trends, and processing status within authorization scope

Documentation Boundaries

  • External docs describe platform coverage, data access, authorization boundaries, and result semantics.
  • External docs must not expose collector API keys, internal tasks, databases, object storage, queues, or collector troubleshooting details.
  • Public API Reference is generated from consumer-authenticated operations in the primary contract. The complete contract remains internal.