corpus.blog valid
corpus.blog
A public record of which independent blogs cite which pages, built from the feeds of tens of thousands of blogs. It holds the citation graph -- who links to what, with the words they used -- not the text of the posts.
- Authority
- 45 reach 6 · trust 5 · quality 19 · freshness 15
- Tier
- listed
- llms.txt
- https://corpus.blog/llms.txt
- Sections
- 2
- Links
- 8
- Size
- 2122 bytes
- Popularity rank
- #719802
- Registered
- 2026-09-20
- Country
- France Hosting inference
- Hosting country
- France Hosting inference
- Country evidence
- No published address evidence collected yet
- For agents
- Interface: a documented API or declared MCP endpoint an agent can call
- First seen
- 2026-10-25T16:31:45.187Z
- Last checked
- 2026-10-25T18:34:56.314Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-25T18:34:53.753Z. Cached copy · Source on corpus.blog
# corpus.blog
> A public record of which independent blogs cite which pages, built from the feeds of tens of thousands of blogs. It holds the citation graph -- who links to what, with the words they used -- not the text of the posts.
Agents should read the corpus through the MCP server listed below rather than scraping these pages: one tool call returns clean, structured rows where a page is mostly navigation. The server needs a free corpus.blog account; MCP clients that support OAuth sign in through the browser on first connect, with a link sent by email.
The JSON API at /api/v1 (documented at /api) takes a key from the same account, created at /my/agent and sent as a bearer token.
No article text is available through any route. Link to each article's own URL, attribute figures to corpus.blog, and do not redistribute results in bulk.
## Pages
- [About](/about): what corpus.blog counts and how
- [How corpus.blog runs](/open): what beta means here, corpus and account totals, edge traffic, costs and where each part runs
- [Crawler policy](/crawler): who CorpusBot is and how to stop it
- [Blogs](/blogs): every source we hold, with who cites it
- [Talked about](/talked-about): the pages the corpus cites most this week
- [Neighbourhoods](/neighbourhoods): groups of blogs that cite alike and write alike, each named and approved by a person, with its member blogs and an OPML file of their feeds at `/neighbourhoods/{slug}/opml`; the index separates personal blogs from organisations
- [More like this](/more-like-this): the blogs and posts nearest to a post, a blog or an OPML list of subscriptions, as a page and as an OPML file (a blog's hub also has one at `/blogs/{subject}/opml`)
<!-- mcp-discovery:start -->
## MCP servers
This site offers its content over the Model Context Protocol (MCP). Agents should connect to these servers instead of scraping HTML.
- [corpus.blog](https://corpus.blog/mcp): Which independent blogs cite which pages: citations, rankings and anchor text. Streamable HTTP endpoint. Server card: https://corpus.blog/.well-known/mcp-server-card
<!-- mcp-discovery:end -->
Machine-readable: GET /v1/resolve?q=corpus.blog · GET /v1/domain/corpus.blog · 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 corpus.blog, 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 corpus.blog:
1. POST https://agentwebmap.com/v1/sites/corpus.blog/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://corpus.blog/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/corpus.blog/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/corpus.blog).
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.