Skip to content

docs: fix agent content_type docs to match live API - #410

Merged
Rassl merged 1 commit into
mainfrom
docs/content-type-audio-video
Sep 14, 2026
Merged

Rassl merged 1 commit into
mainfrom
docs/content-type-audio-video

Conversation

@Rassl

@Rassl Rassl commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

POST /api/v2/content only accepts tweet, audio_video, document, webpage, arxiv_paper and legal_document. The docs listed youtube_video, web_page, link, github_repository, twitter_handle etc., all of which production rejects with INVALID_CONTENT_TYPE.

  • YouTube is audio_video (creates Episode); add curl example
  • verified content_type -> example URL -> node_type table
  • radar source_type values called out as never valid content_type
  • INVALID_CONTENT_TYPE added to the errors list

POST /api/v2/content only accepts tweet, audio_video, document, webpage,
arxiv_paper and legal_document. The docs listed youtube_video, web_page,
link, github_repository, twitter_handle etc., all of which production
rejects with INVALID_CONTENT_TYPE.

- YouTube is audio_video (creates Episode); add curl example
- verified content_type -> example URL -> node_type table
- radar source_type values called out as never valid content_type
- INVALID_CONTENT_TYPE added to the errors list
@Rassl
Rassl merged commit b3c245d into main Sep 14, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant