API and Agent Discovery

This site exposes a small read-only discovery surface for agents and automation.

Discovery endpoints

  • /.well-known/api-catalog publishes an RFC 9727 API catalog.
  • /openapi.json describes the public read-only endpoints and the MCP transport.
  • /.well-known/agent-skills/index.json lists site-specific skill documents with SHA-256 digests.
  • /.well-known/mcp/server-card.json advertises the remote MCP server card.
  • /.well-known/agent-card.json publishes the A2A discovery card.
  • /api/status.json returns a lightweight health document.

Content negotiation

HTML remains the default response for browsers.

Clients that send Accept: text/markdown to page routes receive a markdown representation of the rendered page with:

  • Content-Type: text/markdown
  • Vary: Accept
  • x-markdown-tokens

Example:

curl https://lawzava.com/ \
  -H "Accept: text/markdown"

MCP endpoint

The site exposes a small read-only MCP endpoint at /mcp.

Available tools:

  • list_site_sections
  • get_recent_posts
  • search_posts
  • get_contact_channels

OAuth metadata

The MCP endpoint advertises OAuth metadata for client credentials flows:

  • /.well-known/oauth-authorization-server
  • /.well-known/oauth-protected-resource
  • /.well-known/jwks.json
  • /oauth/token

The scope currently used by the MCP endpoint is mcp.read.

A2A discovery

The site publishes an A2A Agent Card at /.well-known/agent-card.json and a discovery-oriented interface descriptor at /a2a/v1.

The A2A surface is discovery-focused. Live read-only tool execution is available through:

  • WebMCP in the browser
  • MCP at /mcp

Document responses include RFC 8288 Link headers for:

  • api-catalog
  • service-desc
  • service-doc
  • describedby