POST /api/kharon/briefs/search
Price: 5 credits
Search The Brief, Kharon's sanctions and export-control investigative desk, newest article first. Narrows by free-text query and by the desk's own topic, content-type and region tags. Returns article cards with the URL alias, headline, standfirst, abstract, publication and revision dates, reading time, lede image and the full tag set; entries that point at an outside publication carry the outbound link.
Use this to find articles, then pass a returned `alias` to /kharon/briefs for the body — cards carry no article text. Values inside one filter are OR'd while the three filters intersect, so topics=[sanctions, evasion] widens whereas adding regions=[china] narrows. `search` and the tag filters are both applied by the source, so an over-constrained query answers 412 rather than an empty list. Sort order is fixed to newest first and every call starts at the newest article, so raise `count` to reach further back — asking again with the same `count` returns the same leading articles.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)search string nullable — Full-text query matched by the source across the article corpus (examples: "Iran", "shadow fleet", "semiconductors"; minLength: 1)topics array nullable — Subject tags; several values widen the result set to their union (one of: "artificial_intelligence", "enforcement", "evasion", "export_controls", "forced_labor", "global_trade_and_supply_chains", "investment", "military_end_use", "national_security", "research_security", "sanctions", "terrorism", "transnational_crime")types array nullable — Content format; several values widen the result set to their union (one of: "article", "report", "snapshot", "webinar", "column", "story_collection", "data_viz")regions array nullable — Geographic tags; several values widen the result set to their union (one of: "africa", "asia_pacific", "central_asia", "china", "europe", "iran", "latin_america", "middle_east", "north_america", "north_korea", "oceania", "russia", "south_asia")count integer required — Max number of results to return (min: 1; max: 2000)@type string (default: "KharonBriefCard")id string nullablealias string nullableurl string nullableheadline string nullablesummary string nullablemain_category string nullableread_time string nullablepublished_at string nullablecreated_at string nullableupdated_at string nullableis_external boolean nullableexternal_link object nullable@type string (default: "KharonLink")text string nullableurl string nullablelink_type string nullabletarget string nullableimage object nullable@type string (default: "KharonAsset")id string nullableurl string nullablealt string nullablewidth integer nullableheight integer nullablemime_type string nullabletopics array (default: [])@type string (default: "KharonCategory")id string nullablealias string nullableduration string nullableimage object nullable@type string (default: "KharonAsset")id string nullableurl string nullablealt string nullablewidth integer nullableheight integer nullablemime_type string nullabletypes array (default: [])@type string (default: "KharonCategory")id string nullablealias string nullableduration string nullableimage object nullable@type string (default: "KharonAsset")id string nullableurl string nullablealt string nullablewidth integer nullableheight integer nullablemime_type string nullableregions array (default: [])@type string (default: "KharonCategory")id string nullablealias string nullableduration string nullableimage object nullable@type string (default: "KharonAsset")id string nullableurl string nullablealt string nullablewidth integer nullableheight integer nullablemime_type string nullable422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — No brief matched the query and filters Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.