Content Analysis reference
Every Content Analysis operation, from the registry
9 operations wired in the registry, 9 of them proven by real traffic, 3 catalogued but not yet wired.
Choose a Content Analysis operation
Start with the object your task needs. The groups below use the current catalogue; open an endpoint to check accepted identifiers, filters, price and availability before retrieving.
Products and categories
- Content Analysis categories — Monocrawl's own mention-classification taxonomy (taxonomy id monocrawl.content_analysis.v1), including the full keyword list behind each category so any classification can be audited. Static, costs no credits.
Other operations
- Content Analysis filters — The filterable fields for the content analysis endpoints — field, type, operators, allowed values, which endpoints accept it and whether it is applied upstream or locally. Generated from the adapter's own filter implementation, so it cannot drift. Static, costs no credits.
- Content Analysis languages — Reference list of the ISO-639-1 language codes content analysis can genuinely filter on, each marked with which source honours it. Static, costs no credits.
- Content Analysis locations — Reference list of the ISO-3166 alpha-2 country codes content analysis can genuinely filter on — publisher country for news, storefront for rating-distribution. Static, costs no credits.
- Keyword mention trends — Mention volume and sentiment for a keyword bucketed by day, week or month across the sources we can reach. Bucket heights are bounded by each source's per-query cap, so the series is a shape, not a census — the response says so explicitly.
- Keyword rating distribution — Real 1-5 star histogram for a keyword that resolves to an App Store app, built from actual published reviews plus Apple's own lifetime average. If the keyword resolves to nothing rateable it returns 404 — no histogram is ever synthesised.
- Keyword sentiment breakdown — Positive / neutral / negative split for a keyword with mean, median and a score histogram, plus the most positive and most negative mentions. Lexicon-based and fully deterministic — the method, its thresholds and its limits are returned with every response.
- Keyword mention summary — Aggregate view of a keyword's mentions: volume, per-source breakdown, sentiment split, category mix, top publishers and top terms — all computed deterministically from the mentions we could reach.
Search and discovery
- Keyword mention search — Web citations of a keyword from news, Hacker News and Reddit with deterministic per-mention sentiment (in-adapter lexicon, no AI), Monocrawl category labels and per-source provenance. Fans out to 3 upstreams; coverage is partial and every response names what it could not consult.
Check fields and collection limits
Use the endpoint’s declared parameters and returned continuation. Filters from another platform do not automatically apply here. Preserve source identifiers, URLs and warnings; a successful page does not establish complete history. Published response schemas identify whether they come from a reviewed shaper or observed response shapes.
Agents can use get_endpoint for the current contract and get_docs with topic platforms/content_analysis to read this page. The coverage guide explains nulls and partial results, and the production guide covers budgets and recovery.
Operations
Content Analysis
Each row is a registry operation: expand it for parameters, a curl built from the registry's own examples, and a Markdown copy of the whole entry. The badge on the right is the operation's state, read at request time — we publish all three rather than rounding up. Recorded proof is historical, not a guarantee of current availability.
- live · proven
- a real upstream response has been served through this API and recorded
- wired · unproven
- a real-data route is registered, but qualifying proof is absent; permission or capacity restrictions may apply
- sample · free
- no live upstream — /v1 refuses it, /sandbox returns a marked sample
Content Analysis
9 operationsCatalogue only
Designed, not yet wired
These ids are in the Content Analysis catalogue but have no registry row, so they are targets rather than operations. On /v1 each answers 501 ENDPOINT_NOT_AVAILABLE at no charge; the same path under /sandbox returns a representative sample marked synthetic: true. They are listed separately so you can distinguish planned coverage from the operations available above.
/v1/content_analysis/indexed-search/v1/content_analysis/indexed-summary/v1/content_analysis/indexed-phrase-trends
Elsewhere
The same registry, other shapes
- Content Analysis overview — supported data categories and use cases for this platform.
- Full endpoint reference — every platform on one page.
/openapi.jsonor/openapi.yaml— the machine-readable contract, for Postman, Insomnia or a client generator.GET /v1/utility/endpoints?platform=content_analysis— the same rows to your code at runtime, for 0 credits.