esug.org valid

HyperKitty Mailing List Archives

HyperKitty is the web archive component of Mailman 3. It exposes a complete, well-documented, read-only **JSON REST API** that mirrors every page on this site. AI agents, bots, and crawlers SHOULD use the REST API instead of scraping HTML — it is faster, cheaper, more reliable, paginated, and friendlier to the server.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T05:58:59.485Z. Cached copy · Source on esug.org

# HyperKitty Mailing List Archives

> HyperKitty is the web archive component of Mailman 3. It exposes a complete, well-documented, read-only **JSON REST API** that mirrors every page on this site. AI agents, bots, and crawlers SHOULD use the REST API instead of scraping HTML — it is faster, cheaper, more reliable, paginated, and friendlier to the server.

## TL;DR for AI agents

- **DO NOT scrape the HTML pages** at `/hyperkitty/list/...`, `/hyperkitty/archives/...`, etc. The HTML is a presentation layer over the API and is rate-limited / fragile.
- **DO use the REST API** under `/hyperkitty/api/`. All endpoints return JSON and serve the same archive data the website does.
- **DO use pagination** (`?limit=...&offset=...`). Default page sizes are small; never request unbounded data.
- **DO identify yourself** with a descriptive `User-Agent` header (e.g. `MyBot/1.0 (+https://example.com/bot)`).
- **DO respect `robots.txt`** and any `Retry-After` headers on `429` responses.
- **DO cache** responses where reasonable; archive content is largely immutable.

## API base URL

HyperKitty is always deployed under the `/hyperkitty/` path. The web UI lives at:

```
<origin>/hyperkitty/
```

and the JSON REST API root is:

```
<origin>/hyperkitty/api/
```

All endpoint paths below are relative to the site origin (i.e. they include the `/hyperkitty/` prefix).

## Endpoints

All endpoints are `GET` and return JSON. Paginated endpoints accept `limit` and `offset` query parameters and return an object with `count`, `next`, `previous`, and `results` fields (standard Django REST Framework pagination).

### `GET /hyperkitty/api/lists/`
List all mailing lists available in the archive.

- Query params: `limit`, `offset`
- Returns: paginated list of mailing list objects (`name`, `display_name`, `description`, `archive_url`, `created_at`, ...)

### `GET /hyperkitty/api/list/{list_address}/`
Detailed metadata for a single mailing list archive.

- `list_address` is the full posting address, e.g. `team@example.com`.
- Returns `404` if no archive exists for that address — useful as an existence check.
- Returns: `name`, `display_name`, `description`, `subject_prefix`, `archive_url`, `created_at`, `list_url`, `post_count`, ...

### `GET /hyperkitty/api/list/{list_address}/threads/`
Discussion threads for a list, sorted by **most recent activity** (`date_active`) first.

- Query params: `limit` (default 10–100, server-configurable), `offset`
- Each thread includes: `thread_id`, `subject`, `starting_email`, `date_active`, `replies_count`, `participants_count`, ...
- **Note:** This is per-list. To find globally newest activity across all lists, query each list and merge by `date_active` client-side.

### `GET /hyperkitty/api/list/{list_address}/thread/{thread_id}/emails/`
All emails in a single thread, in chronological order.

- Query params: `limit`, `offset`
- Each email includes: `message_id`, `message_id_hash`, `subject`, `sender_name`, `sender_email`, `date`, `content`, `
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=esug.org · GET /v1/domain/esug.org · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for esug.org:
1. POST https://agentwebmap.com/v1/sites/esug.org/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://esug.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/esug.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/esug.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.