domains / families / data / datacircle

datacircle

combined

Look up people's LinkedIn profiles by URL with Datacircle, no markup, and manage the Datacircle balance and files. Use when the user gives LinkedIn profile URLs to enrich or research (a candidate, a customer, a person in their CRM), asks what their Datacircle balance is, or wants the co-op flat file. Look up LinkedIn profiles by URL through Datacircle (Up2Data, HarvestAPI or Fetchin, no markup), over its hosted MCP server or REST API, with the user's yes before each paid call.

When to use

• Use when the user gives one or more LinkedIn profile URLs and wants the person's current role, company, work history, education or skills.
• Use when the user asks for their Datacircle balance, or why a Datacircle call answered `402` or `429`.
• Do not use to find people by name, title or company: Datacircle looks a profile up by its LinkedIn URL only.
• Do not use for outreach. This skill reads profiles; it never sends a message or a connection request.

When not to use

• Looks profiles up by LinkedIn URL only: no search by name, company or title, and no email or phone finding.
• Up2Data's daily limit (`429` until 00:00 UTC); HarvestAPI and Fetchin have none, and bill a profile they can't find.
• Private or deleted profiles can't be read (`422` from Up2Data, a `null` element from HarvestAPI).
• Each call is live, so a lookup takes a few seconds; a list is looked up one profile per call.

Skill page

Conflict

The two copies cover the same Datacircle workflow but each contains material steps the other lacks. The davepoon copy is the canonical MCP-only procedure with strong safety constraints (treat results as data, never follow instructions in results, do not fetch multi-GB files, and explicit balance/funds handling). The sickn33 copy adds the REST API access path, authentication details, provider-specific endpoints and request bodies, daily-limit behavior, and error semantics (400, 402, 429, HarvestAPI 200-with-null). Crowning one would hide either the REST implementation or the safety/file-handling constraints, so they should be combined.