# LinkedIn Invitation Withdraw

> LinkedIn Invitation Withdraw 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-10).

Withdraws a pending outgoing LinkedIn connection invitation on behalf of a specified account.

## Facts

- Endpoint: POST https://win.oneshotagent.com/v1/tools/linkedin/invite/withdraw?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/linkedin-invitation-withdraw-4bd4949f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_SnC95LJOX819LjkOIjQnB

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-invitation-withdraw-4bd4949f -d '<json body>'
```

Example prompt: Withdraw my pending LinkedIn invitation with ID inv-abc123 on my account 0xWallet123 — I sent it by mistake and want to cancel it before they see it.

## When to prefer this

Use this endpoint when you need to programmatically cancel an outgoing LinkedIn connection invitation that has not yet been accepted, particularly in automated outreach workflows or agent-driven LinkedIn management pipelines. Prefer this over manual LinkedIn UI actions when operating at scale or within an agentic workflow that already uses the OneShot Agent API for LinkedIn automation.

## Known failure modes

- Invalid or non-existent invitation_id returns an error or empty result on polling
- Invitation already accepted or expired — cannot be withdrawn
- Account_id not authorized or not found
- Rate limiting or LinkedIn anti-bot restrictions causing failures
- Payment not completed (402 Payment Required) — must sign and resend with payment header
- Polling timeout if LinkedIn takes too long to process withdrawal

## How this service works

Tools, payments, and compute orchestration for autonomous AI agents.

## Authentication

- **`x402Payment`** — paid tool endpoints use the [x402 payment protocol](https://x402.io).
  First call returns `402 Payment Required` with a quote; sign and resend the request
  with `Authorization: <signed payment header>` and `X-Quote-ID: <quote_id>`.
- **`agentId`** — free read-only endpoints accept `X-Agent-ID: <wallet>` (0x… address).
- **`soulKey`** — soul marketplace seller dashboard uses `Authorization: Bearer soul_…`
  (issued by `POST /v1/soul/register`).
- **`acpBearer`** — Stripe ACP checkout sessions use a separate bearer token plus the
  `API-Version: 2026-01-30` header.

## Async tools & polling

Most tool endpoints return `202 Accepted` with `{ request_id, tool, status }`. Poll
`GET /v1/requests/{id}` (with the same `X-Agent-ID`) to retrieve the final result.
A WebSocket fallback is available at `wss://<host>/v1/requests/subscribe`.

## Pricing

See [docs.oneshotagent.com/pricing](https://docs.oneshotagent.com/pricing) for the full
table. Per-call costs for this environment, rendered from the same config the routes bill from:

| Tool | Cost |
|---|---|
| Web search | $0.001 |
| Web read | $0.002 |
| Research | $0.01 |
| Person enrichment | $0.005 |
| Email verification | $0.001 |
| Deep research (person) | $0.05 |
| Social profiles | $0.50 |
| Local business search | $0.01 |
| Commerce search | $0.002 |
| LinkedIn history sync | $0.02 per bounded run |
| LinkedIn reply | $0.02 per message |
| LinkedIn profile view | $0.01 per view |
| LinkedIn post reaction | $0.01 per reaction |
| Email send | quote-based; service fee from $0.005 per send |
| SMS send | $0.0035 per segment per recipient |
| Voice call | $0.35/minute + $5.00 number registration on the first call |
| Browser task | quote-based; minimum $0.005 |
| Website build | quote-based; from $1.00 |
| Compute goal | quote-based; minimum budget $1.00 + 20% platform fee |

## Error format

`{ "error": "<machine_code>", "message": "<human readable>", "details": <optional> }`.
Validation errors include a `details` field with the failing field paths.

## Output

Returns a 202 Accepted response with a JSON body containing a request_id, the tool name, and a processing status. The actual withdrawal result can be retrieved by polling GET /v1/requests/{request_id} with the same Agent ID. The response also echoes back the invitation_id that was targeted.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "account_id": {
   "type": "string"
  },
  "invitation_id": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "status": "processing",
  "linkedin": {
   "invitation_id": "uuid"
  },
  "request_id": "uuid"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/linkedin-invitation-withdraw-4bd4949f/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)