# Developer and Agent Resources

Developer and agent access to Mormon Transhumanist Association public Markdown, discovery files, MCP search, authentication guidance, and administrative API boundaries.

The Mormon Transhumanist Association provides open document formats and an authenticated, read-only Model Context Protocol service for agents that research public website content. This page documents the supported entry points, their intended use, authentication boundaries, and current limitations.

## Public document access

Public pages require no credentials. Request a canonical page with Accept: text/markdown, append .md to its path, or add ?mode=agent for a structured homepage view. Start discovery with [llms.txt](/llms.txt), the [XML sitemap](/sitemap.xml), the [AI Catalog](/.well-known/ai-catalog.json), or the [Agent Skills index](/.well-known/agent-skills/index.json). Unknown paths return HTTP 404 with recovery links.

## MCP public-content service

The streamable HTTP MCP endpoint is https://www.transfigurism.org/mcp. Read its [Server Card](/.well-known/mcp/server-card.json) before connecting. Requests require Authorization: Bearer <key> with an API key issued by an Association administrator. The service is read-only and rate-limited to 60 requests per minute per key. There is no public sandbox or self-service key issuance at this time.

## MCP tools

Use describe_content_catalog to inspect supported public types and filters. Use search_content for full-text discovery, get_content_by_url for a known path, list_content for iteration, and get_related_content for relationship traversal. Additional tools list topics, quotations by topic, and works by author. Returned public URLs are authoritative; agents should not construct paths from titles.

## Quickstart

Fetch the site guide with curl https://www.transfigurism.org/llms.txt. Fetch a Markdown homepage with curl -H "Accept: text/markdown" https://www.transfigurism.org/ or curl https://www.transfigurism.org/index.md. For MCP, configure a streamable HTTP client from the Server Card and supply the issued Bearer key through secure secret storage.

## Administrative REST API

Authenticated /api/v1 routes support authorized Association administration and automation. They are not a public, compatibility-guaranteed integration product, and no public OpenAPI document or test environment is currently offered. Write access requires a scoped key and must not be inferred from the read-only MCP service.

## Access and support

To discuss an approved integration or request an API key for Association work, use the [contact page](/contact) and describe the intended task, data needed, and whether read or write access is required. Never place credentials in URLs, logs, issue reports, or public output.