---
ref: tool:datacircle/get-linkedin-profile-up2data
name: Get a LinkedIn profile from Up2Data
company: company:datacircle
workflows: []
access: [mcp, api]
tags: [capability:enrich-contacts, category:data-provider, has:api, has:mcp]
docs: https://docs.datacircle.dev/api-reference/up2data/enrich-one-linkedin-profile
updated: 2026-10-10
---

# Get a LinkedIn profile from Up2Data

Returns Up2Data's own answer for one LinkedIn profile URL, fetched live, plus datacircle_meta with the call's cost and the balance left.

Note: $2.375 per 1,000; a profile Up2Data can't find is free (422). Send X-Data-Provider: up2data. Datacircle caps Up2Data at $1 a day per account (421 profiles), with a shared daily limit for all customers; past either, 429 until 00:00 UTC. On MCP, provider defaults to up2data.

## Set up

Use the first option your agent supports.

### MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

```json
{ "mcpServers": { "datacircle": { "url": "https://api.datacircle.dev/mcp" } } }
```

Call the MCP tool `get_linkedin_profile` with `POST /v1/profiles/enrich`.

Server URL: https://api.datacircle.dev/mcp

Note: The first time, your client signs you in with your Datacircle email (OAuth). Each tool makes one REST call and costs what that call costs, from the same balance.

### API (official)

- Base URL: https://api.datacircle.dev
- Endpoint: `POST /v1/profiles/enrich`
- Auth: send the header `Authorization: Token $DATACIRCLE_API_KEY`
- Get a key: https://datacircle.dev/login
- Docs: https://docs.datacircle.dev/quickstart

Note: Send the provider's own request with an X-Data-Provider header naming it (up2data, harvestapi or fetchin). Every JSON answer adds datacircle_meta, with the call's cost and the balance left; a balance that can't cover the call answers 402.

Before anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
- Never print API keys.
