# IJR.com

> IJR.com is a news-first platform: every story is clustered from sources
> across the political spectrum with a per-source bias breakdown, and the
> community discusses it in the open: Reddit-style boards, writer
> publications, and per-thread discussion pages. Content listed here is
> public and may be read, cited, and linked.

## News

- [News feed](https://ijr.com/discover): today's stories, each with a
  left/center/right coverage breakdown, reader votes, and discussion.
- [Storylines](https://ijr.com/discover): developing narratives tracked
  across days of coverage with key-development timelines.
- [Topics](https://ijr.com/discover): per-topic hubs under /discover/topic/.
- [News sitemap](https://ijr.com/news-sitemap.xml): fresh stories,
  Google News format.

## Community

- [Communities](https://ijr.com/c): reader-created discussion boards; every
  person, company, and place in the news also has a board under /x/.
- Discussion threads: every community post has a permalink page under
  https://ijr.com/discover/thread/ with its full reply tree.
- [Community answers](https://ijr.com/answers): reader-maintained answers
  to common questions.

## Writers

- [Journals](https://ijr.com/journals): reader publications with long-form
  posts and comments; each journal emits RSS at
  /journals/<handle>/rss.xml.

## Civic

- [2026 Election Tracker](https://ijr.com/election): the live map, polls
  and betting markets, balance of power, and every 2026 congressional
  race, with candidates, cited position research, and roll-call voting
  records on politician entity pages.

## Machine-readable

- [Sitemap](https://ijr.com/sitemap.xml)
- [Robots policy](https://ijr.com/robots.txt)

## Agents (OpenServe)

OpenServe, the family's work product, has an MCP server for agents that
act on a workspace owner's behalf. It is not a public content surface:
every call needs a workspace API key the owner mints in Settings.

- Endpoint: https://www.openserve.com/api/v1/mcp (Model Context
  Protocol over Streamable HTTP, JSON responses; POST only).
- Auth: `Authorization: Bearer os_sk_…`, a key scoped by family:
  identity, collective, site, ads, crm, email, social, brand, analytics,
  agents. A read key reads; a write key also files changes.
- What an agent can read: website visitors and audiences, ad campaigns
  and the media buyer's moves, the CRM pipeline, email lists and their
  performance, connected social pages, the brand kit, site analytics,
  and the agents and teams at work.
- What an agent never does: send an email, post to social, or apply a
  paid change on its own. It files; a person approves in Activity.

## Agents reading content (OpenServe open gateway)

An agent can find and read the family's published journals for the
person who granted it, with that person's own subscriptions and
memberships. Paid-plan reads of members-only posts pay the publisher
from the subscription pool, as web reads do.

- Discovery: https://www.openserve.com/.well-known/openserve.json
  lists the endpoints, auth and what this deployment supports.
- Scope: `content:read` on a workspace API key or an OAuth grant.
- MCP tools: search_content, check_content_access, read_content,
  get_content_usage. REST: POST /api/v1/open/search, POST
  /api/v1/open/access/evaluate, GET /api/v1/open/resources/{id}.
- The only permitted use is answering the person
  (personal_assistance). Training, redistribution and indexing are
  refused. Cite the canonical link each read returns.
- Without access, a read returns the free opening and the offers with
  links for the person. An agent never buys.