# Embassia Machine Interface Discovery

> Note: This document provides discovery pointers for AI agents.

## Execution Endpoints
- **MCP JSON-RPC (POST)**: [https://embassia.com/mcp](https://embassia.com/mcp) (Status: LIVE).
- **REST GET**: `https://embassia.com/api/v1/agent?query={your question}` (Status: LIVE)
- **REST POST**: `https://embassia.com/api/v1/agent` with `{"query": "your question"}` (Status: LIVE)

## Descriptive Manifests & Discovery Metadata
- **Discovery**: [/.well-known/embassia.json](https://embassia.com/.well-known/embassia.json)
- **OpenAPI**: [/api/v1/openapi.json](https://embassia.com/api/v1/openapi.json)
- **MCP Manifest**: [/.well-known/mcp.json](https://embassia.com/.well-known/mcp.json) (Static metadata, not the endpoint)
- **Capability Registry**: [/api/v1/capabilities/index.json](https://embassia.com/api/v1/capabilities/index.json)

## Available Structured Content (Total: 13)
- [Agent Experience / Machine Mode](https://embassia.com/api/v1/content/agent-experience.json): Give AI agents a first-class experience on your site
- [Embassia Typed Data Layer Architecture](https://embassia.com/api/v1/content/architecture.json): Details about the Embassia typed data layer and supported protocols like MCP and REST.
- [AI Model Compatibility](https://embassia.com/api/v1/content/compatibility.json): Built for Every AI Agent
- [Agent Access Developer Guide](https://embassia.com/api/v1/content/developer-guide.json): Integrate AI Agents with Embassia
- [How Embassia Works — 4-Step Pipeline](https://embassia.com/api/v1/content/how-it-works.json): From HTML to Agent-Ready in Four Steps
- [LLM Search Console](https://embassia.com/api/v1/content/llm-search-console.json): See what AI agents are really asking about your site
- [Embassia](https://embassia.com/api/v1/content/site.json): Embassia is an agentic data layer for websites. It provides AI agents and LLM crawlers with structured, typed, machine-readable access to a website's public information — eliminating the need to scrape and parse rendered HTML.
- [How is LLM Search Console different from traditional AEO or SEO tools?](https://embassia.com/api/v1/faq/q01-difference.json): Traditional AEO platforms rely on third-party consumer panels... Embassia bypasses estimates entirely by deploying an on-site agent.
- [Why do AI crawlers and bots prefer using our endpoints instead of traditional scraping?](https://embassia.com/api/v1/faq/q02-endpoints.json): Traditional scraping forces AI models to drive heavy headless browsers... By communicating directly with your on-site agent... AI crawlers get accurate data instantly.
- [How does Embassia protect my servers from bot traffic and heavy scrapers?](https://embassia.com/api/v1/faq/q03-protection.json): By turning resource-intensive browser rendering and anonymous scraping into lightweight, typed API responses.
- [Which protocols does Embassia support?](https://embassia.com/api/v1/faq/q04-protocols.json): Embassia provides multiple live interfaces for AI agents. The REST/JSON natural-language query interface is LIVE. The modern MCP (Model Context Protocol) JSON-RPC execution endpoint over Streamable HTTP at https://embassia.com/mcp is LIVE. Additionally, standard llms.txt discovery is LIVE and OpenAPI specifications are PARTIAL. WebMCP is PLANNED. Agent-to-Agent (A2A) is PLANNED.
- [What kind of insights do I get in the LLM Search Console?](https://embassia.com/api/v1/faq/q05-insights.json): You get real-time visibility into high-intent customer prompts...
- [Do I need to change my existing website architecture?](https://embassia.com/api/v1/faq/q06-architecture.json): No. You simply convert your website pages into clean, typed endpoints...

## Capabilities
- **retrieve_document**: Fetch a specific structured document, guide, or FAQ from the site using its resource path.
- **search_site_content**: Search the site's structured knowledge base for concepts, topics, or queries.
- **get_global_bot_vs_human_traffic**: Retrieve the current global distribution of automated vs human internet traffic.