Research API & MCP

The archive provides a public, read-only REST API and remote Model Context Protocol server. No API key is required. Clients can search transcript evidence, inspect surrounding context, analyze exact mentions, and retrieve canonical recording metadata.

Endpoints

REST API index · OpenAPI document · https://archive.ecash.com/mcp

MCP Tools

search_passages ranks timestamped transcript evidence. search_records searches titles and metadata. get_record retrieves one archive entry. get_transcript_contextexpands a timestamp before citation. analyze_mentions counts exact terms over time. get_archive_statisticsreports corpus coverage and methodology.

Connect an Agent

Add the archive to Codex with one command:

codex mcp add drivechain-archive --url https://archive.ecash.com/mcp

Or add it to Claude Code:

claude mcp add --transport http --scope user drivechain-archive https://archive.ecash.com/mcp

Other MCP clients can use the same remote HTTP endpoint with this generic configuration:

{
  "mcpServers": {
    "drivechain-archive": {
      "type": "http",
      "url": "https://archive.ecash.com/mcp"
    }
  }
}

Search the REST API

Repeat q for alternative formulations of one research question. Results are fused into a single ranked list with recording dates, timecodes, citations, and playable URLs.

curl --get 'https://archive.ecash.com/api/v1/search' \
  --data-urlencode 'q=miner theft slow withdrawal' \
  --data-urlencode 'q=Drivechain withdrawal security' \
  --data-urlencode 'limit=10'

Evidence and Attribution

Transcripts are automated and may contain errors. Multi-participant recordings are not speaker-diarized, so the presence of text in a recording does not identify its speaker. Review the linked media before attributing a quotation. Summaries, chapters, and key takeaways are generated research aids rather than primary-source evidence.

Usage

The service is rate-limited and intended for research queries, integrations, and citation workflows. It is not a bulk media-download interface.