Returns the finished remix for a remix_post job: adapted title, description, script segments and checklist. Free to call. Poll get_job_status until the job reports completed, then fetch here. The result is also viewable in the web app under Content Ideas.
A free endpoint that returns the completed output of a remix_post job: the adapted title, description, script segments and execution checklist. It is the collection step of the remix flow, called once the asynchronous job has finished. Reading a result never costs credits; only the remix itself was billed.
Connect the Viral Outliers MCP server once and the get_remix_result tool becomes available to your agent alongside all other skills:
claude mcp add --transport http viral-outliers https://viraloutliers.com/api/mcp \
--header "Authorization: Bearer so_live_YOUR_KEY"In Claude.ai or ChatGPT, add a custom connector pointing at https://viraloutliers.com/api/mcp. Your agent then calls get_remix_result on its own whenever the task needs it.
| Name | Type | Description |
|---|---|---|
jobRef* | string (path) | The pipeline jobRef returned by remix_post (URL-encode it). |
Given the jobRef returned by remix_post, it returns the finished remix, the adapted title, description, segment-by-segment script and checklist, in structured form ready to act on. It returns status and result together, so a populated remix field tells you the job is done and hands you the content in the same call.
It is free and read-only. The credits for the adaptation were spent when remix_post queued the job (and refunded automatically if it failed), so fetching the result as many times as you need costs nothing.
Use it after remix_post: poll get_job_status (or get_remix_result directly) with the jobRef until the remix is populated, then pull the structured script into your own rendering, scheduling or review pipeline. Because it is idempotent and free, it is also the way to re-retrieve a remix later without regenerating it.
The same finished idea is viewable in the web app under Content Ideas, so a human collaborator can pick up exactly what the agent produced without touching the API.
This skill is free and never spends credits.
Poll get_job_status with the jobRef until status is completed, then call get_remix_result with the same jobRef; both are free. The finished script also appears in the account's Content Ideas dashboard.
Fetching is free, and you can retrieve the same remix as many times as you like. The credits were charged once when remix_post queued the job (and refunded automatically if it failed), so re-reading the finished result never adds to your bill.
Also available as a REST API endpoint.
Related topics: async job results · content pipeline integration · retrieve AI generation output · remix result retrieval