Monitor ScienceX science news across nanotechnology
Use Phys.org endpoints to turn monitor sciencex science news across nanotechnology into repeatable API requests with documented inputs and JSON responses.
翻译进行中。 该页面的简体中文翻译正在准备中，暂时以英文内容显示。
媒体与流媒体4 active endpointsapiKey
Phys.org API
ScienceX science news across nanotechnology, physics, astronomy and space, Earth science, chemistry, biology, and other sciences. Call sections to discover the nine verified science feeds, including breaking stories and editorials, then pass one of those exact slugs for headlines. Canonical dated /news/ story URLs are accepted for public article paragraphs. The linked byline points to ScienceX's editorial team rather than an individual author profile.
Collect ScienceX science news across nanotechnology, physics, astronomy and space, Earth science, chemistry, biology, and other sciences with documented Phys.
Endpoint families
4
Documented params
6
Examples
4
Live catalog snapshot
Phys.org coverage
Active endpoints
4
Methods
GET
Required params
6
Schema refs
4
Article1
Headlines1
News1
Sections1
{
"platform": "Phys.org",
"endpoint": "physorg-sections",
"method": "GET",
"path": "/physorg/sections",
"auth": "apiKey"
}Use cases
Workflows that fit Phys.org
Collect ScienceX science news across nanotechnology, physics, astronomy and space, Earth science, chemistry, biology, and other sciences with documented Phys.
Separate Phys.org feed records from article or profile follow-up
Use Phys.org endpoints to turn separate phys.org feed records from article or profile follow-up into repeatable API requests with documented inputs and JSON responses.
Preserve source URLs, dates, and access outcomes for review
Use Phys.org endpoints to turn preserve source urls, dates, and access outcomes for review into repeatable API requests with documented inputs and JSON responses.
Managed execution
How Crawlora handles this platform
Every figure below is read from the live Phys.org endpoint catalog — 4 endpoints, 6 documented request parameters, and 4 published response schemas — the same catalog Docs and Playground run against.
Documented endpoint coverage
4 documented Phys.org endpoints, grouped into 4 request families — Article, Headlines and News, plus 1 more.
Published request surface
6 request parameters are documented across those Phys.org endpoints, 6 of them required — the full input contract is public before you write any integration code.
Known response shape
4 of the 4 Phys.org endpoints ship a recorded example response, and 4 carry a documented response schema — you can code against the real JSON before the first request.
Documented failure modes
Phys.org endpoints document their error responses (400, 404, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
Agent-callable MCP tools
4 hosted MCP tools back the Phys.org endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
Know what the API can collect before integrating
1 endpoints
Article
/physorg/article
GETapiKey
1 endpoints
Headlines
/physorg/headlines
GETapiKey
1 endpoints
News
/physorg/news
GETapiKey
1 endpoints
Sections
/physorg/sections
GETapiKey
Endpoint catalog
Phys.org API endpoints
GETapiKeyexample
/physorg/articleGet a Phys.org article
Returns public Phys.org article metadata and readable body paragraphs from a canonical dated news URL. The service tries proxied HTTP first and uses the production browser fleet when the article edge challenges HTTP. Billing is 2 credits for an HTTP-profile success and 10 credits when browser rendering is required. No author-profile route was verified.
MCP tool physorg_article
url:queryx-api-key:header
GETapiKeyexample
/physorg/headlinesGet Phys.org section headlines
Returns current stories from one Phys.org feed. The accepted values are the seven Topics menu feeds plus the Breaking and Editorials feeds. Search and tag feeds are not included.
MCP tool physorg_headlines
section:queryx-api-key:header
GETapiKeyexample
/physorg/newsGet Phys.org top stories
Returns current stories from Phys.org's public all-stories RSS feed. Summaries are publisher-provided teasers. Use physorg-sections to discover the topic and editorial RSS feeds accepted by physorg-headlines.
MCP tool physorg_news
x-api-key:header
GETapiKeyexample
/physorg/sectionsList Phys.org RSS sections
Lists the seven topic feeds in Phys.org's Topics menu and its two additional public Breaking and Editorials feeds. Every returned slug is accepted by physorg-headlines. Search and tag feeds are not included.
MCP tool physorg_sections
x-api-key:header
Related APIs
More 媒体与流媒体 coverage
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.
How to scrape Phys.org
Extract Phys.org data in 4 steps
Phys.org is ScienceX science news across nanotechnology, physics, astronomy and space, Earth science, chemistry, biology, and other sciences. A live /physorg/sections response on 2026-10-14 contained 9 topic feeds; refresh it before scheduling because publisher feeds change. Call sections to discover the nine verified science feeds, including breaking stories and editorials, then pass one of those exact slugs for headlines. Canonical dated /news/ story URLs are accepted for public article paragraphs. The linked byline points to ScienceX's editorial team rather than an individual author profile. The API has no search, author, tag, or pagination contract. Do not interpret the organization/editorial-team page as a person profile or promise arbitrary archive traversal. Use the endpoint cards for this integration's accepted inputs. Publisher reference: https://phys.org/rss-feed/
- Step 1
Refresh Phys.org's editorial inventory
A live /physorg/sections response on 2026-10-14 contained 9 topic feeds; refresh it before scheduling because publisher feeds change. Call sections to discover the nine verified science feeds, including breaking stories and editorials, then pass one of those exact slugs for headlines. Canonical dated /news/ story URLs are accepted for public article paragraphs. The linked byline points to ScienceX's editorial team rather than an individual author profile.
- Step 2
Plan around Phys.org's source-specific constraints
The nine topical feeds let a collector separate subject areas before fetching stories. Article extraction is available on canonical story URLs, but no author endpoint or caller-controlled paging was validated; retain the source feed label with each article.
- Step 3
Carry Phys.org section context into each headline pull
The nine topical feeds let a collector separate subject areas before fetching stories. Article extraction is available on canonical story URLs, but no author endpoint or caller-controlled paging was validated; retain the source feed label with each article. Pass only a value returned by /physorg/sections and accepted by /physorg/headlines; preserve the selected desk with its results.
- Step 4
Check Phys.org article access before using body text
The API has no search, author, tag, or pagination contract. Do not interpret the organization/editorial-team page as a person profile or promise arbitrary archive traversal. Keep teaser, truncation, premium, or access fields beside the canonical URL so downstream users can see what the publisher actually returned.
FAQ
Scraping Phys.org: common questions
How should I scope a Phys.org headline pull?
A live /physorg/sections response on 2026-10-14 contained 9 topic feeds; refresh it before scheduling because publisher feeds change. Call sections to discover the nine verified science feeds, including breaking stories and editorials, then pass one of those exact slugs for headlines. Canonical dated /news/ story URLs are accepted for public article paragraphs. The linked byline points to ScienceX's editorial team rather than an individual author profile.
What should I preserve when using Phys.org's article route?
The API has no search, author, tag, or pagination contract. Do not interpret the organization/editorial-team page as a person profile or promise arbitrary archive traversal.
How do Phys.org topic feeds relate to article lookup?
Choose among the nine discovered topical feeds first and preserve the selected topic when you follow a canonical story link to article extraction. The API has no author route and no caller-controlled paging, so a feed-based research set should record when each topic sample was collected.