Delete a community report
Does not delete the entities it grouped — only the summary.
Full-key operation
Does not delete the entities it grouped — only the summary.
Authorization
api_key_header Every request carries an organization API key. A key has one of two scopes. A full key reaches every operation in this document and belongs on your server. A search key is the one to ship in a browser widget or a storefront page: it reaches only the operations marked x-nova-key-scope: search — searching, federated search, recommendations, event ingestion, and the visitor-facing AI operations (semantic and image search, voice transcription and voice search, assistant chat, and the visitor's own conversation). It cannot write documents or read or change configuration; any other operation answers 403. AI operations are paid in credits from the organization's wallet whichever key calls them (402 when the balance runs out), and a search key needs X-NOVA-SESSION-ID on them: the session is what a conversation belongs to, and what the per-session allowance (429) is counted against. A key of either scope may additionally carry restrictions set in the console: an allowlist of collections (403 elsewhere), a forced filter_by per collection that is ANDed into every search (document-level access control), an allowlist of fields (include_fields is limited to it and a request naming any other field in query_by, facet_by, sort_by, filter_by or highlight_fields answers 400), an IP/CIDR allowlist and an Origin/Referer allowlist (403), and a per-key rate limit (429 with Retry-After).
In: header
Path Parameters
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X DELETE "https://example.com/graph/communities/string"{ "id": "string"}Answer a question via a Global Search primer plus Local Search follow-ups (DRIFT) POST
GraphRAG's "DRIFT" mode: a primer step (`globalSearchGraph`'s map-reduce over `level`'s community reports, at most `max_communities` of them) proposes an intermediate answer plus specific follow-up questions the reports can't answer on their own. Each of the first `max_follow_ups` follow-ups is then answered by a Local Search step — the entities most relevant to that follow-up by embedding similarity, their one-hop graph neighbors, and any claims about them (see `generateGraphEntities`) — and a final model call synthesizes the primer answer with every follow-up's local answer into one response. This is single-level DRIFT: follow-ups are answered but do not themselves spawn further follow-ups. Requires at least one `generateGraphCommunities` run; a collection with no entities yet still runs the primer step but every follow-up comes back with an empty `answer`.
List extracted claims GET
Structured factual assertions ("covariates") about this collection's entities, extracted alongside them by `generateGraphEntities` — see `GraphClaim`.