Realoficial

Workflow	Type	Description
realoficial.projects.list-projects	Atomic	A project is one source video submitted for clipping. Projects are returned under the data key.
realoficial.renders.list-renders	Atomic	The POLL half of the render pair. There is no per-render GET: the reference client lists renders and matches on id. Each entry carries status (pending, processing, done) and download_url once finished. The download_url points at a CDN and is fetched directly, not through this API - and it can 404 briefly after status becomes done while the CDN catches up.
realoficial.shorts.list-shorts	Atomic	Returns the clips (cortes) the AI produced for a project. Observed response nesting is data.data, so callers must unwrap twice. Sorting by score surfaces the highest-rated clips first.
realoficial.shorts.render-short	Atomic	Submits a clip for rendering and returns a render identifier on the render_id key (sometimes nested under data). This is the SUBMIT half of a submit-then-poll pair: poll listRenders to find the render and its download_url. Confirmed POST-only: a GET returns 405. Takes no request body.
realoficial.user.get-user	Atomic	Confirmed to exist by live probing (403 when plan-gated rather than 404). Its response shape is unverified - the reference client does not call it.