Public-data workflow

Lead & company enrichment

Enrich a company or person from name → website, recent news, social presence, structured data.

Sales, recruiting, and research workflows that need public context before outreach.

Using ChatGPT, Claude Code or another client? See the setup steps

Why it is hard

Public signal is scattered across platforms.

Most enrichment vendors solve one slice — emails, company data, or social. Agents need public company and social context in the same response shape.

Lead or company context brief

Public profile, post, job, or company signals

Suggested discovery questions

Source gaps that need human verification

Run prompt

Start the agent from a concrete task

Replace the market, brand, competitor, or creator set, then let the agent call UnifAPI MCP only when it needs live public-data evidence.

Enrich this person or company from public sources. Summarize visible company context, recent public posts, roles, relevant signals, and suggested discovery questions.
Workflow

From public records to a decision brief

1

Start with a name, company, or profile URL

The agent resolves browser-visible identifiers such as LinkedIn slugs, handles, and source URLs into API calls.

2

Attach public evidence

UnifAPI returns company, profile, post, and public social records without asking the user to maintain separate collectors.

3

Prepare the next conversation

The output is a research brief with talking points and uncertainty clearly marked.

Live API sources

APIs this workflow can call

Next step

Run it as a Skill, then productize over HTTP.

Use the related Skill when a human wants an agent-ready brief.

Use the API catalog when the workflow graduates into production code.

Keep every public-data call tied to a source URL, request id, and billing record.