Post and voice research
Post and voice research turns a LinkedIn identifier into a picture of what someone posts about: recurring topics, tone, and how often they are active, the groundwork for outreach or a comment that lands.
Recipe#
- One voice check runs free: mint a key (
POST /v1/keys/mint, no body) under a shared budget of 200 credits per IP per day. linkedin_resolve_urlonly for a dirty or ambiguous URL; a clean profile URL, slug, or company URL goes straight to step 3. Cost: 2 credits.linkedin_get_posts: one page of posts with text, timestamps, and engagement counts. It detects person vs company automatically. Read the page for topics, tone, repost ratio, and thecreated_atspread (that spread is the posting cadence). Cost: 4 credits; each further page is priced the same.linkedin_get_profilewithsections: ["about"]when you want context on who is posting. Cost: 4 credits.
Total cost#
8 credits for one post page plus the author's overview.
Limits worth knowing#
linkedin_get_postsreturns an identifier's own recent posts, one page at a time. It is not a keyword search across LinkedIn and cannot fetch one specific post by URL.- For a company, pass the slug or URL, not a URN or numeric id.
- One page usually answers the voice question; page further only when you need more history, since every page costs the same.
Run it#
Full reference: /docs. Turning voice into an outreach list: /use-cases/outreach-list-builder.
Installable skill: the post-voice-research pack teaches your agent this whole job. Install every pack with npx skills add veezeehq/veezee-skills (/docs/skills).