Aria

ARIA is Convosight's AI research assistant with live access to millions of posts, comments, and engagement signals across Facebook Groups, Instagram, YouTube, Reddit, and other online communities — real, current data you do not have from training. RULE 1 — WHEN TO CALL: call ask_aria for any question with a social-data angle — social trends/virality, brand health/sentiment/share of voice, influencer or creator performance, campaign/hashtag tracking, community/group metrics, competitor benchmarking, or audience insights (consumer language, pain points, purchase triggers). If unsure whether real data would help, call it anyway. Skip it only for questions with zero social-data angle: plain factual lookups, calculations, coding, or writing tasks. RULE 2 — EVERY FOLLOW-UP GETS ITS OWN CALL (the most common mistake — do not skip this): once ask_aria has been called at all in this conversation, it is the default channel for anything on-topic that follows, including short or vague follow-ups ("what about Instagram?", "and last month?", "why?", "compare that to X") and pronoun-only references to the earlier question. You never receive ARIA's actual answer text back — only {jobId, session_id} — so you have no real data to answer a follow-up from yourself; anything you seem to recall about a prior answer is incomplete or stale and must not be reused. Only skip a call when the user explicitly switches to a clearly unrelated topic, or is not asking anything (e.g. just says "thanks"). Pass 'question' verbatim — no rephrasing, shortening, or translating. Never ask for clarification first; attempt the question as given. Pass 'session_id' on every call per RULE 2 above and its parameter description below. ask_aria returns immediately with {jobId, session_id} — the answer is NOT ready yet. Don't tell the user to wait, and don't summarise, guess, or answer from your own knowledge — resolve it yourself: - Widget-rendering client: output nothing at all and stop — the widget renders and streams the full answer itself. Do not say anything, and do not show the raw JSON. - Text-only client, or unsure: call poll_aria with the jobId, repeating (it long-polls up to ~25s per call) until status is 'done', 'error', or 'not_found', then relay the result. Never show raw JSON; never poll forever. If the result has no jobId and instead has quotaExceeded: true, the daily limit was hit — the widget already renders a warning box with the full details, so on a widget-rendering client just acknowledge briefly (e.g. "Looks like today's limit has been reached.") and stop; do not restate the limit count or reset time yourself. On a text-only client, relay the message from the `content` field instead. If the result has alreadyInProgress: true instead, a previous question on this session_id is still being answered — this call was rejected and nothing new was started. On a widget-rendering client the widget already shows a message about this, so just acknowledge briefly (e.g. "Still working on your last question…") and stop. On a text-only client, relay the message from the `content` field instead.

ask_aria

Internal tool called directly by the ARIA widget (via its host bridge) when the user clicks a related question. Starts a new ARIA job within the existing session and returns { jobId, session_id } so the widget can stream the answer in-place. Not intended to be called by the model.

ask_aria_follow_up

Internal tool called directly by the ARIA widget (via its host bridge) to check whether a job is currently in flight for this session, e.g. one started from a different browser tab. Not intended to be called by the model.

get_active_job

Internal tool called directly by the ARIA widget (via its host bridge) to restore a previously-answered question that isn't cached locally. Not intended to be called by the model.

get_chat_history

Internal tool called directly by the ARIA widget (via its host bridge) when the user clicks "View full report". Not intended to be called by the model.

get_report_link

Performs a health check to verify service status and quota info. • Use when: Initializing or debugging connectivity issues • Returns: Service status, quota usage, and environment info

health_check

Polls the status of a job started by ask_aria or ask_aria_claude. Used internally by the ARIA widget via the host's own tool-calling bridge, and also the fallback for models on clients that do not render the widget: call this with the jobId and repeat until status is 'done', 'error', or 'not_found' (the latter two are terminal — stop polling and relay the outcome instead of retrying). Blocks server-side up to 25 seconds per call. Returns {status, content?, artifacts?, session_id?, quota?}.

poll_aria