Exact Web Answer Agent (AMD AI League Match 4)

Match 4 entry: an agent that reads a natural-language request, navigates the given website (or a saved copy of it) and returns the one specific value the user asked for, with the page it came from. Not a summary and not a list of links. Match 4 image: docker.io/driedsandwich/amd-ai-league:m4-v1 How it works. Each request runs as a fresh python3 /app/app.py process with a 24-second internal deadline. It writes a well-formed placeholder JSON first, then fetches the start page with short timeouts, follows the same-site links whose text best matches the question, cleans each page to text (tables kept as rows) and ranks passages. A Qwen3-4B-Instruct model, loaded once at container start and kept resident on the AMD GPU behind a unix socket, picks the value from the top passages and names the supporting page. A rule-based extractor for prices, dates, versions, numbers and contacts is the fallback when the model has no time left. The answer is the value only; if the pages do not contain it, the agent returns an empty answer instead of guessing. Output: /app/output/<query-id>_output.json with answer, citations (source URLs, or corpus-relative paths when pages are given as a folder), sources, source_url and confidence. Because the detailed Match 4 harness was not published, the image follows the container contract shared by the earlier Matches: the mandated ROCm PyTorch base image, weights shipped inside the image, no downloads at start-up, and the model placed on the GPU explicitly. The script accepts several argument spellings (--query or --question, --query-id or --id, --url, --corpus for saved pages, --index, --input). No API keys; inference runs locally on the AMD GPU. Match 3 and Match 2 images are given in their Mini Challenge fields (docker.io/driedsandwich/amd-ai-league:mc3-v1 and docker.io/driedsandwich/amd-ai-league:mc2-v2).