Build / Cursor / Content feed API

How to Add a Content Feed API with Cursor and Synorb

Use Cursor when the job is not a clean-sheet app but an existing-codebase change: add the route, type the response, wire the UI, and keep the integration clear. Synorb gives the app a current source-grounded feed contract.

Get Keys Copy prompt ↓
Build intent

What is this content feed api supposed to do?

A content feed API turns external context into a stable app-owned endpoint: the frontend, agent, dashboard, or workflow asks your backend for normalized rows, and the backend calls Synorb with server-side credentials.

Backend route

Create /api/content-feed or an equivalent server endpoint that calls Synorb REST.

Typed contract

Return id, headline, summary, publishedDate, sourceUrl, sourceName, tags, pagination, and usage.

Existing UI integration

Wire source-linked cards into an existing dashboard, product page, newsroom, or agent surface.

Cursor fit

Why does Cursor fit this build?

Cursor fits this build because it can inspect existing routes, components, tests, environment conventions, and cache patterns before editing. The public claim should be concrete: add a source-grounded feed to your existing application without exposing API secrets.

Builder surface
Cursor builds the app layer
GoalContent feed API
OutputUI, routes, filters, states, and review workflow
Context layer
Synorb supplies source-grounded feeds
BuildMCP exploration where available
ShipREST from a backend route with server-side secrets
Starting scopes

Which Synorb feeds should this app start with?

Start narrow, prove the feed contract, then broaden coverage. These scopes give the coding agent concrete source-grounded examples to design against.

existing app feeds

Use Synorb Streams and source-linked feed records to test this scope with source URLs, dates, tags, and coverage caveats preserved.

agent context endpoints

Use Synorb Streams and source-linked feed records to test this scope with source URLs, dates, tags, and coverage caveats preserved.

research dashboards

Use Synorb Streams and source-linked feed records to test this scope with source URLs, dates, tags, and coverage caveats preserved.

newsroom surfaces

Use Synorb Streams and source-linked feed records to test this scope with source URLs, dates, tags, and coverage caveats preserved.

customer-facing monitors

Use Synorb Streams and source-linked feed records to test this scope with source URLs, dates, tags, and coverage caveats preserved.

Architecture

Use the same safe data path.

1

Explore with an agent

If Cursor or your companion coding agent supports MCP, inspect Synorb Streams and source-linked examples before generating the app. Otherwise use the REST docs and the sample row shape in the prompt.

2

Call Synorb from the backend

The shipped app should call Synorb REST from a server route, scheduled job, webhook receiver, or server function. Keep SYNORB_API_KEY and SYNORB_SECRET out of browser code.

3

Show citations and coverage

Every card should preserve source URL, source name, published date, tags, and an honest empty or limited-results state when the selected scope has few results.

One-shot prompt

Paste this into Cursor.

This prompt is tuned to the build intent and keeps Synorb credentials server-side.

Content feed API prompt

Asks for the app surface, backend feed route, source-linked rows, safe credential handling, and transparent coverage states.

Use Cursor to add a Synorb content feed API to this existing codebase. First inspect the framework, route conventions, environment variable handling, fetch utilities, tests, and existing card components. Then add a server-only endpoint named /api/synorb-feed or the nearest local convention. The endpoint must read SYNORB_API_KEY and SYNORB_SECRET from server-side environment variables and call POST https://api.synorb.com/streams/query. Accept query, tag_names, stream_ids, days, page_size, and cursor parameters. Return normalized rows with id, headline, summary, publishedDate, sourceUrl, sourceName, streamNames, tags, significance, pagination, usage, and cacheAgeSeconds. Add 10-15 minute caching, error handling, and a no-results state. Do not expose Synorb credentials to browser code. Add a setup note with curl -s https://synorb.com/connect.
FAQ

Questions builders ask.

Why use Cursor for a content feed API?

Cursor is useful when the feed has to land inside an existing repository with local route conventions, types, tests, and a clear pull request diff.

Should the frontend call Synorb directly?

No. The frontend should call your backend endpoint. Your backend should call Synorb with server-side credentials.

What response shape should the API return?

Return normalized feed rows plus pagination and usage state. Preserve source URLs so the app can cite every item.

How does Cursor inspect Synorb data while building?

Connect Synorb MCP where available, or paste sample Manifest shapes from the docs, then implement the production route with REST.

Connect

Want to test Synorb feeds for free?

Provision starter credentials, then keep REST credentials server-side in the app you build.

curl -s https://synorb.com/connect
Get Keys More examples →