> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dripstack.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Core Concepts

> Key ideas in the Drip API: publications, posts, search, and paid article summaries.

Drip is organized around a few simple API concepts. Search across supported
financial newsletters and blogs, choose a relevant post, then unlock the paid
summary when your agent needs it for research.

## Publication

A **publication** is a supported financial source, usually a newsletter or blog.
It is identified by a **`publicationSlug`**, typically a normalized hostname.

| Source URL                            | `publicationSlug`             |
| ------------------------------------- | ----------------------------- |
| `https://michaeljburry.substack.com`  | `michaeljburry.substack.com`  |
| `https://unchainedcrypto.beehiiv.com` | `unchainedcrypto.beehiiv.com` |

Use `GET /api/v1/publications` to list the curated catalog, or
`GET /api/v1/publications/search?q=...` to find a source by name.

## Post

A **post** is a single article from a publication. It is addressed by its
publication plus its own **`slug`**:

```text theme={null}
GET /api/v1/publications/{publicationSlug}/{postSlug}
```

Search results include both `publicationSlug` and `slug`, so an agent can build
the paid article URL directly from a search result.

## Search

**Search** (`GET /api/v1/search`) is the free discovery layer. Use it to find
candidate posts by topic across supported financial newsletters and blogs.

The response includes:

| Field             | Meaning                                                                                    |
| ----------------- | ------------------------------------------------------------------------------------------ |
| `items`           | Ranked post candidates with fields such as `publicationSlug`, `slug`, `title`, and date    |
| `mode`            | Search strategy used: `hybrid` combines semantic and keyword search; `fts` is keyword-only |
| `matchConfidence` | Overall result quality: `strong`, `weak`, or `none`                                        |
| `count`           | Number of items returned after applying the requested `limit`                              |

Treat `items` as candidates. Fetch the selected post from the paid article
endpoint to receive its robust summary.

## Paid Article Summaries

A paid request returns article metadata and a robust `synthesizedSummary`. It
does not grant permanent access. Every request to the paid route is charged.

Wallet requests use x402 on Base or Solana, or MPP on Tempo. An unpaid wallet
request returns a `402` challenge containing the authoritative runtime price.
API-key requests spend pre-purchased credits instead.