asha-news

Reviewed Jan 1, 2000.

• tools: 25 tools scanned
• metadata: scanned

No findings.

Tools (25)

• asha_feed

  Latest source-backed news from the Asha News archive. Returns items with publish time, source, and citation links.

• asha_search

  Unified search across Asha News articles, active story clusters, and published generated briefs. Use this before choosing a narrower endpoint.

• asha_search_articles

  Keyword search across recent Asha News articles. Cite source URLs and Asha article/story URLs when present.

• asha_digest

  Clustered public news digest. format=markdown returns prose; otherwise JSON clusters.

• asha_share_pack

  Share-ready package for a published, cited Asha brief/story. Returns found=false when no final share pack is available.

• asha_blindspot

  Persisted Asha Blindspots / coverage gaps from posture analysis. Use only when status=available; do not infer gaps from empty or unavailable responses.

• asha_palestine

  Palestine desk timeline (evidence-classed events) with a freshness indicator, plus the desk section map (Now / The Record / Israel Exposed wings with canonical page URLs).

• palestine_check_claim

  Check one claim about Palestine against the desk's claim library and evidence archive. Returns the matched claim family, verdict, a short evidence-backed answer, and citation URLs. Rate-limited — send a single clear claim per call and relay the citations with the answer.

• palestine_genocide_case

  The full genocide-case record from the Asha News Palestine desk: what each court, UN body, rights organization, and study found — precisely characterized (provisional measures are not merits rulings; warrants are charges, not convictions) — plus attributed casualty figures, a case timeline, and an FAQ. Relay characterizations exactly and keep citation URLs.

• palestine_search_archive

  Search the Palestine evidence archive: 140,000+ upstream media records, the Killed in Gaza victims memorial, and the curated claim library. Results carry stable IDs and canonical URLs — cite those instead of scraping.

• palestine_evidence_search

  Search the Palestine evidence graph: reviewer-approved records with dates, places, assigned categories, and the source that documented each one. Returns facet counts (region, category, year, source, trust states) alongside results, so you can see the shape of the corpus before narrowing. Every record separates the upstream source's own wording (upstream.classification) from Asha's review (asha.finding) — quote the first with attribution, never relay it as an Asha finding. bot_can_cite is true only for editorially verified records; everything else is citable strictly as "this source says". Asha holds metadata and links only; media opens on the upstream record.

• palestine_evidence_record

  One Palestine evidence record by its stable ref (e.g. gl-2810), with its assigned categories, editor-asserted incident links, related records, and ranked external media candidates carrying observed link health. Media candidates are third-party destinations — Asha never hosts them, and anything graphic or ungraded requires explicit consent before it loads. A ref that is not found may simply not have cleared editorial review; treat 404 as "not published", not as "does not exist".

• palestine_evidence_health

  Operational state of the Palestine evidence pipeline: which sources are collecting and when they last succeeded, how deep the review queue is, how many records are actually published, and how reachable the external media pointers were at their last check. Aggregate counts only — it never names an unreviewed record. Use it to answer "is this archive current?" honestly before citing it, and read degraded_reasons rather than the status alone. A source with ingest_enabled:false is configured off, not broken.

• palestine_evidence_taxonomy

  The controlled vocabulary behind the Palestine evidence graph: incident_type (what happened), theme (what was hit), affected_group (who), and legal_category (what a named body says it amounts to). Call this before filtering so you use real slugs. legal_category terms are editorial-only — they are never derived from text, and record that a named authority made that characterization.

• asha_sources

  Asha News public source directory with provenance and trust metadata.

• asha_clusters_search

  Search story clusters by topic. Returns grouped multi-source coverage.

• asha_market_context

  Public market price context for supported instruments. Returns quote source, timestamp, and instrument rows.

• asha_breaking

  Breaking news: active alerts plus breaking-flagged articles with age and expiry. Poll every 60s with since={last generated_at} for deltas; notify your user on new items.

• asha_daily_brief

  Server-rendered daily brief: categorized sections with publish time + age per item, Palestine desk leading. format=markdown for chat relay, html for a styled self-contained page, json for structured data. Relay as-is.

• asha_share_payload

  Ready-to-post social share payloads for an article (x, bluesky, threads, mastodon, telegram, whatsapp, facebook, linkedin): text within platform limits, hashtags, image, and intent URL. Post verbatim; keep attribution.

• conflict_state

  Live Middle East Conflict Monitor snapshot: official alerts, geolocated OSINT events, active story clusters, EN/AR theater brief, and per-tier freshness (degraded flag). Pass since={seq} for envelope deltas. Streaming clients can use SSE at https://asha.news/api/conflict/stream instead.

• conflict_events

  Geolocated Conflict Monitor events (strike, explosion, intercept, movement, statement, thermal_confirmation) with severity, verification status, and EN/AR summaries. Filter with bbox=w,s,e,n; pass since={seq} for deltas.

• asha_editorial_guidelines

  Asha News editorial voice contract: evidence-first, openly pro-Palestine, citations preserved. Read before generating derived briefs, titles, or social posts.

• asha_mint_share_link

  Mint the stable asha.news/s/<code> short link for an article, generated brief, story cluster, or allowlisted route. Idempotent — the same target always returns the same code. Use this instead of pasting long URLs; the short link carries social preview metadata.

• asha_subscribe_newsletter

  Start a DOUBLE OPT-IN newsletter signup for an email address. Asha emails a confirmation link; nothing is delivered until the person clicks it. Only submit an address the person gave you in this conversation, and tell them to check their inbox — you cannot confirm on their behalf.