Skip to main content
Use API keys when your agent, backend job, or research pipeline wants a traditional bearer token instead of wallet-based x402 or MPP payments. An API key authorizes paid article reads with Authorization: Bearer pk_drip_... and spends your pre-purchased credits. Search and publication discovery routes are free. Each successful paid request returns a robust synthesized summary of a publisher’s article. The first successful pay for a post unlocks it forever for that Drip account — API key, in-app chat/JWT, and MCP OAuth tokens for the same user share the entitlement. Later unlocks of the same post do not spend credits. For production usage, follow Errors & Retries.
1

Create an API key and add credits

Sign in to Drip, then create a key from the API Keys dashboard. Copy the key when it is shown; raw keys are not displayed again.Add balance from the Credits dashboard.
2

Search across supported sources

Search across all supported financial newsletters and blogs for posts relevant to your research question.
Each result includes publicationSlug and slug. Use those two values to build the paid article URL. Search results are candidates, not paid article summaries.
3

Query a specific publication

If you already know which source you care about, find the publication slug and list its ready posts.
The publication response includes recent posts with slug, title, publishedAt, and priceCents. If priceCents is null, the charged 200 response provides the current price in paymentInfo.amountUsd.
4

Retrieve an article summary with your API key

Use the publicationSlug and slug from search or publication lookup to call the paid article route. A successful response returns 200 with article metadata and synthesizedSummary. The first successful pay for a post unlocks it forever for this Drip account; later requests for the same post do not spend credits.

Request examples

Example response

The response contains a robust synthesized summary and source metadata. The first successful pay unlocks that post forever for this Drip account; repeating the request for the same post does not spend credits again (paymentInfo.protocol is unlock, and unlocked is true).

Common responses

Keep API keys server-side. Do not ship pk_drip_... keys in browser code, public repositories, or agent traces.

Error response examples

An invalid or revoked API key returns:
If the summary has not finished processing, no credits are charged: