Public-data workflow

B2B prospect & company enrichment

Research a company or known person from a LinkedIn slug — profiles, recent posts, jobs, post comments, plus open-web context.

B2B teams using public company, hiring, and profile signals for account planning.

Why it is hard

Public signal is scattered across platforms.

B2B sales and recruiting agents need dependable public context without a large provider subscription. UnifAPI exposes all 8 currently supported LinkedIn operations under one contract, using URL slugs as path keys and leaving unsupported legacy routes out of the catalog.

Account research brief

Hiring and company-post signals

Likely buyer or influencer roles

Outreach angles with source evidence

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.

Research this target account from public LinkedIn and social signals. Summarize company priorities, hiring signals, recent posts, likely buying committee, and outreach angles.
Workflow

From public records to a decision brief

1

Resolve the account

The agent starts from a company slug, profile URL, domain, or account name and chooses the narrowest public-data calls.

2

Gather B2B signals

LinkedIn company, job, post, and profile records can be joined with other public social sources through the same envelope.

3

Write an account plan

The final brief gives evidence, account hypotheses, suggested discovery questions, and follow-up searches.

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.