fix: resolve the 9 broken links reported by mintlify broken-links

[eastagiletracker]

This PR proposes fixing the 9 broken links that mintlify broken-links reports on main, every one of which is a live 404 on docs.modelslab.com today. We include this PR work along with a full history of your repo at https://eastagiletracker.com/projects/495. You can sign in with your GitHub ID to claim ownership of the project.

What is broken

Running the check your README documents, on main at 54c5bc1:

$ npx mintlify broken-links
found 9 broken links in 7 files

agents-api/overview.mdx
 ⎿  /agents-api/training
 ⎿  /agents-api/servers
 ⎿  /agents-api/uploads

error-codes.mdx
 ⎿  /general-api/fetch-image

image-editing/overview.mdx
 ⎿  /image-generation/flux_kontext/flux-kontext-img-to-image

image-generation/flux/flux-text-to-image.mdx
 ⎿  /image-generation/flux/flux-img2img

image-generation/overview.mdx
 ⎿  /image-generation/nanobanana-lite-pretrained/overview

release-notes/overview.mdx
 ⎿  /release-notes/playground

video-api/video-to-video.mdx
 ⎿  /images/video-api/assets/images/Image-to-video-06907dcc4363b727c589be0243af41f4.jpg

This is not local-only link rot. Each of the nine targets returns 404 on docs.modelslab.com right now, while all seven host pages return 200 — so a reader lands on a real page and clicks through to nothing. Six of the nine sit on overview and release-notes landing pages, which is the top of the navigation funnel.

What changed

Four links whose target moved or was misaddressed — retargeted. Every replacement was checked against the deployed site and returns 200.

• image-editing/overview.mdx — the Flux Kontext Dev card pointed into image-generation/flux_kontext/; the page actually lives at /image-editing/flux-kontext-img-to-image.
• video-api/video-to-video.mdx — 2cfc173 ("feat: images") renamed the video-api example images and updated video-api/overview.mdx and video-api/scene-maker.mdx, but this page kept the pre-rename filename. It now points at Image_to_video_modelslab.jpg, which is the same asset under its new name, so the page renders exactly as it did before that commit.
• error-codes.mdx — the "Processing Status vs Errors" section linked /general-api/fetch-image, which has never existed. It now points at the community-models fetch page, the same target image-generation/flux/flux-text-to-image.mdx already uses for "Retrieve results for processing requests".
• image-generation/flux/flux-text-to-image.mdx — the "Image to Image" related-endpoint card pointed at a FLUX-specific img2img page that has never existed; image-generation/flux/openapi.json documents only /text2img. FLUX image-to-image runs through the shared /api/v6/images/img2img endpoint, so the card now points at the community-models Image to Image page, whose own public-model list already includes the flux-1-d base model. This is the one judgement call in the diff, and it is a one-line change if you would rather it went somewhere else.

Five cards whose target was removed or never written — dropped, so the navigation stops promising a page that 404s.

• image-generation/overview.mdx — the NanoBanana Lite card. 0d0212c ("Remove shared server nano banana docs") deleted that page set; the remaining nano banana docs are the dedicated-server ones under enterprise-api/, which is a different tier, so I did not repoint the public card at them.
• release-notes/overview.mdx — the Playground card. release-notes/playground.mdx was removed in 88ffeb5 / 64956b8 and has no replacement in the repo.
• agents-api/overview.mdx — the Training, Servers and Uploads cards. These are not all the same case, and the difference is worth flagging: agents-openapi.json exposes no training paths and no server paths at all, so those two groups have nothing behind them, but Uploads is real — POST /files/upload and POST /files/base64, with the files:write scope already documented in your Token Scopes table. That card can come straight back the moment a page for it lands. I left it out rather than write one, because the published spec declares no request body for either route and I did not want to guess at the payload.

Verification

Same command, same tree, on this branch:

$ npx mintlify broken-links
success no broken links found

The before state is the 9-link report above and the after state is clean, so the check that fails on main passes here. The diff is 5 insertions and 20 deletions across 7 .mdx files — no docs.json, no OpenAPI spec, no asset, and no prose rewritten beyond one card description that would otherwise have promised a FLUX-only endpoint.

How this was managed

This work was tracked as a single story, Fix the 9 broken links reported by mintlify broken-links, on a board imported from this repo's own issues and pull requests — 119 stories in all — at https://eastagiletracker.com/projects/495.

If you'd rather not receive contributions like this, reply no-more-prs on this pull request and we won't open any further ones on your repositories.

---

Lawrence W. Sinclair
CEO / East Agile
linkedin.com/in/lwsinclair/
eastagile.com

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}