# ScopeAPI Facebook Post Comments Fetcher

> ScopeAPI Facebook Post Comments Fetcher is a paid API for AI agents from scopepay.vercel.app, paid per call via x402, $0.5/call, status unknown (last checked 2026-09-15).

Fetches comments on a specific Facebook post by post ID, returning social engagement data via pay-per-call micropayment.

## Facts

- Endpoint: GET https://scopepay.vercel.app/api/facebook/post/%7BpostId%7D/comments
- Price: $0.5/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/scopeapi-facebook-post-comments-fetcher-de72ed33
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ue4ECtnzDX_4GK6Oc5kdv

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability scopeapi-facebook-post-comments-fetcher-de72ed33
```

Example prompt: Can you pull all the comments from the Facebook post with ID 1234567890abcdef so I can see what people are saying about it?

## When to prefer this

Use this endpoint when you need to retrieve comments from a specific Facebook post by its ID and are willing to pay $0.50 USDC per call via x402 micropayment. Prefer this over scraping Facebook directly when you need a clean REST API interface without managing Facebook API credentials. Best suited for social listening, sentiment analysis, brand monitoring, or competitive intelligence use cases on Facebook content.

## Known failure modes

- Invalid or non-existent postId returns empty data or error response
- Private or restricted Facebook post returns no data due to access limitations
- Payment failure (insufficient USDC balance) results in 402 response and no data returned
- Rate limiting or upstream Facebook data source unavailability causes request failure
- Malformed postId path parameter returns a 400-level error

## How this service works

37 paid REST endpoints: Facebook social & ads intelligence, Amazon e-commerce data, job market intelligence. Pay per call via x402 micropayments (USDC on Base).

## Output

A JSON object containing comment data sourced from the specified Facebook post, including user reactions, replies, and engagement details, returned under a 'data' field with source attribution to ScopeAPI.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "postId": {
       "type": "string"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {},
  "source": "ScopeAPI"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/scopeapi-facebook-post-comments-fetcher-de72ed33/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from scopepay.vercel.app](https://www.zero.xyz/host/scopepay.vercel.app/llms.txt)
