vercelpycheck

Scan pasted project files for known Vercel Python-runtime deploy footguns: conflicting requirements.txt/pyproject.toml manifests, a dependency manifest missing from the project root, sibling-module imports that need sys.path, multiple top-level ASGI apps under api/, streaming/SSE responses that can crash the Python runtime, oversized dependencies (torch/tensorflow/etc.), and unrouted .well-known/ files. Static analysis over file contents -- it doesn't run a real build, so a clean result means 'no known footgun found,' not a deploy guarantee. To scan a public GitHub repo automatically instead of pasting files, use the $29 checkout at https://www.edgethirteen.com/tools/vercelpycheck.

{'type': 'object', 'required': ['files'], 'properties': {'files': {'type': 'string', 'description': "Project files bundled as repeated '### FILE: path' markers followed by that file's content, e.g. '### FILE: requirements.txt\\nfastapi\\n### FILE: api/index.py\\n...'. Include api/*.py files plus root manifests (requirements.txt, pyproject.toml, vercel.json, uv.lock)."}}}