resolve_url 2 credits

Identify what a LinkedIn URL points at before fetching it. Give any LinkedIn profile, company, or post URL (utm params, www/m subdomains, trailing slashes are fine); get back {type: person|company|post, id, handle, canonical_url}. For profile URLs, id is the stable person URN; for company URLs, id is the stable company URN; for post URLs, id is the activity URN extracted from the URL. Use the returned handle or id with get_profile, get_company, or get_posts. Costs 2 credits. Skip this tool when you already have a slug, URN, or clean URL: get_profile and get_company accept those directly, so resolving first would waste 2 credits. Not for non-LinkedIn URLs; it returns INVALID_INPUT for those.

Parameters

REST

GET /v1/resolve · auth: required · metered: true

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

MCP

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

Input examples

Profile URL from a user message

{
  "url": "https://www.linkedin.com/in/williamhgates?utm_source=share"
}

Company URL

{
  "url": "https://linkedin.com/company/anthropicresearch"
}

Output

Returns a url_resolution envelope. Full field list: /docs/fields#url_resolution.

Errors

REST returns application/problem+json; MCP returns the same content as an error result. message is written as the next-turn instruction.