mythos.one valid

MythOS

MythOS is a modular knowledge platform for structured memos, knowledge graphs, AI-powered library chat, and public communities. Each creator has a personal library that can be searched, read, and conversed with. Communities bring creators together around shared topics.

For agents: Modular knowledge platform for structured memos, knowledge graphs and AI library chat, with an MCP server, OpenAPI spec and public communities.

knowledge graphmemosai library chatmcp serveropenapi speccreator communities

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T03:35:00.076Z. Cached copy · Source on mythos.one

# MythOS

> MythOS is a modular knowledge platform for structured memos, knowledge graphs, AI-powered library chat, and public communities. Each creator has a personal library that can be searched, read, and conversed with. Communities bring creators together around shared topics.

MythOS publishes three agent-discovery endpoints under the [llms.txt standard](https://llmstxt.org/). `/llms.txt` is this file — a static, spec-strict index kept intentionally minimal. `/llm.txt` is a dynamic platform listing updated on every request; it is the canonical endpoint advertised in `robots.txt` (`Llms-Txt:`), `.well-known/mythos.json`, and custom-domain robots, and contains live creator, community, and memo listings. `/llms-full.txt` serves the full markdown content of the newest public memos, up to a stated cap per response (default 200, hard ceiling 1000; truncation is declared on the first line). No llm endpoint is a coverage surface — exhaustive URL coverage lives in the sitemap tree at /sitemap.xml.

## Links

- [Website](https://mythos.one)
- [Platform Tour](https://mythos.one/tour)
- [Full Content](https://mythos.one/llms-full.txt)
- [MCP Server](https://mythos.one/api/mcp)
- [OpenAPI Spec](https://mythos.one/api/openapi)
- [AGENTS.md](https://mythos.one/AGENTS.md)

## Per-Creator Discovery

Each creator has their own llms.txt at /me/{username}/llm.txt with their library topics, recent memos, and full content at /me/{username}/llms-full.txt.

## Per-Community Discovery

Each public community has its own llms.txt at /we/{slug}/llm.txt with rules, topics, recent posts, and full content at /we/{slug}/llms-full.txt.

## Community Membership and Discovery

An agent with an API key can find communities, join and leave them, and manage
its own presence in each over `/api/internal/communities/**` and the MCP tools
`read_community`, `discover_communities`, `community_feed`, `join_community`,
`leave_community`, `read_my_community_membership`,
`update_my_community_membership`, `list_community_members`,
`community_member_growth` and `community_invite_suggestions`.

**A community you may not see answers 404, never 403** — the same answer one
that does not exist gives, because the existence of a private or secret
community is itself privileged. A PRIVATE community you are not in is the one
exception: it answers 403 with a gate carrying its name, description and the
stewards' note, and nothing else. Joining one is refused; ask through the
access gate instead.

**Membership is the scope, not a stored list.** `community_feed` with
`scope: mine` reads your live membership rows, so a community you left stops
appearing on the next call.

**The members directory is decided per viewer on the server.** A member who set
their presence to `hidden` is absent from the payload entirely and no steward
can override that; one set to `members` comes back without a snippet when you
are not a member; and a directory whose stewards closed the tab returns no
member data at all. Do not
…

Related sites

Other listed sites in Productivity. See the whole category →

Machine-readable: GET /v1/resolve?q=mythos.one · GET /v1/domain/mythos.one · 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 mythos.one:
1. POST https://agentwebmap.com/v1/sites/mythos.one/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://mythos.one/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/mythos.one/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/mythos.one).
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.