OpenAPI 3.1 spec
The canonical, self-describing contract for every public /api/v1/* endpoint. Point your integration or AI agent at it on cold start — no need to hardcode field lists.
Open the specA self-describing public API, a remote MCP server for AI agents, signed webhooks, and scoped keys. Everything an integrator or answer engine needs to work with LegacyCore.
The canonical, self-describing contract for every public /api/v1/* endpoint. Point your integration or AI agent at it on cold start — no need to hardcode field lists.
Open the specA Streamable-HTTP Model Context Protocol server exposing scoped tools over Bearer auth — so external AI agents can read applications, write conservation events, and more, gated per-tool.
MCP + auth docsHMAC-signed event delivery for application and policy lifecycle events, with a durable retry queue. Verify signatures, park the payload, and drain on your side.
Webhook patternsIssue lc_ prefixed keys scoped to read:applications, write:applications, or write:conversations. Every call is per-tool audited.
API-key authMachine-readable feeds for answer engines: an AI plugin manifest, a full AI-optimization manifest, and JSON feature + FAQ catalogs — all listed in llms.txt.
AI manifest