AI & MCP
Natural Language Search
Natural Language Search retrieves records by meaning rather than requiring exact terms.
Endpoints
GET /v1/icd/nl-searchGET /v1/icdb/nl-search
Example
Code
Parameters
| Parameter | Required | Purpose |
|---|---|---|
search | Yes | Descriptive query |
country | No | Primary-country filter |
entity | No | Entity filter |
source_component | No | Component-type filter |
date_from | No | Earliest date, YYYY-MM-DD |
date_to | No | Latest date, YYYY-MM-DD |
page | No | One-based page |
per_page | No | Requested page size |
top_k | No | Retrieval candidate limit |
The API Reference is authoritative for bounds and endpoint-specific behavior.
Response
Results include the canonical title, summary and source metadata when available, plus a relevance score. A score is a comparative retrieval signal; it is not a probability, a truth rating, or an authorization indicator.
When Not to Use It
- For a known Component ID, use direct Component ID lookup.
- For a known UUID, use the detail endpoint.
- For exact terms and filters, structured search is usually more efficient.
- For a synthesized answer, use Domain GenAI.
Last modified on
