# Developers · Terradium

Terradium's machine surface lives on **https://api.terradium.io**. This marketing site (https://terradium.io) publishes docs, the OpenAPI document, and agent files. It is not the API host and it is not the MCP server.

Live product version: **v1.0.8**. Confirm with `GET https://api.terradium.io/healthz` (no auth).

## REST (content API)

Read-only published posts, API-key gated:

```
GET https://api.terradium.io/api/v1/public/content/{projectId}/posts
GET https://api.terradium.io/api/v1/public/content/{projectId}/posts/{slug}
GET https://api.terradium.io/api/v1/public/content/{projectId}/categories
```

Send `X-API-Key: td_live_...` (or `Authorization: Bearer`). Create keys in the dashboard under Project settings, API access. Single-post markdown is also available with `Accept: text/markdown` (keyless for that clean format).

Discoverability files on the same project path (`/llms.txt`, `/sitemap.xml`, `/robots.txt`, `/llms-full.txt`) are keyless.

Full reference: [/docs/api-reference](/docs/api-reference). Machine-readable spec: [/openapi.json](/openapi.json).

## MCP

```
https://api.terradium.io/api/v1/mcp
```

Authenticate with a project-scoped token. Prefix: `td_mcp_`.

```
Authorization: Bearer td_mcp_...
```

`X-API-Key` is accepted too. Writes (generate, publish, sample, change settings) need this project token and an active subscription. A content `td_live_` key cannot write.

Create a token in the dashboard: Project settings, Agent (MCP). The raw token is shown once.

Guide: [/docs/mcp](/docs/mcp).

## How an agent should proceed

1. Read [/llms.txt](/llms.txt).
2. Read [/openapi.json](/openapi.json).
3. Call MCP at the API host above. Do not POST MCP to terradium.io.

## CLI

The published CLI is the embed installer, not a second product API:

```
npx terradium init
```

That writes a `terradium.config.json` and the snippet for `@terradium/embed` (AI-referral attribution on a customer site). There is no Homebrew or PyPI package.

## Pricing lock

$29 is writer plus 15 tracked questions weekly, 3 answer engines, 1 run per question (about 45 samples a cycle, 250 a billing period). 30 article generations per billing period. 7 days free. The API enforces these limits: a setting outside the plan is rejected with a machine-readable code, not silently clamped. Daily sampling and 50 questions are a higher plan that is not publicly listed — email company@kugie.app.
