opensource.legal valid

cite

cite is the citation layer for agentic workflows: an open citation graph that humans and AI agents can read, reason over, and contribute back to. Documents are nodes, citations are edges, annotations are how humans and agents build the graph together. This instance exposes a Model Context Protocol (MCP) endpoint so agents can traverse the graph and cite the spans they pulled from. Released as OpenContracts since 2019; rebranded as cite for the v3 release line.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T10:35:48.581Z. Cached copy · Source on opensource.legal

# cite

> cite is the citation layer for agentic workflows: an open citation graph that humans and AI agents can read, reason over, and contribute back to. Documents are nodes, citations are edges, annotations are how humans and agents build the graph together. This instance exposes a Model Context Protocol (MCP) endpoint so agents can traverse the graph and cite the spans they pulled from. Released as OpenContracts since 2019; rebranded as cite for the v3 release line.

## MCP Server

This instance exposes a read-only MCP server that AI agents can connect to for accessing public corpuses, documents, annotations, and discussion threads.

- Endpoint (global): https://contracts.opensource.legal/mcp/
- Endpoint (corpus-scoped): https://contracts.opensource.legal/mcp/corpus/{corpus_slug}/
- Protocol: JSON-RPC 2.0 (MCP spec 2025-03-26)
- Auth: None required (public data only)
- Rate limit: 100 requests/minute per IP

### Connecting

Use any MCP-compatible client. For Claude Desktop, add to config:

```json
{
  "mcpServers": {
    "cite": {
      "command": "npx",
      "args": ["mcp-remote", "https://contracts.opensource.legal/mcp/"]
    }
  }
}
```

### Available Tools

- `list_public_corpuses`: List all public corpuses (paginated, searchable)
- `list_documents`: List documents in a corpus
- `get_document_text`: Get full extracted text from a document
- `list_annotations`: List annotations on a document (filter by page or label)
- `search_corpus`: Semantic vector search within a corpus
- `list_threads`: List discussion threads in a corpus
- `get_thread_messages`: Get messages in a thread (flat or hierarchical)

### Available Resources (URI-based)

- `corpus://{corpus_slug}` - Corpus metadata
- `document://{corpus_slug}/{document_slug}` - Document with text
- `annotation://{corpus_slug}/{document_slug}/{annotation_id}` - Annotation details
- `thread://{corpus_slug}/threads/{thread_id}` - Discussion thread

## REST Search API

A simple JSON search endpoint at `https://contracts.opensource.legal/api/search/?q=QUERY` is available for crawlers and lightweight integrations.

## Available Collections

- **Texas Interconnection and ERCOT Resource Integration** (slug: `texas-interconnection`, 87 documents): One-time snapshot bulk-20260908. Texas Interconnection and ERCOT Resource Integration. Source documents retain their ...
- **Supreme Court Docket 24-860** (slug: `scotus-24-860`, 24 documents): One-time snapshot bulk-20260908. Supreme Court Docket 24-860. Source documents retain their dates and versions; this ...
- **Supreme Court Docket 24-1056** (slug: `scotus-24-1056`, 34 documents): One-time snapshot bulk-20260908. Supreme Court Docket 24-1056. Source documents retain their dates and versions; this...
- **Supreme Court Docket 24-1046** (slug: `scotus-24-1046`, 133 documents): One-time snapshot bulk-20260908. Supreme Court Docket 24-1046. Source documents retain their dates and versions; this...
- **Supreme Court Docket 23-1209** (slug: `scotus-23-1209`
…

Related sites

Find similar publishers by meaning →

Other listed sites in AI and machine learning. See the whole category →

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