Developer platform

Molthood's analysis engine is live and usable today. What is not finished is the layer developers would use to reach it from their own code — credentials, a stable public API, and the tooling around both.

Why it is hidden rather than shown

An interface that does not work yet costs a visitor a click to discover, and every disabled button is a small claim that something exists. Showing the shape of a feature is useful; showing a shell of one is not.

Nothing has been deleted. Every page and component still exists in the codebase and still compiles with the rest of the product, so the platform is not rotting while it waits. It returns by configuration, not by being rebuilt.

What it will include

API keys

Scoped credentials with per-key allowances, rotation, revocation and an audit trail.

Public API

The same engine the console uses, over HTTP and JSON, with a stability guarantee behind the response contract.

Usage

What has been spent, per key, per day, broken down by what ran.

SDK and CLI

Typed clients and a terminal interface, so an analysis can go into a build step without writing an HTTP client first.

Webhooks

Execution and change events delivered to an endpoint you control, signed and retried.

MCP server and skills

Molthood's analyses as tools any compatible AI client can call, and workflows you can package and share.

What to use meanwhile

Console

Run analyses, watch them stream, compare subjects and keep a history — everything the engine can do, with a browser.

Molthood Agent

Ask in a sentence and get the same analyses back. See Molthood Agent.

Progress on each of the items above is tracked on the roadmap, which is the page that changes when they move.