∞Online LegacyDevelopers

Developer Portal

Build with Online Legacy

Integrate conversational AI legacy profiles into your applications. Our public API is accessible without authentication — no API key required for public endpoints.

OpenAPI 3.1 specAPI llms.txtMCP server card

Quickstart

Ask a question about Online Legacy in one HTTP request — no API key, no setup:

curl -X POST https://online-legacy.com/ask \ -H "Content-Type: application/json" \ -d '{"query":{"text":"How does Online Legacy work?"}}'

Response (NLWeb v0.55 format):

{ "_meta": { "response_type": "answer", "version": "0.55" }, "results": [ { "@type": "Answer", "text": "Online Legacy creates conversational AI twins...", "url": "https://online-legacy.com" } ] }

API reference

POST/askNo auth required

Natural language query — NLWeb v0.55. Add "prefer":{"streaming":true} to receive a Server-Sent Events stream.

GET/ask?q=your+question

GET convenience wrapper for the NLWeb endpoint.

POST/api/legacy/{slug}/chat

Chat with a published legacy profile. Returns a streamed SSE response in the voice and knowledge of the person. Replace {slug} with the profile's public URL slug.

View complete OpenAPI 3.1 spec →

Agent discovery

AI agents and crawlers can discover Online Legacy capabilities through these standard discovery endpoints:

llms.txt
LLM-readable site index
API llms.txt
API capabilities for agents
OpenAPI spec
OpenAPI 3.1 machine-readable spec
Agent card (A2A)
A2A protocol agent card
Agent skills
Callable skill definitions
ARD catalog
Agentic Resource Discovery
AI catalog
AI agent catalog entries
MCP server card
MCP server manifest
Plugin manifest
Agent Plugins specification
Agent mode view
Machine-readable homepage

Authentication

No authentication required

All public endpoints — /ask, /api/legacy/*/chat, and all discovery files — are open with no API key or session token required.

Admin and content management endpoints require a session token issued by Online Legacy staff. See auth.md for the full authentication specification.