Skip to main content
LTHN Documentation
Product API MCP

Getting started

Getting started

Map the public domains, pick the right integration lane, and reach the live API and MCP surfaces quickly.

Getting started

The LTHN platform is split across purpose-built domains:

  • https://lthn.ai for the public product site, models, pricing, and developer overview.
  • https://api.lthn.ai for REST endpoints, explorers, and human-readable API guides.
  • https://mcp.lthn.ai for the MCP registry, server catalogue, and connection flow.
  • https://docs.lthn.ai for framework, package, and RFC reference material.

Pick the right integration lane

Building inside Laravel

Start with the Core PHP docs and the package contracts:

  • /php for framework conventions and module patterns.
  • /agent for the server-side agent runtime contract.
  • /api and /mcp for the two main protocol packages.

Automating builds and releases

Use Core Go:

  • /go for framework and CLI guidance.
  • /cli for generated command reference.

Calling the platform directly

  • Use the API domain when you want explicit HTTP endpoints and generated OpenAPI docs.
  • Use the MCP domain when your client already speaks the Model Context Protocol.

Public surfaces

API

  • POST /v1/score/content
  • POST /v1/brain/remember
  • GET /v1/plans
  • GET /docs/openapi.json

MCP

  • GET /.well-known/mcp-servers.json
  • GET /servers
  • GET /connect
  • POST /mcp/tools/call

Design standard

The platform RFC is the reference point for the overall experience and package alignment. Read it alongside the OpenBrain RFC and the agent package docs when you are implementing a new feature.