Skip to main content
GET
Get signal detail
title, url, and published_at always describe the full source. The units may reflect only a segment of that source (e.g., a five-minute exchange in a two-hour podcast). See Signal scope vs. source scope.

Authorizations

X-API-Key
string
header
required

API key for authentication. Include in every request as X-API-Key: gld_your_key_here.

Path Parameters

signal_id
string
required

Unique signal identifier.

Example:

"0001f3a7b9c8d4e5f6a7b8c9d0e1f2a3b4c5d6e7"

Response

Successful Response

Full signal as a flat list of verified units (grouped by role, in document order).

signal_id
string
required
Example:

"0001f3a7b9c8d4e5f6a7b8c9d0e1f2a3b4c5d6e7"

url
string
required
Example:

"https://reuters.com/technology/nvidia-h200-shipments"

verified_unit_count
integer
required

Number of verified units in the decomposition (equals len(units) in detail). The honest depth signal — use this, not statement length, to gauge analytical depth.

Example:

12

title
string | null
Example:

"NVIDIA H200 Shipments Surge as Supply Eases"

published_at
string | null

Publication timestamp (ISO 8601).

Example:

"2026-01-15T10:00:00Z"

content_type
enum<string> | null
Available options:
analysis,
event
Example:

"analysis"

domain
string | null

Source registrable domain.

Example:

"reuters.com"

themes
Themes · object
entities
EntitySummary · object[]
units
Unit · object[]

Flat list of verified units, grouped by role (central statement, then arguments, then claims) in document order. List position is the order; there is no separate index field.