# LinkedIn Conversation Reply via OneShotAgent

> LinkedIn Conversation Reply via OneShotAgent is a paid API for AI agents from win.oneshotagent.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-11).

Sends a reply message into an existing LinkedIn conversation through a human-connected LinkedIn account, at a flat per-message price with idempotency and daily rate limits.

## Facts

- Endpoint: POST https://win.oneshotagent.com/v1/tools/linkedin/reply?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/linkedin-conversation-reply-via-oneshotagent-7b0c9737
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kFqhe_nHYp4Ad8-7e9quU

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-conversation-reply-via-oneshotagent-7b0c9737 -d '<json body>'
```

Example prompt: Reply to the LinkedIn conversation ID conv_abc123 on my account acct_xyz789 with this message: 'Thanks for reaching out — I'd love to schedule a 30-minute call next week to discuss your proposal.'

## When to prefer this

Use this endpoint when you need to programmatically reply to an existing LinkedIn conversation through a real, human-connected account — particularly for sales follow-ups, recruiter responses, or partnership outreach automation. It is appropriate when you already have a conversation_id (from the companion GET conversations endpoint) and need deterministic, idempotent delivery at flat cost. Prefer this over scraping or browser automation when reliability, auditability, and LinkedIn account safety matter.

## Known failure modes

- Daily per-account cap (default 50 messages) exceeded — request rejected until cap resets
- Invalid or expired conversation_id — conversation not found or not accessible by the account
- Invalid account_id — account not connected or permission `reply` not granted
- Duplicate Idempotency-Key reused with different parameters — conflict error
- Message text outside 1-4000 character range — validation error
- LinkedIn-side rate limiting or temporary unavailability — transient failure

## How this service works

Send a reply in an existing LinkedIn conversation through a human-connected account that granted `reply`. Flat price per message. Requires an Idempotency-Key header. Per-account daily cap (default 50) shared across all callers, randomized spacing; a message LinkedIn accepted cannot be recalled.

## Output

A confirmation that the message was accepted by LinkedIn and delivered into the conversation thread. The response includes delivery status and message metadata. Note: once accepted by LinkedIn, the message cannot be recalled.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "text": {
   "type": "string",
   "description": "Message text (1-4000 chars)"
  },
  "account_id": {
   "type": "string",
   "description": "Connected LinkedIn account id"
  },
  "conversation_id": {
   "type": "string",
   "description": "Conversation id from GET /v1/tools/linkedin/accounts/{id}/conversations"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "status": "processing",
  "linkedin": {
   "scheduled_for": null,
   "action_request_id": "uuid"
  },
  "request_id": "uuid"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/linkedin-conversation-reply-via-oneshotagent-7b0c9737/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from win.oneshotagent.com](https://www.zero.xyz/host/win.oneshotagent.com/llms.txt)