My FastAPI backend and Next.js frontend are up and running, yet one endpoint is still tripping us up—the payload leaves the server fine but lands in the browser with the wrong data format, so the UI misbehaves. I need a sharp eye to step into the repo, trace the request–response path, and eliminate the mismatch. What you’ll be doing • Walk through the FastAPI routes, Pydantic models, and serializers. • Inspect the Next.js side (React hooks, fetch/axios calls, state handling) to be sure data is parsed and rendered correctly. • Adjust headers, schemas, or front-end logic so the format is consistent end-to-end. • Run a quick regression test and push a clean commit or PR showing everything works smoothly. Acceptance criteria – API responses arrive in the browser exactly as defined. – Related UI components render without console errors or broken state. – No new lint/test failures introduced. It’s a compact task with a fixed $50 payout and should be straightforward for someone who has untangled FastAPI ↔ Next.js issues before. When you reply, just highlight relevant experience; that’s all I need to choose quickly. Deliver on this and there’s plenty more work in the pipeline.