Build Content Feed API Kit with Cursor and Synorb

Content Feed API Kit

Build a reusable backend package that exposes normalized Synorb Manifests, Briefs, Signals, claims, filters, and pagination to an existing app. Server-only Synorb client; Normalized Manifest, Brief, Signal, claim, and citation adapters; Private product API routes; Pagination, filters, caching, and tests

How do you build Content Feed API Kit with Cursor and Synorb?

Use the Content Feed API Kit one-shot prompt to have Cursor build a working product with Synorb discovery, server-side REST, source-linked claims, and Cursor-native automation.

A real app, not a flattened feed.

How the live data flows

Cursor builds the product layer. Synorb supplies the cited core.

Cited data core

Streams user-approved Streams discovered for the existing app; source channels, home domains, tickers, identifiers, or media formats matching the product scope; Brief, Signal, Manifest, claim, citation, coverage, usage, and diagnostics surfaces

Facets Manifests, Briefs, Signals, claims, citations, source URLs, coverage, diagnostics, usage, and pagination.

Experience layer

Cursor

Build prompt

CREDENTIALS FIRST: Before any Synorb setup, ask the user in plain English for one Synorb Key (SYNORB_KEY). Parse only credentials.synorb_key from GET https://synorb.com/connect; store the one key as a server-side secret and use Authorization: Bearer for both REST and MCP. A self-provisioned key is 24 Hour Agent Demo access for 1,000 Manifests and expires 24 hours after mint; read and surface the top-level expires_at field. Bind an email with POST https://api.synorb.com/api/connect/bind-email using the same Bearer key to get Starter, free forever with 1,000 Manifests/month and no expiry; Paid is $10/month for 10,000 Manifests/month. After expiry, bind an email, mint a new demo at https://synorb.com/connect, or sign up free at https://synorb.com/signup. Store one server-side key, show "Synorb key expired - bind an email or mint a new demo key" instead of a generic auth failure, and document expires_at plus these recovery paths in the generated README and environment template.

PRODUCT TO BUILD

Build a Content Feed API Kit inside this repository. The goal is not a new dashboard first; it is a reusable backend and typed adapter layer that exposes normalized Synorb Manifests, Briefs, Signals, claims, citations, filters, diagnostics, usage, and pagination to the existing app.

TAGS

API, backend, adapters, manifests, signals, briefs, pagination, integration

PRIMARY USER

Developer adding Synorb to an existing application or internal platform.

APP-SPECIFIC ACCEPTANCE TESTS

FINAL OUTPUT

Build the product as a working vertical slice with real Synorb data or a setup-blocked state. Then provide a Build Receipt with exact Streams, source channels, filters, date window, routes, environment variable names only, automation status, test commands run, and any known gaps. Do not deploy unless the user separately asks after review.