treg_linkedin_user_posts $0.001875 per call

linkedin.user.posts — routed: best of 2 providers, own keys first. List a LinkedIn member's recent posts from a profile URL or handle — treg picks the provider and names the one that served (Multi-provider (routed) · LinkedIn)

For AI agents: call treg_linkedin_user_posts
POST https://toll402.dev/v1/p/treg.linkedin.user.posts
{
 "linkedin_handle": "…"
}
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": {
  "linkedin_url": {
   "type": "string",
   "description": "identity"
  },
  "linkedin_handle": {
   "type": "string",
   "description": "identity"
  },
  "limit": {
   "type": "integer",
   "description": "filter; default 10; posts per page where the provider takes a count"
  }
 },
 "additionalProperties": true,
 "description": "Send what you know; treg sends each provider only the fields it accepts ({linkedin_url} | {linkedin_handle}) and fills linkedin_handle, linkedin_url from the rest. 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 "
}

MCP

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

All tools · OpenAPI