Anything that autonomously opens PRs from research papers lives or dies on whether you believe its judgment. Being able to ask what else was on the table and why it was rejected turns the agent from an oracle into something you can argue with. Note that trigger_agent_run spends your model budget and their docs tell clients to confirm before calling it — respect that, because a dispatched fleet run is not free. Pausing revokes the key, so resuming means re-provisioning; it is a stop, not a snooze.
Remyx sits between your coding agents and production, ranking which candidate improvement is worth the engineering time. Their flagship agent, Outrider, opens draft PRs implementing recent research in your repos; this endpoint is how you drive the fleet.
- Fleet — list_agents, get_agent_activity, get_fleet_report with dispatches, drafts, merged and spend
- Inbox — get_inbox surfaces drafts to review, held discussions and health items such as an unmerged setup PR or a missing model key; dismiss_inbox_item archives one
- Diagnosis — analyze_agent_run root-causes a run from its job log with evidence and a suggested next step; list_agent_runs can include the selection audit, meaning what was considered and set aside
- Control — install_agent provisions on a repo, pause_agent revokes its key, trigger_agent_run dispatches a live run and spends model budget
- Research — search_research and get_research_asset over the index, plus account and connection tools
A scoped API key. Keys are opaque and named, carrying an explicit scope set — a call to an unscoped route is refused. Personal keys never expire; automation keys carry a fixed lifetime. Remyx stores only the hash, and the plaintext is shown once.
Paste a URL with a key — add the endpoint to your client