{
  "id": "developer-agent-access",
  "title": "Agent Access Developer Guide",
  "content_type": "page",
  "canonical_url": "https://embassia.com/developers/agent-access/",
  "updated_at": "2026-09-28T13:00:00Z",
  "language": "en",
  "content": {
    "headline": "Integrate AI Agents with Embassia",
    "sections": [
      {
        "title": "Quick Start",
        "body": "To integrate an AI agent with Embassia's machine-readable interfaces, start by fetching the discovery document at GET https://embassia.com/.well-known/embassia.json. This document lists all available interfaces, content endpoints, and protocol details.",
        "code_example": "curl -s https://embassia.com/.well-known/embassia.json | jq ."
      },
      {
        "title": "Content Retrieval",
        "body": "All content is available via GET requests to static JSON endpoints. No authentication required. Start with the content index to discover all available documents.",
        "code_example": "curl -s https://embassia.com/api/v1/content/index.json | jq '.documents[] | {id, title, api_url}'"
      },
      {
        "title": "Search",
        "body": "Use the search index for keyword matching. The index contains pre-tokenized document titles, descriptions, and content excerpts. Implement client-side filtering by matching query terms against the keywords array.",
        "code_example": "curl -s https://embassia.com/api/v1/content/search-index.json | jq '.entries[] | select(.keywords[] | contains(\"agent\"))'"
      },
      {
        "title": "Full Text Access",
        "body": "For bulk context loading, use llms-full.txt which contains the complete site content as plaintext. This is optimized for AI context windows — low token count, no HTML boilerplate.",
        "code_example": "curl -s https://embassia.com/llms-full.txt"
      },
      {
        "title": "MCP Discovery",
        "body": "The MCP manifest at /api/v1/mcp.json lists available tools and resources following Anthropic's Model Context Protocol specification. Note: this is a static manifest for discovery. Full JSON-RPC MCP server support is planned for a future release using Cloudflare Workers.",
        "code_example": "curl -s https://embassia.com/api/v1/mcp.json | jq .tools"
      },
      {
        "title": "OpenAPI Specification",
        "body": "A complete OpenAPI 3.1 specification is available describing all endpoints, schemas, and response formats.",
        "code_example": "curl -s https://embassia.com/api/v1/openapi.json | jq .info"
      },
      {
        "title": "Content Freshness",
        "body": "Each content document includes an updated_at timestamp and content_hash. Use these fields to validate freshness. Cloudflare CDN serves responses with appropriate Cache-Control headers."
      },
      {
        "title": "CORS Policy",
        "body": "All endpoints are served with Access-Control-Allow-Origin: * — agents can fetch from any origin without CORS issues."
      }
    ],
    "contact": "For integration questions, email founders@embassia.com",
    "api_base": "https://embassia.com/api/v1/"
  },
  "metadata": {
    "content_version": "1.0.0",
    "content_hash": "developer-guide-v1-20260928"
  }
}