treg_linkedin_post_detail $0.00125 per call

linkedin.post.detail — routed: best of 3 providers, own keys first. One LinkedIn post or article by URL — the provider's own object in `post`, with title/text/likes/comments where known (Multi-provider (routed) · LinkedIn)

For AI agents: call treg_linkedin_post_detail
POST https://toll402.dev/v1/p/treg.linkedin.post.detail
{
 "url": "https://example.com"
}
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": {
  "url": {
   "type": "string",
   "description": "identity"
  }
 },
 "additionalProperties": true,
 "description": "Send what you know; treg sends each provider only the fields it accepts ({url}). Omit a field you don't have: a url field holding something else, such as N/A, is refused (422 invalid_identity). On a miss it tries the next provider, cheapest first. Options are X-Treg-Route-* headers, never body fields. The answer is {output, raw, _treg}; X-Treg-Served-By names the provider."
}

MCP

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

All tools · OpenAPI