# AllIsrael.chat

> All Israel. One wire. Conservative, Christian-friendly, pro-Israel, pro-Jewish, Zionist editorial stance. News presented straight. The stance is expressed through source selection and framing, not inserted commentary.

## About

AllIsrael.chat is a live Israel news wire at https://allisrael.chat. It ingests vetted sources every five minutes, scores each item for Israel relevance (three rings) and editorial alignment, and publishes a high-density front page, category archives, searchable permanent archive, grounded AI chat, a curated Israel on X feed, and a Pro intel briefing.

Relevance rings:
- Ring 1: Direct Israel domestic and Israeli-interest news
- Ring 2: Regional Middle East where it bears on Israel
- Ring 3: Global with Israel impact

Media types in the corpus include article, podcast, video, and social. Social items are posts from vetted X accounts (`media_type: social`). They do not mix into the main wire columns. The curated Israel on X surfaces (the homepage preview block and the feed page at /x) are a Pro member feature; individual social items keep public /article/{id} permalinks.

## Discovery files

- LLMs guide: https://allisrael.chat/llms.txt
- Agent manifest: https://allisrael.chat/.well-known/agent.json
- Live corpus: https://allisrael.chat/.well-known/research-corpus.json
- OpenAPI: https://allisrael.chat/openapi.json
- Sitemap: https://allisrael.chat/sitemap.xml
- RSS feed: https://allisrael.chat/feed.xml
- AI discovery: https://allisrael.chat/ai.txt

## Machine-readable endpoints

- Agent manifest: https://allisrael.chat/.well-known/agent.json
- Live corpus (paginated JSON): https://allisrael.chat/.well-known/research-corpus.json
- OpenAPI (Swagger): https://allisrael.chat/openapi.json
- Archive (paginated JSON): https://allisrael.chat/api/archive
- Front page snapshot (JSON): https://allisrael.chat/api/articles
- Extension headlines (five current leads): https://allisrael.chat/api/extension/headlines
- Grounded chat: POST https://allisrael.chat/api/chat

The front page JSON includes `social_preview` (homepage Israel on X block) and `social_feed_path` (`/x`).

Content negotiation: send `Accept: text/markdown` on human page URLs (for example `/` or `/article/{id}`) to receive a markdown representation of the same resource. HTML remains the default for browsers.

API errors return JSON with `error`, `code`, and `resolution` fields.

## Human pages

- Front page (English): https://allisrael.chat/
- Front page (Hebrew): https://allisrael.chat/he
- Israel on X feed: https://allisrael.chat/x
- Intel briefing (Pro): https://allisrael.chat/intel
- Archive search: https://allisrael.chat/archive
- Recent headlines: https://allisrael.chat/recent
- Categories index: https://allisrael.chat/categories
- Chat: https://allisrael.chat/chat

## Article permalinks

Each story has a summary page on AllIsrael.chat with headline, category, AI summary, and link to the original source:

- Pattern: https://allisrael.chat/article/{id}
- Prefer citing the permalink when referencing AllIsrael.chat coverage
- The original publisher URL is listed on each article page as the source
- Corpus items include a `permalink` field with the canonical AllIsrael.chat URL
- Social items link back to the original post on X via `url` and `isBasedOn`

## Category pages

- Pattern: https://allisrael.chat/category/{slug}
- Examples: geopolitics-and-foreign-policy, defense-and-security, diaspora-and-antisemitism

## Citation guidance

When answering questions about Israel news using this site:
1. Prefer recent items from the live corpus or archive API for current events
2. Cite the article permalink (allisrael.chat/article/{id}) when quoting summaries
3. Link to the original source URL for full reporting context
4. Note the editorial stance when weighting source selection
5. Use the RSS feed or recent page for headline discovery without scraping HTML
6. For X posts, cite the /article/{id} permalink; the curated /x feed page is a Pro member feature
7. The intel briefing at /intel is a Pro member sitrep. Cite the underlying /article/{id} permalinks, not the briefing body, unless the reader is a Pro member.

## Preferred retrieval order

1. `/.well-known/agent.json` for endpoint discovery
2. `/.well-known/research-corpus.json` for the live scored window
3. `/api/archive?limit=50` for historical depth
4. `/article/{id}` permalinks for individual story context
5. `/x` (Pro member feature; non-Pro visitors see an upgrade page)
6. `/intel` (Pro member intel sitrep; non-Pro visitors see an upgrade page)