humantic_pi_profile_update_v1

Enrich a profile with extra text to raise confidence / unlock DISC.

At a glance

Key inputs

identifier (linkedin_url / email / profile_id) + text written by the person — emails, posts, a cover letter (300+ words); optional force.

Upstream API

POST /v1/user-profile/create (profile_enrich=true)

Example ask

Here are three emails Sarah wrote me — add them to her profile so the read firms up.

Example tool call

humantic_pi_profile_update_v1({
  "linkedin_url": "https://linkedin.com/in/sarah-chen-vp",
  "text": "Hi Marcus — quick update before Thursday. I went through the vendor shortlist last night and the payback math on two of the three doesn't hold up past month nine. I'd rather cut scope than carry a tool we can't justify at renewal. Proposal: pilot with the ops pod for six weeks, measure time-to-first-touch and rep hours saved, then decide. If the numbers land, we expand; if not, we walk. Can you get me the CFO slot before the board pack closes? …"
})

Example output

{
  "status": "200",
  "message": "Success",
  "metadata": { "status": "FOUND", "status_code": 1, "analysis_status": "IN_PROGRESS", "analysis_type": "linkedin" },
  "_status": "processing",
  "_idempotency_hit": false,
  "_trace_id": "05b5cbcd9fd71419",
  "_quota": { "pool": "api", "limit": 3000, "consumed": 414, "remaining": 2586 }
}
// text is queued for re-analysis — call profile_fetch after 30–45 seconds to read the updated confidence / DISC
// _idempotency_hit:false confirms the upstream call actually ran; identical args within 24h are served from cache unless force:true

Good to know. text must be written by the person — their emails, posts, or a cover letter — not a bio about them. 300+ words gives Humantic AI enough signal (only the first 10K words are read). Once uploaded the analysis goes to processing: call profile_fetch after 30–45 seconds to get the sharper read or newly unlocked DISC. Identical calls within 24h are served from cache — pass force to re-run.