Ottili LD3

Set up an RSS source

Connect an RSS or Atom feed as an LD3 source, validate the feed, understand verification, and manage the source company-scoped — Beta.

Overview

Set up an RSS source* explains how to connect an RSS or Atom feed as a content source in Ottili LD3*, validate the feed, and manage the source company-scoped. RSS feeds are one of several intake types that supply raw material for content automation.

RSS source intake is part of the Beta (BETA)* of Ottili LD3. Everything runs company-scoped: every source belongs to exactly one company (company_id) and is recorded through Ottili Core Audit*.

What an RSS source is in LD3

An RSS source is a publicly reachable feed (RSS 2.0 or Atom) that LD3 reads on a schedule. Typical feeds:

Blog feeds* — e.g. https://blog.example.com/feed.xml
Press and news feeds* — editorial outputs from publishers or agencies
Industry publications* — trade media with an RSS/Atom output
Status or changelog feeds* — release notes you want to monitor

Every feed item is ingested with its provenance*: LD3 keeps the original link and attribution so every claim in a later draft can be traced back to origin.

Prerequisites

An active Ottili ONE* company with access to the LD3 module (Beta).
A stably reachable feed URL* (HTTPS recommended) that returns valid RSS 2.0 or Atom.
At least one connected source (or monitored topic) before LD3 starts the pipeline.
See [LD3 sources](/docs/ld3-sources) and [LD3 source verification](/docs/ld3-verification).

Create an RSS source, step by step

1. Pick the source type* — in the LD3 sources surface, choose *RSS/Atom*.

2. Provide the feed URL* — paste the absolute address of the feed (see next section).

3. Capture metadata* — name, topic assignment and optionally language or region.

4. Activate* — the source starts delivering new items; LD3 attaches provenance to every claim it contains.

5. Let it verify* — before a draft is generated from the source, LD3 checks credibility, freshness and internal conflict.

Provide the feed URL correctly

Use the absolute URL* of the feed, not the website home page (the feed usually lives at /feed, /rss or /feed.xml).
The feed should return valid RSS 2.0 or Atom*; LD3 reads each item's title, link, publish date and content.
Prefer HTTPS* and a feed that stays reachable, so verification and citations stay valid.
Add multiple feeds from the same source as separate sources rather than combining one URL.

LD3 fetches the feed as part of source intake; a feed that is briefly unreachable is marked unreachable, not silently ignored.

What LD3 secures at intake (provenance)

At every intake, LD3 records:

Original link* — where the item was published.
Attribution* — which source delivered the item.
Timestamp* — when LD3 observed the item.

LD3 does not scrape anonymously: every source keeps its original link and attribution. This is what lets fact extraction and later review trace any claim back to its source.

RSS source verification

Source verification is verification-first. Before an RSS source feeds generation it is checked for:

Credibility* — known, attested sources are preferred; unknown ones are flagged.
Freshness* — stale or unreachable feeds are marked.
Internal conflict* — contradictory statements inside a feed are highlighted, never used silently.

Low-trust or conflicted sources are flagged, never used silently. For the meaning of maturity labels see [Understand feature status labels](/docs/understand-feature-status-labels).

Manage the source (status, metadata, weighting)

Once the RSS source runs, you manage it centrally:

Status* — active, paused or disabled; only active sources feed generation.
Maintain metadata* — name, topics and priority are editable at any time.
Check provenance* — original link and attribution stay attached per claim.
See verification results* — per source you can see whether and why LD3 rated it trustworthy or conflicted.
Adjust weighting* — the learning loop can weight sources more or less strongly over time (Early Access).
Remove* — removing a source takes it out of intake; already generated, verified facts remain traceably referenced.

Company context and audit

RSS sources in LD3 are natively part of Ottili ONE: one login (One Login), one company context (company_id), one audit trail (Ottili Core Audit) and one shared platform. Every action resolves to exactly one company and is recorded.

Status and availability

RSS source intake carries the product status Beta (BETA)*.

Capability	Status
RSS/Atom intake (Source Intake)	Beta (BETA)
Source verification	Beta (BETA)
Source management (status, metadata, weighting)	Beta (BETA)
Learning loop (source weighting)	Early Access (EARLY_ACCESS)