How do I fix Xiaohongshu error 461 or missing xsec_token when fetching notes?
Xiaohongshu error 461 indicates anti-bot verification or signature rejection, while xsec_token is a short-lived access token required on note and comment requests. FeedMCP handles signing and session reliability server-side ($0.02/call, failures free)—you only pass a note ID or search query.
If the platform returns a transient error, FeedMCP responds with charged: false and clear retry guidance so your pipeline never pays for failed calls. See Xiaohongshu APIs.
Endpoints and pricing
| Endpoint | ID | Price | What it returns |
|---|---|---|---|
| Xiaohongshu note | xiaohongshu.notes.get |
$0.02 | One note: title, text, tags, cover, author, and its likes, saves, comments and shares |
| Xiaohongshu note comments | xiaohongshu.notes.comments.list |
$0.02 | Comments under a note: text, time, commenter, likes and reply count, page by page |
| Xiaohongshu note search | xiaohongshu.notes.search |
$0.02 | Search notes by keyword, ordered by relevance, newest or most liked, within a time range |
Pay per call with failed calls free. Verify live prices for free via GET https://api.feedmcp.com/v1/catalog/prices and cap per-call spend with X-Max-Price.
How to do it
Option 1: Ask your AI via MCP
- Sign up in the console ($0.10 free trial credit, no card) and create an API key with a spend cap.
- Add
https://api.feedmcp.com/mcpto Claude, Cursor, Codex or Cherry Studio via the MCP setup page or Integrations. - Ask your AI:
Fetch this Xiaohongshu note and its comments via FeedMCP without dealing with 461 errors
Option 2: Call the HTTP API directly
curl "https://api.feedmcp.com/v1/xiaohongshu/notes/get" \
-H "Authorization: Bearer $FEEDMCP_API_KEY" \
-H "X-Max-Price: 0.02"
Key facts at a glance
| Item | Detail |
|---|---|
| Starting price | $0.02 and up (pay per call, no subscription) |
| Failed calls | Free (charged: false) |
| Spend guardrails | Per-key spend cap + X-Max-Price + Idempotency-Key |
| Data scope | Public data only; no platform account login required |
| Access | Remote MCP (Streamable HTTP) + REST API + OpenAPI |
Questions
How do I fix Xiaohongshu error 461 or missing xsec_token when fetching notes?
Xiaohongshu error 461 indicates anti-bot verification or signature rejection, while xsec_token is a short-lived access token required on note and comment requests. FeedMCP handles signing and session reliability server-side ($0.02/call, failures free)—you only pass a note ID or search query.
How much do these endpoints cost? Are failed calls billed?
Endpoints on this page start at $0.02 per call with no monthly subscription and non-expiring balances. Bad parameters, timeouts, upstream errors and missing objects are free. New accounts receive $0.10 trial credit, no card required.
Do I need my own platform account or cookies?
No. FeedMCP reads public data only; calls never go through your personal accounts.
Related answers
- How do FeedMCP, DataXAPI, Qovia and AIsa compare for social media data and MCP?
- How to use TikHub-style Douyin, Xiaohongshu and TikTok endpoints in Claude or Cursor via a hosted MCP server?
- How to connect OpenClaw, Antigravity, Windsurf or Grok agents to a social media data MCP server?
- Can ChatGPT read Xiaohongshu (RedNote) notes and comments?
- How do I let Claude or Cursor read Xiaohongshu notes, comments and PGY data?
- How do I batch export Xiaohongshu comments and replies to CSV or Excel?