All endpoints operational

Agent Access Guide

Everything you need to integrate an AI agent with Embassia's machine-readable interfaces. No authentication, no SDKs — just HTTP GET requests.

Quick Start

Start by fetching the discovery document. It's the single entry point that lists all available interfaces:

Terminal

curl -s https://embassia.com/.well-known/embassia.json | jq .

The response includes URLs for every machine interface: content index, search index, OpenAPI spec, MCP manifest, and more.

Discovery Endpoints

These are the entry points that AI agents should check first:

GET /.well-known/embassia.json Master discovery

GET /llms.txt Agent guide

GET /llms-full.txt Full content

GET /api/v1/openapi.json OpenAPI 3.1

GET /api/v1/mcp.json MCP manifest

GET /.well-known/mcp.json MCP well-known

Content Retrieval

All content documents are available via GET requests. Start with the content index to see everything available:

List all content

curl -s https://embassia.com/api/v1/content/index.json | jq '.documents[] | {id, title, api_url}'

Content Documents

GET /api/v1/content/site.json Site overview

GET /api/v1/content/how-it-works.json Pipeline

GET /api/v1/content/agent-experience.json Machine mode

GET /api/v1/content/llm-search-console.json Console

GET /api/v1/content/compatibility.json AI models

GET /api/v1/content/developer-guide.json Dev guide

Search

The search index contains pre-tokenized keywords for each document. Download the index and match query terms client-side:

Search for "agent" across all content

curl -s https://embassia.com/api/v1/content/search-index.json \
  | jq '.entries[] | select(.keywords[] | contains("agent"))'

MCP (Model Context Protocol)

The MCP manifest lists available tools and resources following Anthropic's protocol specification:

List MCP tools

curl -s https://embassia.com/api/v1/mcp.json | jq '.tools[] | {name, description}'

Note: The MCP manifest is a static JSON document for discovery purposes. Tool definitions describe available HTTP GET endpoints that agents can call directly. A full JSON-RPC MCP server (supporting interactive tools/call, resources/read) is planned for a future release using Cloudflare Workers.

Access Details

Property	Value
Authentication	`None required`
HTTP Method	`GET`
Response Format	`application/json` or `text/plain`
CORS	`Access-Control-Allow-Origin: *`
Rate Limit	Cloudflare CDN defaults
Cache	Edge-cached, use `updated_at` and `content_hash` for freshness
TLS	Required (HTTPS only)

Content Document Schema

Every content document follows this structure:

        Content Document Schema
      
{
  "id":             // Stable document identifier
  "title":          // Human-readable title
  "content_type":   // "page" | "faq" | "feature" | "product"
  "canonical_url":  // URL of the human-facing page
  "updated_at":     // ISO 8601 timestamp
  "language":       // ISO 639-1 language code
  "content":        // Structured content body (varies by type)
  "metadata": {
    "content_version": // Semver version string
    "content_hash":   // Unique hash for change detection
  }
}

Contact

Questions about agent integration? Email founders@embassia.com