Stories a user has applauded for (their curation)

Extraits de code

curl "https://api.oanor.com/medium-api/v1/recommended" \
  -H "x-oanor-key: oanor_test_..."

await fetch("https://api.oanor.com/medium-api/v1/recommended", {
  headers: { "x-oanor-key": "oanor_test_..." }
});

$ch = curl_init("https://api.oanor.com/medium-api/v1/recommended");
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$out = curl_exec($ch);

import requests
requests.get(
    "https://api.oanor.com/medium-api/v1/recommended",
    headers={"x-oanor-key": "oanor_test_..."}
)

Exemple de réponse

Une réponse réelle de ce endpoint, capturée lors du dernier contrôle de santé.

{
    "data": {
        "feed": {
            "link": "https://medium.com/@quincylarson?source=rss-17756313f41a------3",
            "image": "https://cdn-images-1.medium.com/fit/c/150/150/1*R0u5NcfQM5JfNjFNUMdVcw.jpeg",
            "title": "Stories applauded for by Quincy Larson on Medium",
            "description": "Latest stories applauded for by Quincy Larson on Medium"
        },
        "count": 9,
        "items": [
            {
                "guid": "https://medium.com/p/0fb7bf339400",
                "link": "https://medium.com/@takafumi.endo/prompt-requirements-document-prd-a-new-concept-for-the-vibe-coding-era-0fb7bf339400?source=rss-17756313f41a------3",
                "title": "Prompt Requirements Document (PRD): A New Concept for the Vibe Coding Era",
                "author": "Takafumi Endo",
                "excerpt": "In conventional product development, the established approach has been to create a Product Requirements Document (PRD) to clearly outline product requirements for the development team. As agile development has gained popularity, the significance of PRDs has only grown. Historically, the PRD served a",
                "updated": "2025-04-08T04:43:17.793Z",
                "published": "Mon, 07 Apr 2025 15:45:51 GMT",
                "categories": [
                    "startup",
                    "vibe-coding",
                    "model-context-protocol",
                    "cursor",
                    "ai"
                ],
                "content_html": "<p>In conventional product development, the established approach has been to create a Product Requirements Document (PRD) to clearly outline product requirements for the development team. As agile development has gained popularity, the significance of PRDs has only grown. Historically, the PRD served as a blueprint to align stakeholders, developers, and designers under a unified vision. This alignment helped teams address issues like shifting specifications and misaligned expectations.</p><p>However, in what I call the Vibe Coding era — where AI and humans work side by side — I believe a new concept is necessary: the <strong>Prompt Requirements Document (PRD)</strong>. Whereas traditional PRDs deal mostly with unstructured information for human-to-human alignment, this new PRD focuses on generating, editing, and managing structured prompts (including text, images, videos, and more) that both AI and humans can understand and use effectively.</p><p>This shift reflects our transition from an era where documentation preceded development to one where we first implement prototypes and then use them to define specifications or as input for AI to guide subsequent feature development.</p><h3>Current AI-Assisted Development Environment</h3><p>If you’ve used AI development tools like Cursor or Cline, you might be familiar with the .rules directory and mdc files used to prevent AI from generating unintended code. You can think of that as an early-stage precursor t
…