Technically speaking

The landing page is written for humans. This page adapts to your audience mode.

Framed for decisions, trade-offs, and business outcomes.

Audience mode

One lead, many specialists

technical name: "Orchestrator-Worker Architecture"

A planner agent breaks your request into tasks, then assigns each task to a specialist agent with a clear role.

It is like a pit crew, each person has one job so the whole team moves faster and cleaner.
Example: The planner creates a small mission list, delegates in parallel, then combines everything into one final answer.

technical name: "Parallel Sub-Agent Execution"

Sub-agents run concurrently, each focused on one objective. The system waits for all outcomes, then combines them.

Like cooking with three burners instead of one, dinner is ready faster with less back-and-forth.
Example: Three independent tasks launch together, then the final answer is assembled from all three outputs.

technical name: "API-First Design"

lmkgpt exposes an API endpoint so external systems can trigger the same multi-agent workflow.

It is like giving your software a hotline to the same research squad you use in the UI.
Example: A product can submit a prompt server-to-server and receive structured outputs plus the final summary.

technical name: "Real-Time Streaming via SSE"

Progress is streamed from server to page continuously, so updates appear as agents produce results.

The app keeps a live line open and sends small updates as they happen.
Example: Agent statuses and text stream in increments, not as a single delayed payload.

technical name: "Full Prompt Transparency"

The app keeps the planning steps, per-agent objectives, and raw outputs visible for review.

It is like seeing the rough draft, notes, and final essay, all in one place.
Example: You can verify that the final answer matches what the agents actually produced.

technical name: "Multi-Provider Resilience (Anthropic + OpenAI)"

The system prefers one provider first, then falls back when errors are retryable.

It keeps an alternate route ready so one traffic jam does not cancel the trip.
Example: Each agent can recover independently, so one timeout does not collapse the whole run.

Use the API to validate feasibility, effort, and execution quality before committing roadmap resources.

POST /api/v1/orchestrate