<!-- AUTO-GENERATED from the capability registry — regenerate: npm run generate:registry -->

# `person_linkedin` — Orange Slice capability

> Outcome-priced capability. One price for the answer, whichever providers it took.
> Everything we expose, with prices: https://orangeslice.ai/llms.txt

Finds a person's LinkedIn profile URL from their name plus a company or title. Searches, then has a model check the result against what you supplied, so a returned URL has been sanity-checked. Two credits, billed only when a profile is found.

## Price

**$0.004, charged per hit**

Billed only when the answer is found. A miss costs nothing.

The price is a property of the outcome, not of the work behind it. Whichever
vendor serves this call, and whatever it costs us, the number above is the number
quoted before the run and charged after it.


## Measured reliability

- **Hit rate:** 32% of runs resolve an answer.
- **Sample:** 133 runs, measured 2026-09-01.

Use these to choose between entries that both fit. Do not use them to rule
one out — a low hit rate is a fact about the world's data, not about whether the
call is worth making, and under this pricing a miss is free.


## Call it

**CLI**

```bash
orangeslice enrich person_linkedin --name "Jane Doe" --company Stripe

# a LinkedIn URL is all work_email needs, so the two chain directly:
echo '{"name":"Jane Doe","company":"Stripe"}' \
  | orangeslice enrich person_linkedin \
  | orangeslice enrich work_email
```

**HTTP**

```bash
curl -X POST 'https://orangeslice.ai/api/v1/run' \
  -H 'Authorization: Bearer $ORANGESLICE_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"capability":"person_linkedin","input":{"company":"<string>","keyword":"<string>","location":"<string>"}}'
```

**SDK**

```ts
await services.person.linkedin.findUrl({ company: "…", keyword: "…", location: "…" });
```

## Inputs

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `company` | string | No | Company name |
| `keyword` | string | No | Additional keyword, industry, etc. Any more data to specify the person |
| `location` | string | No | Location string (e.g., city, state, country) to narrow search results |
| `name` | string | No | Full name |
| `title` | string | No | Job title |

Inputs may also be piped as NDJSON, one JSON object per line.

## Output

```json
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "linkedinUrl": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ]
    }
  },
  "required": [
    "linkedinUrl"
  ],
  "additionalProperties": false
}
```

The field that carries the answer is `linkedinUrl`. It is
`null` — or empty — when nothing was found, which is how a miss is told from a
hit without knowing anything else about this entry.

## Before you run

- **Price it first.** `orangeslice enrich person_linkedin --dry-run` returns the
  exact dollar cost and spends nothing.
- **Large runs need approval.** Above the spend-gate threshold a run exits **7**
  until it carries a plan token, and only a dry run mints one.
- **Scopes:** enrich
- **Permitted uses:** research, outreach, export

## Exit codes

`0` ok · `2` bad input · `3` auth · `4` not found · `5` provider ·
`6` rate limited · `7` spend gate, nothing billed · `8` timeout ·
`9` a third-party account needs connecting