Public API
The front page's free side as JSON, with no key and no sign-in.
What Wavo Intelligence's front page shows a visitor, as JSON. /openapi.json describes it in OpenAPI 3.1, and each read's page here is drawn from that description.
| Property | Value |
|---|---|
| Base URL | https://terminal.cloud.wavo.me/api/v1 |
| Sign-in | None: no key, no account |
| Rate limit | 60 requests a minute for each IP address, 30 of them at once |
| Answers | JSON; every refusal an RFC 9457 problem (application/problem+json) |
| Cross-origin | Access-Control-Allow-Origin: *: any page may read an answer |
| Caching | Cache-Control: private, max-age=60: the reader may keep an answer, no shared cache may |
Reads
| Operation | Read |
|---|---|
GET /api/v1/stories | The newest stories |
GET /api/v1/stories/{id} | One story |
GET /api/v1/topics | The day's topics |
GET /api/v1/chart | Apple Music's US top ten |
Rate limit
Every answer names the bucket it spent in RateLimit-Policy ("address";q=60;w=60). A request over it is answered 429, rate_limit_exceeded, and Retry-After says when to try again. The MCP server's tool calls spend a bucket of their own.
Parameters
A read's parameters narrow its answer, each typed and optional. A value its schema refuses is a 400, invalid_parameter, naming it; a parameter a read does not take is left out.
Lists
The lists are the front page's own, a few dozen rows at most: none is paged.
Versions
The operations stay under /api/v1. What may change there, and the notice a version gets before it goes, are in Versioning.