# Headline (`headline-1`): Title and description writing

A specific title, a one-line description and a URL slug.

Headline writes a title and a one-sentence description for any text: a blog draft, a support ticket, a commit, a document, a chat thread. You also get a URL slug made from the title.

Titles name the subject instead of teasing it, in the text's own language. Add a `style` like "sentence case, under 6 words" to match your app.

- **Price:** $0.20 per 1,000 texts. One unit per started 2,000 characters of input.
- **Languages:** ~30 languages
- **Input:** The text to title (string or array of up to 8, up to 6,000 characters each).
- **Batch:** yes, up to 8 inputs per call
- **Status:** live
- **Built on:** [Qwen/Qwen3-0.6B (with JSON-schema constrained decoding)](https://huggingface.co/Qwen/Qwen3-0.6B), Apache-2.0, 0.6B

## Request

```bash
curl https://labs.greatwork.company/v1/run \
  -H "Authorization: Bearer $GWL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"headline-1","input":"We moved our nightly database backups from a cron script on the app server to a managed job that snapshots every SQLite file, verifies it with an integrity check, copies it off the box, and runs a weekly restore drill so we know the backups actually work."}'
```

## Options

| Name | Type | Required | Default | Description |
|---|---|---|---|---|
| `input` | string or string[] | yes | | The text to title (string or array of up to 8, up to 6,000 characters each). |
| `style` | string | no |  | Optional style note, e.g. "sentence case, under 6 words" or "like a changelog entry". |

## Output

| Field | Type | Description |
|---|---|---|
| `title` | string | The title (90 characters max). |
| `description` | string | One sentence (220 characters max). |
| `slug` | string | URL slug from the title. |

The response envelope is always `{"id", "object": "run", "model", "created", "output", "usage": {"units", "unit", "cost_usd", "cost_micros"}, "latency_ms"}`. With an array input, `output` is an array in the same order.

## Examples (real outputs from our servers)

### Engineering note

```json
{
  "model": "headline-1",
  "input": "We moved our nightly database backups from a cron script on the app server to a managed job that snapshots every SQLite file, verifies it with an integrity check, copies it off the box, and runs a weekly restore drill so we know the backups actually work."
}
```

```json
{
  "title": "Database Backup Process Transformation",
  "description": "A detailed explanation of the transition from a cron script to a managed job for nightly database backups.",
  "slug": "database-backup-process-transformation"
}
```

4019 ms, $0.0002.

### Support thread

```json
{
  "model": "headline-1",
  "input": "Customer can't log in after changing their email. Password reset emails go to the old address. Confirmed the old address still shows on the account page.",
  "style": "sentence case, under 8 words"
}
```

```json
{
  "title": "Customer Can't Log In After Changing Email",
  "description": "Confirmed old address still shows on account page after password reset",
  "slug": "customer-can-t-log-in-after-changing-email"
}
```

3026 ms, $0.0002.

## Good for

- Name chat threads and conversations
- Title support tickets from the first message
- Suggest blog titles and meta descriptions
- Label uploaded documents

## Limits and caveats

- Plain titles by design: it won't write clickbait even if asked.
