You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: examples/source_linked_briefing/README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ This example turns a Currents Search API response into two local files:
5
5
-`briefing.md` for a person to read;
6
6
-`briefing.json` for a dashboard, queue, or application-owned agent workflow.
7
7
8
-
Every item keeps its publisher URL and publication time. The script does not call a language model, summarize full publisher articles, or make decisions for the reader.
8
+
Every item keeps its source URL and publication time. The script does not call a language model, summarize full publisher articles, or make decisions for the reader.
9
9
10
10
The example accompanies [Build a Source-Linked News Briefing with Currents Search API](https://currentsapi.services/en/blog/build-source-linked-news-briefing-currents-search-api).
11
11
@@ -57,14 +57,14 @@ The Markdown output remains deliberately plain:
57
57
```markdown
58
58
# Source-Linked News Briefing
59
59
60
-
Generated at: 2026-07-25T00:00:00+00:00
60
+
Generated at: 2026-07-25T00:00:00Z
61
61
62
62
- Battery storage policy enters public consultation - <https://example.com/energy/storage-policy>
63
63
- Published: 2026-07-25T08:00:00Z
64
64
- A fictional example describing a public policy consultation.
65
65
```
66
66
67
-
The JSON output contains `generated_at` and a normalized `articles` list. Each article can contain:
67
+
The JSON output contains `generated_at` and a normalized `articles` list. Each normalized article contains:
0 commit comments