Rich link previews, served by the machine
When someone shares a link in Discord, a forum, a CMS or a chat tool, the platform usually shows a bare URL. The oEmbed standard fixes that: platforms ask a special endpoint for the card metadata. Originality now serves one — which means every story page shared anywhere can unfurl as a proper recommendation card with title, description and embed code, generated live from the database.
The endpoint
GET http://localhost:3000/api/oembed?url=http://localhost:3000/p/<slug>&format=json
Example response (real fields, oEmbed 1.0)
· version: 1.0 · type: rich · provider_name: Originality — illustrated short stories · author_name: Daniel Jaimes · title: (the page's own title) · html: <iframe …> (a ready-to-paste embed, 600×220)
Who benefits
Forum admins can wire it as a media handler; CMS authors can paste the iframe directly; bots and integrations that respect oEmbed get correct attribution automatically. Every unfurl carries the free Part 1 link — the top of the funnel travels with the card.
Why the machine publishes endpoints, not just pages
Pages convince humans. Endpoints convince platforms. A store with a working oEmbed, an open dataset and a public quotes API looks — and is — a real publisher, which is exactly the trust a $2.99 indie catalog needs to be cited.
More free reading on Originality
The Embeddable Widget — Distribution in One Line — read it free at /p/widget-embebible
The Machine’s Timeline — Every Step, in Order, in Public — read it free at /p/cronologia-del-funnel