Skip to main content
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. Use GET /api/v1/publications to list the curated catalog, or GET /api/v1/publications/search?q=... to find a source by name. Details: Publications.

​
Post

A post is a single article from a publication. It is addressed by its publication plus its own slug:
Search results include both publicationSlug and slug, so an agent can build the paid article URL directly from a search result. 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: Treat items as candidates. Fetch the selected post from the paid article endpoint to receive its robust summary. Parameters, filters, and a full example: Topic Search.

​
Company lookup

GET /api/v1/companies returns an identity card (name, ticker, domain, CIK) for “who is NVDA?” — not articles that mention the company. See Company Lookup. GET /api/v1/entities/search lists curated articles that mention a ticker, company, person, organization, or subject, sorted by publish date. Start with Search Articles by Ticker. The response includes matchedEntity.

​
Top-selling

GET /api/v1/posts/top-selling and GET /api/v1/publications/top-selling are free ranked lists for popular items. See Top-selling. A paid request returns article metadata and a robust synthesizedSummary. The first successful pay unlocks that post forever for the paying subject (Drip user for credits / MCP OAuth / API key / JWT; wallet or MPP credential for those rails). Later fetches return the live summary with no charge and no new sale. 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. x402/MPP clients should store unlockToken (or the X-Drip-Unlock response header) and resend it as the request header X-Drip-Unlock for free re-reads.