treg_facebook_post_comments $0.00235 per call

facebook.post.comments — routed: best of 2 providers, own keys first. Comments on a public Facebook post by post id or URL — provider-native comment rows in `comments` (Multi-provider (routed) · Facebook)

For AI agents: call treg_facebook_post_comments
POST https://toll402.dev/v1/p/treg.facebook.post.comments
{
 "post_id": "…"
}
Answers 402 with x402 payment requirements; pay with any x402 client (@x402/fetch, x402 for Python, toll402-client, toll402-mcp) or send a prepaid-credits key as x-toll402-key (https://toll402.dev/credits). Paid per call via x402 (USDC on Base) or with a prepaid-credits key (x-toll402-key, card at /credits); charged only on success. Start at /llms.txt or connect the MCP server: npx -y toll402-mcp · remote https://toll402.dev/mcp.

Input schema

{
 "type": "object",
 "properties": {
  "post_id": {
   "type": "string",
   "description": "identity key (part of post_id)"
  },
  "url": {
   "type": "string",
   "description": "identity key (part of url)"
  }
 },
 "additionalProperties": true,
 "description": "Send everything you know about the subject — treg derives the rest (full_name ⇄ first+last), matches each provider on the variants it accepts ({post_id} | {url}) and sends each provider only the fields it wants. On a miss treg keeps trying providers, cheapest first, within X-Treg-Route-Max-Cost (default $1 per call; misses on per-success providers are free). Options ride as headers, never in the b"
}

MCP

{"mcpServers":{"toll402":{"command":"npx","args":["-y","toll402-mcp"],"env":{"TOLL402_WALLET_KEY":"0x..."}}}}

All tools · OpenAPI