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

How to add a new model provider with a wire capture with Opengrok

Probe a provider's API, attach the capture to a pull request, and pass the repo's contract tests.

Reverse engineering. Probing a provider's live API to record its wire behavior is a form of reverse engineering, so only probe services you are allowed to test.

Who it is forA contributor who wants to add a provider not yet in the repo, triggered by needing a model that Opengrok does not support today.

The problemA provider mapped without evidence can silently ignore thinking or effort settings, so the repo requires a capture before any map is merged.

The outcomeA verified wire map for the new provider, backed by a capture and passing both provider-map contract suites.

What you need first

  • A working Grok Bot desktop install
  • Python 3.9+ and Node 18+
  • API keys for each provider you plan to bind

Steps

  1. Run python tools/wire-probe.py --base https://api.example.com/v1 --model their-model --key-env THEIR_API_KEY against the provider.
  2. Read CONTRIBUTING.md for the contract and attach the capture to your pull request.
  3. Run node tools/test-provider-maps.cjs for Contract A.
  4. Run node tools/test-provider-maps-hop.cjs for Contract B.
  5. Run python tools/qa.py for the leak scan, reference integrity, and suites.

Prompt for your agent

Using the OnlyTerp/opengrok repo, run `python tools/wire-probe.py` against <provider-base-url> with model <model-id> and key from the environment variable <KEY_ENV_NAME>. Report the verdict and the path of the saved capture. Verify both `node tools/test-provider-maps.cjs` and `node tools/test-provider-maps-hop.cjs` pass before reporting the map as ready.

Caveat. The README says a provider is only listed as working after its capture is in the repo, so a new provider with no capture is not a supported route.

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