Zhihu Content detail API

AI prompt

Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.

Please help me write a data collection script with the EveryInfra Zhihu Content detail endpoint (zhihu/content_detail).

Endpoint contract:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to zhihu and action to content_detail, and put the parameters inside params.
- Required parameters:
  - url: The content URL or profile URL required by content-oriented actions. content_detail and content_comments accept answer, article, or video links (question pages are not supported).
- Returns one object. Main fields: id, type, url, title, text, like_count, comment_count, collect_count, posted_at, author_id, author_name, author_url; 17 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=zhihu.
- Example request body:
{
  "platform": "zhihu",
  "action": "content_detail",
  "params": {
    "url": "https://zhuanlan.zhihu.com/p/2032860336215307118"
  }
}
- Price: $0.56 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

Code samples

curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "zhihu",
  "action": "content_detail",
  "params": {
    "url": "https://zhuanlan.zhihu.com/p/2032860336215307118"
  }
}'

[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

{
  "id": "req_…",
  "platform": "zhihu",
  "action": "content_detail",
  "results": {
    "id": "2032860336215307118",
    "type": "article",
    "url": "https://zhuanlan.zhihu.com/p/2032860336215307118",
    "title": "GPT之父把AI扔回1930年：没见过一行代码，却「发明」了Python！",
    "text": "编辑：桃子\n【新智元导读】你敢信？一个活在95年前的AI，竟写出了Python代码。GPT之父下场，用2600亿Token炼出了一个「老古董」AI。\n一个从未见过电脑的AI，竟写出了现代编程语言！\n这可不是什么科幻的设定。\n就在今天，GPT之父Alec Radford带队发布了震撼全网的「talkie」——\n总参数130亿，一个只读过1931年之前旧文献的大模型。\ntalkie的「世界观」（全部训练数据），被冻结在了1930年12月31日。\n那个时代，没有互联网，没有维基百科，更没有任何现代代码。\n它读过的最「新」的东西，是近百年前的专利书、科学期刊、礼…",
    "like_count": 146,
    "comment_count": 64,
    "collect_count": 126,
    "posted_at": "2026-04-29T08:36:06+00:00",
    "platform": "zhihu",
    "author_id": "（已隐去）",
    "author_name": "（已隐去）",
    "author_url": "https://www.zhihu.com/（已隐去）",
    "author_avatar_url": "https://picx.zhimg.com/（已隐去）",
    "author_bio": "",
    "author_verified": true,
    "author_verification_label": "人工智能话题下的优秀答主"
  },
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}

Response fields

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

Errors and billing

401

Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.

422

Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.

402

Insufficient balance. Top up first.

429

The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.

503

Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.

200 empty

The request completed without data and is not charged (billing.reason = empty_result_refunded).

Official references

Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.

• Zhihu: Public Articles Are Not Granted for Arbitrary Republication or Model Training ↗

  Intellectual property terms in the Zhihu agreement require verifying relevant authorizations from the author and platform, while restricting unauthorized scraping, commercial use, and AI model development or training. Reading the content does not replace these permissions, nor does it indicate an endorsement by Zhihu.

  Checked 2026-09-04