ابو مريم on Nostr: Private Provider trying to set PP up for the first time and getting errors. my ...

Private Provider (npub1fet…jzfa)

trying to set PP up for the first time and getting errors. my clanker put this together after a few debugging attempts:

Bug report — privateprovider.xyz (Routstr node, Tinfoil upstream):

All Tinfoil chat models return 404 with x-routstr-error-scope: upstream:
POST /v1/chat/completions {"model":"tinfoil-glm-5-3-flash"}
→ 404 {"error":{"message":"Not found.","type":"invalid_request_error","code":"not_found"}}
request ids: 2d2d9dbf-d57c-4100-ad55-3ee7ff79bb23, 82a13727-9860-4e01-bd3c-04aae54a2c54

- Responses carry tinfoil-pt attestation headers, ~600ms latency — the request
reaches inference.tinfoil.sh and the enclave itself returns 404.
- Unknown model IDs are correctly rejected locally (400 invalid_model, ~2ms),
so node-side resolution is fine; the forwarded request is what's failing.
- /v1/models/paths shows model-id=tinfoil-glm-5-3-flash, but Tinfoil's native
catalog IDs are unprefixed (glm-5-3-flash). Suspect forwarded_model_id / path
mismatch, possibly from the model list sync ~Oct 15.
- My key is funded with total_requests: 0 — nothing has succeeded since top-up.
- [llama3-3-70b test: works / also 404s]

help, pls 😅
this could very well be user error too. take a look and let me know. thx!