DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to trace which provider and policy handled a bad AI answer with Synapass

Look up a request ID to see the routing reason, policy verdict, and answering provider.

Who it is forAn engineer investigating a complaint about a wrong or slow AI answer and needing to know which model produced it.

The problemWithout a central record, it is hard to tell which model, provider, or fallback produced a specific answer.

The outcomeThe engineer gets the routing explanation for one request ID, including the provider that actually answered.

What you need first

  • Docker with Docker Compose, curl, and jq, or Go and Make for the native build
  • At least one provider API key such as OPENAI_API_KEY or ANTHROPIC_API_KEY in .env
  • A host with ports 8080 and 3000 free, or a changed GATEWAY_PORT

Steps

  1. Copy the request_id from the synapass block of the response that needs review.
  2. Run curl -s $GATEWAY/admin/v1/requests/<request_id>/explain -H "Authorization: Bearer $SYNAPASS_ADMIN_KEY". (inferred, check the README)
  3. Check the policy verdict, cache decision, and routing reason in the explain output.
  4. Compare provider with requested_model and routed_model in the original response to confirm what answered.

Prompt for your agent

In the ShadowSafin/Synapass repo, call GET /admin/v1/requests/<request_id>/explain with the admin key and summarize the routing reason and the answering provider. Verify that the summary names the same provider as the synapass.provider field in the original response.

Caveat. The explain endpoint is described in the README, but its exact response fields are not shown there, so check the output format against the documentation before you build automation on it.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page