FeedMCP

Docs

Requests and responses

Requests

An endpoint ID with dots turned into slashes is its path: douyin.videos.comments.list is GET /v1/douyin/videos/comments/list. Parameters go in the query string, or POST them as JSON.

Responses

Every endpoint answers in the same envelope:

{
  "code": "ok",
  "request_id": "req_…",
  "data": {
    "items": [
      "…"
    ]
  },
  "page": {
    "next_cursor": "…",
    "has_more": true
  },
  "warnings": [],
  "meta": {
    "endpoint": "douyin.videos.comments.list",
    "platform": "douyin",
    "fetched_at": "2026-11-19T08:00:00.000Z",
    "billing": {
      "charged": true,
      "amount": "0.002",
      "currency": "USD",
      "balance": "9.98"
    }
  }
}
Field Meaning
data.item / data.items item for single objects, items for lists
page.next_cursor Cursor for the next page; null when there is none
meta.billing What this call cost and the balance left (USD)
meta.fetched_at When the platform was read
warnings Notes such as "No results"
request_id This call's ID, for support and lookups

Pagination

When a list has page.next_cursor, pass it back unchanged as cursor with the same other parameters. Each page is billed. A cursor only works on the endpoint that made it.

view=full

Add view=full to include the platform's raw data as raw, at the same price.

Look up a call

curl "https://api.feedmcp.com/v1/calls/req_…" -H "Authorization: Bearer $FEEDMCP_API_KEY"