Attribution and support
Displaying coverage
Preserve the source and the article link wherever you show a story. Every record carries sources and every member carries a url; a reader who sees a headline should be one click from the newsroom that filed it.
Machine-written summaries and press-side labels are editorial aids, not scores. sides, lean, missingSides and state describe who published what, not whether a claim is true, and they are not a publisher licence. Use them as signals, label them as ours, and keep a human in the loop before anything is presented as a finding.
What the API is not
- Not a syndication feed. Full publisher article bodies are never returned, in the API or in bulk export.
- Not a factuality service. A
blindspotsays one camp did not cover a story; it does not say the story is right. - Not a real-time trading feed. Reads are cached for seconds to minutes, and
generatedAttells you when the page was computed.
Getting help
Write to support@itsbaba.com with the X-Request-Id from a failing response, the path, and the UTC time. That is enough to find the exact request.
The same address handles an Enterprise agreement, a custom quota, invoicing, an agreed SLA, or a use case you are not sure the licence covers. Ask before you build, not after.
Status and changes
/api/v1 is additive: fields are added, never removed or retyped. A breaking change would arrive as /api/v2 with v1 kept alive while you move. info.version in the OpenAPI document tracks additive revisions, so you can pin code generation to a known one.