humantic_pi_profile_fetch_v1

Read an existing profile.

At a glance

Key inputs

One of profile_id / linkedin_url / email; optional format (md / html / pdf / json — default md), persona (sales / hiring), nocache.

Upstream API

GET /v1/user-profile

Example ask

Fetch the Humantic AI profile for sarah@acme.com.

Example tool call

humantic_pi_profile_fetch_v1({
  "email": "sarah@acme.com"
})

Example output

# Sarah Chen — VP Operations, Acme Corp
DISC: D/C · Strategist · High Confidence (92)
D 7.8 high · I 4.1 medium · S 2.8 low · C 8.9 high
OCEAN: Conscientious · Somewhat Open · Emotionally Balanced

## How Sarah shows up
Direct · Analytical · Results-Driven
Wants evidence before commitment; decides fast once the numbers hold up.
More likely to pick the option with the clearest measurable payoff.

## When writing an email
Subject: specific, outcome-led (3-5 words)   Length: short (80-100 words)
Bullet points: yes   Tone: crisp, factual   Close: one concrete next step

## Negotiating and closing
The secret to closing Sarah fast: a quantified business case and a low-risk pilot.
How fast will Sarah move? Quickly — once she has verified the numbers herself.

— format: "pdf" instead returns { "pdf_download_url": "https://mcp.humantic.ai/downloads/…" } (expires in 10 min)

Good to know. Fetches a cached profile in milliseconds; pass nocache to force a fresh read. It is also step two after a fresh profile_create — call it 30–45 seconds later to pick up the finished profile. Default md is compact Markdown for reading and summarizing; html returns one text/html resource, json the full raw envelope. Ask for format: "pdf" to get a shareable download link (generated on request, null while analysis is still running). persona switches the template between sales (default) and hiring.