---
title: "Get an article"
method: GET
path: "/api/mcp/articles/{articleId}"
tags: ["Articles"]
---

# Get an article

`GET /api/mcp/articles/{articleId}`

Full article content + SEO metadata. Checks content_pieces (v2) first, falls back to legacy articles.

## Path parameters

- `articleId` string, uuid, required

## Response `200`

Article detail.

- ArticleDetailResponse
  - `project` ProjectRef
    - `id` string, uuid, required
    - `name` string, required
    - `domain` string, nullable, required
  - `article` Article, required — Content-piece detail. `content-v2` and `legacy` sources share this shape; some fields (e.g. `targetKeyword`, `tldr`, `summary`, `outline` on the content-v2 branch) are always null for that source today.
    - `id` string, uuid
    - `title` string
    - `slug` string, nullable
    - `urlPath` string, nullable
    - `status` string
    - `type` string, nullable
    - `visibility` string
    - `topic` string, nullable
    - `targetKeyword` string, nullable
    - `keywords` string[]
    - `contentHtml` string, nullable
    - `contentMarkdown` string, nullable
    - `metaTitle` string, nullable
    - `metaDescription` string, nullable
    - `ogImage` string, nullable
    - `altText` string, nullable
    - `schemaMarkup` object — Structured-data (JSON-LD) markup, when generated.
    - `tldr` string, nullable
    - `summary` string, nullable
    - `outline` object — Content outline, when generated.
    - `faq` object — Generated FAQ entries, when present.
    - `faqsMarkdown` string, nullable
    - `cta` object — Generated call-to-action, when present.
    - `internalLinks` object[]
    - `externalLinks` object[]
    - `isPillar` boolean
    - `brief` object — Present on content-v2 articles only.
      - `angle` unknown
      - `audience` unknown
      - `intent` unknown
      - `notes` unknown
    - `aiReadinessScore` number, nullable
    - `tags` string[]
    - `wordCount` integer
    - `readTime` integer
    - `source` 'content-v2' | 'legacy'
    - `createdAt` string, date-time, nullable
    - `updatedAt` string, date-time, nullable
    - `publishedAt` string, date-time, nullable

## Other responses

- `401` — Error response. `code` is the machine-readable reason — see the [error reference](/api/errors) for the full catalog and remediation per code.
- `403` — Error response. `code` is the machine-readable reason — see the [error reference](/api/errors) for the full catalog and remediation per code.
- `429` — Rate limited. Usually the per-API-key REST limit (600 requests/minute); on Google-backed endpoints it can also relay an upstream Google rate limit. `Retry-After` (seconds) is present when the limit was applied by Searchable's own rate limiter; it may be absent when an upstream provider rate-limits.
- `500` — Error response. `code` is the machine-readable reason — see the [error reference](/api/errors) for the full catalog and remediation per code.
- `504` — Error response. `code` is the machine-readable reason — see the [error reference](/api/errors) for the full catalog and remediation per code.

---

[API](https://skmtc.net/searchable/apis/searchable-rest-api.md) · [All operations](https://skmtc.net/searchable/apis/searchable-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/searchable/searchable-rest-api/revisions/301b04e800ed/schema)