Skip to content

Alethman API and MCP

Alethman reads India’s news as it is published, groups it into stories, and reads each for what it means for the sectors and states you follow. This is how you take that into your own systems: a REST API for programs, and an MCP server for AI assistants. Both read through your workspace, under one key.

REST API

For your programs

Thirteen endpoints, plain JSON, cursor pagination, one error shape. Mirror articles into a warehouse, put sector readings on a wall screen, file reports where your team reads them.

curl "https://dash.alethman.com/api/v1/stories?order=risk" \
-H "Authorization: Bearer $ALETHMAN_KEY"
Make your first request →
MCP server

For your AI assistant

Eleven read-only tools for Claude, Cursor and any client that speaks the Model Context Protocol. Ask what moved in your sectors this week and get an answer from your own workspace.

claude mcp add --transport http alethman \
https://dash.alethman.com/api/mcp \
--header "Authorization: Bearer $ALETHMAN_KEY"
Connect a client →
13REST endpoints
11MCP tools
120requests a minute per key
v1stable; additions only

Every endpoint returns what the dashboard shows, read through the same workspace scope: the sectors and states your workspace follows.

  • ArticlesEvery article in scope, with its outlet, sectors, states and story.
  • StoriesArticles about one event, grouped, with independent outlets and risk.
  • One story in fullSummary, places, articles, who the reporting names, coverage by country.
  • Sector outlooksEach sector’s reading: risk, direction, verdict and the stories behind it.
  • ForecastsDated yes-or-no questions with probabilities and a public track record.
  • Coordination findingsStories the reporting links into one pattern, graded by evidence.
  • ReportsYour compiled reports, as JSON to compute on or Markdown to read.
  • Your sourcesThe feeds your workspace follows, their health, and what they carried.
  • Your workspaceWhat the key’s workspace follows and which scopes the key carries.
  1. Quickstart: make a key, call the API, read a story, in five minutes.
  2. Authentication and keys: who can make keys, scopes, expiry, rotation.
  3. Countries and scopes: what a workspace follows, and the sector and state keys every filter takes.
  4. Errors and Rate limits: what can go wrong and how to back off.
  5. Guides: whole tasks, end to end, in curl, Python and JavaScript.

The whole API is one OpenAPI 3.1 document, and these docs are available to language models as llms.txt and llms-full.txt.