RuntimeBuzz

API

Read-only JSON for article search and discovery

Search RuntimeBuzz articles by title, excerpt, tags, section, author, or body text. Each result includes the title, excerpt, site path, and canonical URL.

Endpoint

GET /api/search

Query parameters

  • q — Search text. Every whitespace-separated token must appear somewhere in the article title, excerpt, tags, section, author, or body (case-insensitive). An empty q returns { "query": "", "count": 0, "articles": [] }.
  • limit — Optional. Maximum number of articles in the response (default 80, capped at 200).

Response

JSON with application/json; charset=utf-8. Top-level fields:

  • query — The trimmed search string you sent.
  • count — Number of articles returned.
  • articles — Array of objects: title, excerpt, path (relative, e.g. /software/editorials/example), and absolute url on runtimebuzz.com.

Example request

curl -sS "https://runtimebuzz.com/api/search?q=cursor&limit=5"

Replace the host when testing against a local server (for example http://localhost:3001).

Article index (read finder)

GET /api/read-finder-index.json returns lightweight metadata for every post under content/blog/ (no markdown body). Used by the on-site read-finder widget with Fuse.js. Responses support ETag and If-None-Match (304 when unchanged).

Top-level fields: version, generatedAt, fingerprint (content change token), articles (array of path, title, excerpt, tags, tagsJoined, section, author, date).

curl -sS -D - "https://runtimebuzz.com/api/read-finder-index.json" | head