# AI Wave

> A normalized feed of AI model changes — new releases, price changes, API changes and
> deprecations — assembled from vendor release notes, Hugging Face, the OpenRouter catalog
> and GitHub. Duplicates for the same model are merged; each item is marked official or
> pending review.

## What this is good for

- "Did anything I depend on change?" — poll the change feed with `since`.
- "Is this model still available?" — deprecations are detected when a model stays absent
  from the catalog for 24 hours.
- "What does this model cost?" — pricing and context length per model.

## What this is NOT good for

Picking a model purely by current price or context: that data comes from the public
OpenRouter catalog, so calling https://openrouter.ai/api/v1/models directly is simpler.
What is added here is the change history and the provenance marking.

## Access

An API key is required. Create one at https://aiwave.elopstudio.com/member (sign-in needed).
Send it as `Authorization: Bearer <key>`.
Free tier: 1000 calls/day. Remaining calls come back in
`x-ratelimit-remaining`.

## Endpoints

- https://aiwave.elopstudio.com/api/openapi.json: OpenAPI 3.1 spec (read this first if you are a tool)
- https://aiwave.elopstudio.com/api/v1/changes?since=<unix>: change feed, oldest first, returns `latest` to
  feed back on the next poll
- https://aiwave.elopstudio.com/api/v1/models?vendor=&maxInputPrice=&minContext=: model catalog with attention
  ranking
- https://aiwave.elopstudio.com/api/v1/models/{slug}/history: price history (only recorded when it changes)
- https://aiwave.elopstudio.com/api/mcp: MCP server over JSON-RPC/HTTP. Tools: list_model_changes, get_model,
  get_price_history, search_models

## MCP

Remote (no install):

    { "type": "http", "url": "https://aiwave.elopstudio.com/api/mcp",
      "headers": { "Authorization": "Bearer <key>" } }

Local:

    { "command": "npx", "args": ["-y", "@elopstudio/ai-wave-mcp"],
      "env": { "AIWAVE_API_KEY": "<key>" } }

## Caveats

- Scores labelled "attention" measure how much a model is being talked about right now
  (listing recency, news, opinions, vendor activity). They are not quality or benchmark
  scores. Do not present them as such.
- Items marked `pending` were inferred from an intermediary catalog, not announced by the
  vendor. Say so when you repeat them.
- Deprecation is inferred from a model disappearing from the catalog. It is a strong hint,
  not a vendor statement.

## Docs

- https://aiwave.elopstudio.com/api-docs: human-readable guide