Humantic AI

Use this as STEP 2 to answer a specific question about a researched account, right after humantic_miia_report_sections_list_v1 has shown which sections the report has. Returns only the requested sections as markdown - decision makers and buying roles, tech stack, hiring, strategy, discovery questions, approach, next actions - so the answer comes from the report, not from memory. Pass create_request_id, report (executive_summary for approach, org structure, discovery questions and next actions; full_report for company detail, tech stack, hiring, leadership) and sections. sections = the exact section name(s) from the list call, as one string or an array. Ask for every section the question needs in one call. If a section name is wrong, the response lists the valid section names - call again with one of them. Free and instant.

humantic_miia_report_section_get_v1

Use this when an account report was started and the user asks 'is it ready?' or 'is my Carrier report done?', or before reading a report created in this conversation. Returns processing or ready. Pass create_request_id (from create, refresh or list), or category + buyer_company_domain + analysis_type. Timing: reports finish in about 2 minutes or in 15-20 minutes, rarely in between. Check once right after create, once about 2 minutes later, then not again until about 15 minutes have passed - faster polling returns nothing new. While processing, tell the user when to ask again; do not wait silently. When ready: humantic_miia_report_sections_list_v1 for a specific question, humantic_miia_report_fetch_v1 for the whole report. Not cached.

humantic_miia_report_status_v1

Create a Humantic Pi profile from EXACTLY ONE identifier (LinkedIn URL OR email OR free-form text). Returns the persisted profile when ready. To enrich with additional text later, use humantic_pi_profile_update_v1. If you have both a LinkedIn URL and an email for the same person and want both to resolve on fetch, call create separately for each — Humantic does not expose an automated linking operation.

humantic_pi_profile_create_v1

Enrich an existing Humantic Pi profile with additional text (bio, résumé excerpt, notes, writing sample) to improve confidence and unlock personality (DISC) analysis when previously insufficient. If no profile exists for the given identifier yet, one is created from this call. Accepts EXACTLY ONE identifier (linkedin_url, email, or profile_id). text is REQUIRED. Blocks until upstream LP returns. Pass force=true to bypass the 24h idempotency cache when you want to actually re-trigger upstream re-analysis (otherwise identical args within 24h return the cached prior response without consuming credits). Note: even on _status=ready, Humantic's downstream re-analysis may queue asynchronously — if confidence/DISC haven't moved, the response envelope's _idempotency_hit field tells you whether the call was cached or actually executed.

humantic_pi_profile_update_v1

Fetch an existing Humantic Pi profile by EXACTLY ONE identifier (profile_id, LinkedIn URL, OR email). Cached for 30 minutes per-token unless nocache=true. Returns NOT_FOUND if the profile doesn't exist. By default returns JSON (format=json). Pass format=html for one resource block: enriched profile as text/html under resource, with metadata / usage_stats / _status / _trace_id / _quota on _meta (same values as the JSON envelope).

humantic_pi_profile_fetch_v1

Use this when the user refers to an account that may already be researched - 'do we have a report on Wipro?', 'which accounts have I researched?', 'open my Carrier report' - and ALWAYS before humantic_miia_report_create_v1, so a credit is not spent on an account that already has a report. Returns every report under this key, newest first, grouped as COMPLETED, PENDING and FAILED, each with create_request_id, buyer and seller company, analysis_type, created_at and a short preview. Match on buyer_company or buyer_company_domain and take the newest COMPLETED one; an account can have several. Then pass that create_request_id to humantic_miia_report_sections_list_v1, humantic_miia_report_section_get_v1, humantic_miia_report_fetch_v1 or humantic_signals_per_account_v1. Takes no input.

humantic_miia_report_list_v1

Use this when the user wants the whole account report - 'show me the Carrier report', 'summarize the account plan', 'give me the full brief', 'export it as PDF'. Returns the complete report as markdown by default, which is best for reading and summarizing. format=html returns a styled standalone page; format=pdf returns a download link - use those only when the user asks for a file or a shareable view. For a specific question ('what is their tech stack?', 'who are the decision makers?') do NOT fetch everything: use humantic_miia_report_sections_list_v1 then humantic_miia_report_section_get_v1, which are much smaller and faster. Pass create_request_id (from create or humantic_miia_report_list_v1). Cached for 30 minutes; nocache=true bypasses.

humantic_miia_report_fetch_v1

Generate or rewrite sales outreach content matched to the recipient's DISC personality. responsetype selects the mode: personalizedemail (rewrite an email draft — content required), firstpitch (cold first-pitch email — prompt, user_context required, 5-1000 words each), reply / followup (thread continuation — content and earlier_message required). Identify the recipient by email OR linkedin_url (exactly one), or pass personalitytype directly if you already know their DISC type. Works without a pre-existing Humantic profile (upstream resolves one on the fly), but creating the recipient's profile first via humantic_pi_profile_create_v1 gives faster, higher-confidence results. Each generation consumes a content-personalization credit (a separate quota pool from profile credits); identical args within 24h return the cached result without consuming credits — pass force=true to regenerate. The response envelope's _idempotency_hit tells you whether the call was cached.

humantic_content_personalize_v1

Use this when an existing account report is out of date and the user wants it researched again - 'refresh the Bayer report', 'this is from March, update it', 'rerun the Wipro account plan with current data'. Regenerates the report with the original buyer, seller and analysis type and returns a NEW create_request_id; the old report stays available under its old id. Pass only create_request_id (from create or list). The report must be finished (ready or failed); the request is rejected while any report for the same buyer and seller is still generating - wait for it. ASYNC like create: tell the user it is running, then use humantic_miia_report_status_v1 with the NEW id - once about 2 minutes later, then not again until about 15 minutes have passed. Uses one MIIA credit. Identical calls within 24 hours return the same result at no cost (_idempotency_hit: true); force=true starts another regeneration. If the user only wants to know what is new at the account, use humantic_signals_per_account_v1 instead - free and instant.

humantic_miia_report_refresh_v1

Use this when the user reacts to a profile - 'that is the wrong John Smith', 'this is spot on', 'this is not accurate', 'this was not useful'. Records the feedback so the match can be corrected and accuracy improves. Wrong person: iscorrect=false plus correctid (the right person's identifier). Quality feedback: isaccurate and/or isuseful, true or false. The profile must already exist; returns NOT_FOUND otherwise. Returns immediately. Call only on explicit user feedback - never on your own judgment of the profile.

humantic_pi_profile_flag_v1