Monitor ScienceAlert's science reporting across Space
ScienceAlertエンドポイントを使えば、「Monitor ScienceAlert's science reporting across Space」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
翻訳作業中です。 日本語訳を準備中のため、このページは一時的に英語で表示されます。
メディア・ストリーミング稼働中エンドポイント 5件apiKey
ScienceAlert API
ScienceAlert's science reporting across Space, Health, Environment, Humans, Tech, Nature, Physics, and This Week in Science. Use the eight exact navigation sections to keep research monitoring focused, and open canonical story URLs for publicly available article paragraphs. Author URLs return profile metadata plus one recent-article page, which is useful for contributor context but not a complete archive.
Collect ScienceAlert's science reporting across Space, Health, Environment, Humans, Tech, Nature, Physics, and This Week in Science with documented.
エンドポイントファミリー
5
ドキュメント化されたパラメータ
8
サンプル数
5
ライブカタログスナップショット
ScienceAlertのカバレッジ
稼働エンドポイント
5
メソッド
GET
必須パラメータ
8
スキーマ参照
5
Article1
Author1
Headlines1
News1
{
"platform": "ScienceAlert",
"endpoint": "sciencealert-sections",
"method": "GET",
"path": "/sciencealert/sections",
"auth": "apiKey"
}ユースケース
ScienceAlertに適したワークフロー
Collect ScienceAlert's science reporting across Space, Health, Environment, Humans, Tech, Nature, Physics, and This Week in Science with documented.
Separate ScienceAlert feed records from article or profile follow-up
ScienceAlertエンドポイントを使えば、「Separate ScienceAlert feed records from article or profile follow-up」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Preserve source URLs, dates, and access outcomes for review
ScienceAlertエンドポイントを使えば、「Preserve source URLs, dates, and access outcomes for review」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
Crawloraによるこのプラットフォームの処理方法
以下の数値はすべて、稼働中のScienceAlertエンドポイントカタログから取得しています（エンドポイント5件、ドキュメント化されたリクエストパラメータ8個、公開レスポンススキーマ5件）。DocsとPlaygroundが参照しているカタログと同じものです。
ドキュメント化されたエンドポイント
ScienceAlertのエンドポイントは5件、5つのリクエストファミリーに分類されています（Article、Author、Headlinesほか2件）。
公開されたリクエスト仕様
これらのScienceAlertエンドポイントには8個のリクエストパラメータがドキュメント化されており、うち8個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
判明しているレスポンス構造
5件のScienceAlertエンドポイントのうち5件が実際のサンプルレスポンスを、5件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
ドキュメント化されたエラー
ScienceAlertのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、429、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
エージェントから呼べるMCPツール
ScienceAlertのエンドポイントは5個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
統合前にAPIで収集できるデータを把握
1エンドポイント
Article
/sciencealert/article
GETapiKey
1エンドポイント
Author
/sciencealert/author
GETapiKey
1エンドポイント
Headlines
/sciencealert/headlines
GETapiKey
1エンドポイント
News
/sciencealert/news
GETapiKey
1エンドポイント
Sections
/sciencealert/sections
GETapiKey
エンドポイントカタログ
ScienceAlert APIエンドポイント
GETapiKeyexample
/sciencealert/articleGet ScienceAlert article content
Returns a ScienceAlert article by absolute canonical `url`: title, description, section, authors, publication and update times, image, the cleaned body `paragraphs` and a `paywalled` flag. Section pages and author listing URLs are rejected.
MCPツール sciencealert_article
url:queryx-api-key:header
GETapiKeyexample
/sciencealert/authorGet a ScienceAlert author profile
Returns a ScienceAlert author's profile and one page of articles, from an author listing `url` in the form `https://www.sciencealert.com/<author>/page/<number>`; the first observed page is `/page/0`. The response has the name, `slug`, biography, image, social links, that page's articles, and `page` and `has_next_page` for paging.
MCPツール sciencealert_author
url:queryx-api-key:header
GETapiKeyexample
/sciencealert/headlinesGet ScienceAlert section headlines
Returns the latest ScienceAlert stories for one section. `section` is required and takes `space`, `health`, `environment`, `humans`, `tech`, `nature`, `physics` or `this-week-in-science`; other values are rejected. Each item has its title and URL.
MCPツール sciencealert_headlines
section:queryx-api-key:header
GETapiKeyexample
/sciencealert/newsGet ScienceAlert top stories
Returns ScienceAlert's latest top stories across the site. Takes no parameters, and `sciencealert-headlines` narrows by section instead. Each item has its title, URL, summary, author and publication time.
MCPツール sciencealert_news
x-api-key:header
GETapiKeyexample
/sciencealert/sectionsGet ScienceAlert sections
Lists the eight top-level ScienceAlert sections that `sciencealert-headlines` accepts: `space`, `health`, `environment`, `humans`, `tech`, `nature`, `physics` and `this-week-in-science`. Each entry has a `slug`, a display `name` and the section page `url`.
MCPツール sciencealert_sections
x-api-key:header
関連API
メディア・ストリーミングのその他のカバレッジ
Media & Streaming
FUSSBALL.DE
Follow German football from the Bundesliga down to the lowest Kreisklasse. Discover competitions in all 22 federations, then read matchdays, standings, scorers, clubs, teams, and players from the DFB's own amateur-football portal.
Media & Streaming
Sportskeeda
Browse Sportskeeda's sports and entertainment coverage, community wikis, quizzes, and fan games with the catalog's current slugs and filter limits.
Media & Streaming
JustWatch
Research streaming catalogs, title availability, providers, offers, seasons, episodes, and release changes from JustWatch with normalized JSON.
ScienceAlertのスクレイピング方法
5ステップでScienceAlertのデータを抽出
ScienceAlert is ScienceAlert's science reporting across Space, Health, Environment, Humans, Tech, Nature, Physics, and This Week in Science. A live /sciencealert/sections response on 2026-10-14 contained 8 section records; refresh it before scheduling because publisher feeds change. Use the eight exact navigation sections to keep research monitoring focused, and open canonical story URLs for publicly available article paragraphs. Author URLs return profile metadata plus one recent-article page, which is useful for contributor context but not a complete archive. Section pagination was not validated and produced an access error in testing; the API exposes no page parameter. Do not promise complete archives or bypass publisher access controls. Use the endpoint cards for this integration's accepted inputs. Publisher reference: https://www.sciencealert.com/
- ステップ 1
Refresh ScienceAlert's editorial inventory
A live /sciencealert/sections response on 2026-10-14 contained 8 section records; refresh it before scheduling because publisher feeds change. Use the eight exact navigation sections to keep research monitoring focused, and open canonical story URLs for publicly available article paragraphs. Author URLs return profile metadata plus one recent-article page, which is useful for contributor context but not a complete archive.
- ステップ 2
Plan around ScienceAlert's source-specific constraints
Record the exact section slug returned by discovery before creating a scheduled feed pull. The article route and public contributor profiles are distinct lookups; no caller-controlled archive page was validated, so do not derive paging from buttons on the website.
- ステップ 3
Carry ScienceAlert section context into each headline pull
Record the exact section slug returned by discovery before creating a scheduled feed pull. The article route and public contributor profiles are distinct lookups; no caller-controlled archive page was validated, so do not derive paging from buttons on the website. Pass only a value returned by /sciencealert/sections and accepted by /sciencealert/headlines; preserve the selected desk with its results.
- ステップ 4
Check ScienceAlert article access before using body text
Section pagination was not validated and produced an access error in testing; the API exposes no page parameter. Do not promise complete archives or bypass publisher access controls. Keep teaser, truncation, premium, or access fields beside the canonical URL so downstream users can see what the publisher actually returned.
- ステップ 5
Use ScienceAlert's contributor route for its documented purpose
Use the eight exact navigation sections to keep research monitoring focused, and open canonical story URLs for publicly available article paragraphs. Author URLs return profile metadata plus one recent-article page, which is useful for contributor context but not a complete archive. Section pagination was not validated and produced an access error in testing; the API exposes no page parameter. Do not promise complete archives or bypass publisher access controls.
FAQ
ScienceAlertのスクレイピング：よくある質問
How should I scope a ScienceAlert headline pull?
A live /sciencealert/sections response on 2026-10-14 contained 8 section records; refresh it before scheduling because publisher feeds change. Use the eight exact navigation sections to keep research monitoring focused, and open canonical story URLs for publicly available article paragraphs. Author URLs return profile metadata plus one recent-article page, which is useful for contributor context but not a complete archive.
What should I preserve when using ScienceAlert's article route?
Section pagination was not validated and produced an access error in testing; the API exposes no page parameter. Do not promise complete archives or bypass publisher access controls.
Can ScienceAlert articles be paged by an archive button?
The publisher page may expose more-story controls, but the validated public contract does not offer an archive page input. Use a returned section slug for headlines and canonical URLs for article requests; do not infer a stable page cursor from browser behavior. Contributor profiles are a separate route and should be resolved from a verified profile URL, not from a guessed author-name search.