# LinkedIn Person Posts Fetcher

> LinkedIn Person Posts Fetcher is a paid API for AI agents from x402.orthogonal.com, paid per call via x402, $0.08/call, status unknown (last checked 2026-09-14).

Retrieves posts from a specific person's LinkedIn profile, with pagination support and cost-efficient billing for multi-page requests.

## Facts

- Endpoint: GET https://x402.orthogonal.com/aviato/social/person/posts
- Price: $0.08/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/linkedin-person-posts-fetcher-9a1cd112
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_A3hytWSmS91pQAiU-ake9

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 linkedin-person-posts-fetcher-9a1cd112
```

Example prompt: Can you pull the latest LinkedIn posts from the profile with LinkedIn ID 'ACoAAxxxxx'? Grab the first page with 10 posts per page.

## When to prefer this

Use this endpoint when you need to retrieve the public post history of a specific known LinkedIn person — identified by their LinkedIn ID or entity ID. It is particularly cost-efficient for multi-page fetches due to its parentRequestId billing model that charges 0 for continuation pages. Prefer this over generic web scraping when structured LinkedIn post data is needed for a specific individual.

## Known failure modes

- Invalid or missing linkedinID/linkedinEntityID returns an error or empty result
- Profile not found or private profile returns no posts
- Rate limiting or access restrictions from LinkedIn may cause failures
- Missing required query parameters results in a 400-level error
- Network timeout for profiles with large post histories

## How this service works

Get posts from a person's LinkedIn profile. Pagination billing: call the first page normally and save billing.requestId from the Orthogonal /v1/run response. For later page, offset, or cursor calls on the same logical search, pass parentRequestId with unchanged non-pagination parameters. Valid continuation calls still get their own request IDs and quoted price, but are charged 0. Changing filters starts a new billable request.

## Output

Returns a paginated list of LinkedIn posts from the specified person's profile, including post content, timestamps, and engagement metadata. Also includes a billing.requestId that should be saved and passed as parentRequestId for subsequent page calls to avoid being charged for continuation pages.

## 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"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "page": {
       "type": "integer",
       "description": "For later pages of the same logical search, keep non-pagination parameters unchanged and pass top-level parentRequestId from the first Orthogonal /v1/run response."
      },
      "perPage": {
       "type": "integer"
      },
      "linkedinID": {
       "type": "string"
      },
      "linkedinEntityID": {
       "type": "string"
      }
     }
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/linkedin-person-posts-fetcher-9a1cd112/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.orthogonal.com](https://www.zero.xyz/host/x402.orthogonal.com/llms.txt)