Moonlytics Data API
Digital asset market, social and intelligence data through one normalized interface — one asset identity, one schema, one time base.
The Moonlytics Data API is currently in development. There is no public endpoint, no self-serve sign-up, no API key issuance and no published rate limit today. The data described across this site is live and in production, but it is reached through internal service interfaces that back the applications rather than through a public API.
Nothing on this page is presented as available. Endpoints will be documented here when they exist and can be called, not before.
What exists today
The layer behind the API is not hypothetical. It runs continuously and it currently holds:
Applications reach it through authenticated internal services: a market and social observation service backed by a relational store, and a set of data services for metadata, ecosystem series, news and narratives. Those interfaces are authenticated, subscription-aware and cached, and they are what moonboard.ai reads from in production.
The public API is the work of exposing that surface safely — stable contracts, authentication and key management, quota enforcement, redistribution boundaries that respect the upstream provider agreements, and documentation that does not go stale. That work is in progress.
Design principles it will follow
These are settled, and they constrain what the API can look like when it ships:
- Canonical identifiers everywhere. Every resource is addressed by the Moonlytics asset id. Symbol lookup exists as a search operation that returns candidates, never as an addressing scheme.
- Explicit timestamps on every value. No response contains a number without the time it describes.
- Native cadence preserved. Hourly and daily series stay separate resources. No silent resampling.
- Nulls survive. Absent means absent in the response, as it does in storage.
- Documented pagination and stable ordering, so a paged pull is reproducible.
- Errors that say what went wrong, with a stable machine-readable code.
Planned surface area
Product planning, not a release schedule. Every row below is a candidate area, and the last column states what it would be built on — which is the honest measure of how far away it is.
| Area | Status | Purpose | Underlying data |
|---|---|---|---|
| Assets API | Planned | Resolve and look up canonical asset identities, provider mappings and categories. | Asset registry (live internally) |
| Market API | Planned | Hourly market observations, current and historical. | Observation store (live internally) |
| Social API | Planned | Social volume, interactions and dominance series. | Observation store (live internally) |
| Sentiment API | Planned | Asset-level sentiment series, served with its activity volume. | Observation store (live internally) |
| News API | Planned | The deduplicated news window. | News feed (live internally) |
| Narrative API | Planned | Hourly topic snapshots and their movement. | Narrative snapshots (live internally) |
| Ecosystem API | Planned | Daily channel, repository and contributor series. | Ecosystem series (live internally) |
| Historical API | Planned | Range queries across any stored series. | Observation store (live internally) |
| Search API | Planned | Find an asset by symbol, name or provider identifier. | Asset registry (live internally) |
| Scores API | Planned | Published composite scores alongside their inputs. | Methodology layer |
Not planned as public data
Some things will not be exposed regardless of demand, and it is fairer to say so now:
- Raw provider payloads. Redistribution of an upstream provider's data in its original form is a licensing matter, not a technical one. What the layer can offer is its own normalized and derived output, within the terms it operates under.
- Source article text. The news feed carries generated event summaries, not publisher content.
- Post-level social content. The layer stores aggregates. It does not hold or serve individual posts.
What to do in the meantime
If you are evaluating whether this data would be useful to you, the fastest path is to look at what has already been built on it. Moonboard renders the full stack — market, social, sentiment, ecosystem, news and narratives — against the live market.
If you have a specific integration or research need, write to us. That is currently a real conversation with the people who run the pipeline rather than a queue behind a waitlist form.
Related
- Developer portal — integration concepts and what is documented so far.
- Canonical data model — the shapes the API will serve.
- Designing APIs for AI agents — how agent consumption shapes the design.
- Status — what is operational today.