Get a LinkedIn profile from Fetchin

Get a LinkedIn profile from Fetchin

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

Note: $1.485 per 1,000, found or not (not found answers 404). No daily limit, but 5 requests a second across all customers (then 429, free). Send X-Data-Provider: fetchin; only profileUrlOrUrn, a full profile URL, is passed on. On MCP, set provider to fetchin.

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.

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

Call the MCP tool get_linkedin_profile with GET /api/v1/profile.

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: GET /api/v1/profile
• 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.