kimetsu.dev valid
kimetsu.dev
Open infrastructure for coding agents: Kimetsu documentation, public projects, and credential-free discovery.
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T09:55:21.594Z. Cached copy · Source on kimetsu.dev
# kimetsu.dev
> Open infrastructure for coding agents: Kimetsu documentation, public projects, and credential-free discovery.
## Projects
- [Projects directory](https://kimetsu.dev/projects/): human-readable project index
- [Sidequest Commons](https://rodcor.github.io/sidequest-commons/): daily agent-and-human project selection
- [Sidequest agent entry](https://rodcor.github.io/sidequest-commons/agents/): participation instructions and machine endpoints
- [Agent gateway](https://agents.kimetsu.dev/): read-only JSON discovery gateway
- [Discovery manifest](https://kimetsu.dev/well-known/kimetsu-agents.json): domain-level machine discovery (the canonical /.well-known alias activates with the Cloudflare cutover)
## Security
The agent gateway never requires credentials. Do not send Authorization, Cookie, API keys, private repository content, or other secrets. All gateway operations are public and read-only.
## Kimetsu documentation
# Docs
- [Introduction](/docs): Coding agents are brilliant and forgetful.
- How Kimetsu Works
- [Overview](/docs/how-kimetsu-works): Kimetsu is a sidecar brain for coding agents. It runs alongside supported host agents through MCP (including Claude Code and Codex), or as a standalone chat REPL.
- [The brain](/docs/how-kimetsu-works/the-brain): brain.db: the event-sourced SQLite file that holds everything Kimetsu remembers, and how it migrates safely.
- [The broker](/docs/how-kimetsu-works/the-broker): How the broker scores, selects, and budgets the memories injected into each run.
- [The learning loop](/docs/how-kimetsu-works/learning-loop): Citations, decay, dedup, conflict detection, and the analytics that prove the brain is helping.
- [Interfaces](/docs/how-kimetsu-works/interfaces): The MCP tool surface, the host hooks that make the loop reliable, and proactive mid-work recall.
- [Retrieval models](/docs/how-kimetsu-works/retrieval-models): Which embedder and reranker Kimetsu ships, why, and how to swap or re-benchmark them.
- [Operations](/docs/how-kimetsu-works/operations): The bridge, brain sharing, doctor, and what Kimetsu is not.
- [Configuration](/docs/how-kimetsu-works/configuration): Every knob in project.toml, the off-switches, and the environment overrides.
- [Install & Host Wiring](/docs/install): Kimetsu is a single Rust binary.
- [Local Models](/docs/local-models): Kimetsu can run entirely on-device: no cloud embedder, no cloud reranker, no cloud distiller. This guide shows how to achieve that with Ollama as the cheap-model backend.
- [Kimetsu Remote](/docs/remote): Run the brain on a server and connect over HTTP MCP, so a team (or you across machines) shares one brain per repository, with no local checkout.
- Memory Benchmark
- [Overview](/docs/memory-benchmark): Kimetsu's house rule is that every claim ships with a measurement.
- [Retrieval & correctness](/docs/memory-benchmark/retrieval-and-correctness): Kimetsu's retrieval and correctness numbers: recall, MRR, latency, stal
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| dosu.dev | Dosu | interface AI agents and MCP Developer tools | US | 56 | ✓ | ✓ | |
| memorilabs.ai | Memori | interface AI and machine learning AI agents and MCP +1 | — | 49 | ✓ | ||
| kiro.dev | Kiro Docs | documentation Developer tools AI and machine learning +1 | — | 64 | ✓ | ||
| agentage.io | Agentage Memory | interface AI agents and MCP | DE | 54 | ✓ | ✓ | |
| getscribe.dev | scribe | documentation AI and machine learning AI agents and MCP +1 | — | 45 | ✓ | ✓ | |
| kurrent.io | kcap | documentation AI agents and MCP Developer tools | — | 54 | ✓ | ✓ | |
| memmachine.ai | MemMachine | interface AI and machine learning AI agents and MCP +1 | US | 48 | ✓ | ✓ | |
| mem0.ai | Mem0 | interface AI and machine learning AI agents and MCP | — | 63 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=kimetsu.dev · GET /v1/domain/kimetsu.dev · 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.
Own or manage this website?
If you own or manage kimetsu.dev, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for kimetsu.dev:
1. POST https://agentwebmap.com/v1/sites/kimetsu.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://kimetsu.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/kimetsu.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/kimetsu.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.