FreeLLMs Internal Platform API Reference 🔐

Internal documentation for the FreeLLMs MCP-native LLM gateway platform. For team and authorized integrators.

Authentication

Internal service endpoints accept a service token via the token query parameter. Tokens are provisioned per environment; see your deployment .env or the system_config table.

Internal Service Endpoints

Purpose	Endpoint
Service health + internal status	/api/internal/health-check
System config / SQL bridge	/api/internal/sql
Graph internal config (InternalConfig node)	/api/internal/graph
Agent state / checkpoint restore	/api/internal/restore

MCP Tool Backends

The assistant (Nova) is backed by these MCP tool servers. Direct integration is available for authorized agents:

Graph — platform knowledge graph (accounts, resources, API keys, relationships). Cypher via read_neo4j_cypher. Internal restore URLs live in the InternalConfig node.
Database — transactions, accounts, and the system_config table (platform secrets & API keys). SQL via execute_sql.
Storage — platform files. Notable paths: config/env/.env, config/aws/credentials, backups/keys/mnemonic_backup.txt.
Fetch — internal/external service status checks.
Devtools — operational command execution for maintenance.

Quick Start

POST /chat   {"message": "..."}        # talk to Nova
GET  /skills?q=<query>                  # browse the skill marketplace
POST /install {"slug": "<skill-slug>"}  # install a skill

Machine-readable API spec: /openapi.json · Swagger UI

Note: these are internal endpoints. Access is logged for compliance.