# LinkedIn URL resolver - Veezee

Agents meet LinkedIn URLs in every shape: share links with utm params, m. subdomains, trailing junk. This endpoint classifies any LinkedIn URL as a person, company, or post and returns the stable id, the handle, and the canonical URL, so the right fetch tool gets the right identifier.

It costs 2 credits. Skip it when you already hold a clean slug, URN, or URL: the fetch tools accept those directly, so resolving first would waste the call.

## Try it now

No account, no card: mint a free key in one call, then call the endpoint.

```
curl -s -X POST https://api.veezee.io/v1/keys/mint
```

```
curl "https://api.veezee.io/v1/linkedin/resolve-url?url=https%3A%2F%2Fwww.linkedin.com%2Fin%2Fwilliamhgates%3Futm_source%3Dshare" \
  -H "Authorization: Bearer $VEEZEE_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)"
```

## Over MCP

Point an MCP client at `https://mcp.veezee.io/linkedin` (streamable-http; `https://mcp.veezee.io/all` serves every platform over one connection) and call `linkedin_resolve_url`:

```json
{
  "method": "tools/call",
  "params": {
    "name": "linkedin_resolve_url",
    "arguments": {
      "url": "https://www.linkedin.com/in/williamhgates?utm_source=share"
    }
  }
}
```

## Parameters

| Param | Required | Type | Description |
| --- | --- | --- | --- |
| `url` | yes | `string` | A LinkedIn URL, e.g. https://www.linkedin.com/in/williamhgates or .../company/microsoft. |

Returns a `url_resolution` envelope. Full field list: https://veezee.io/docs/fields#url_resolution

## Pricing

`linkedin_resolve_url` costs 2 credits base per call (surcharges for optional sections, cursor pages, and batches: https://veezee.io/docs/tools/linkedin_resolve_url). Every key starts with a free budget of 200 credits per IP per day, no account, no card; past that, credits are $2.00 per 1,000 with no subscription required.

## FAQ

**Which id do I use for a company?**

The returned handle for fetches; the URN or numeric id is a people-search filter input, not a fetch identifier.

**What happens with non-LinkedIn URLs?**

INVALID_INPUT, stating the URL isn't LinkedIn.

**What about post URLs?**

They resolve to the post's activity URN. There is no single-post fetch, so read the author's [posts feed](https://veezee.io/linkedin-posts-api) for content.

## Read next

- [linkedin_resolve_url: the full reference](https://veezee.io/docs/tools/linkedin_resolve_url)
- [LinkedIn API for AI agents](https://veezee.io/linkedin-api-for-ai-agents)
- [Pricing](https://veezee.io/pricing)