Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add LLMTR to the free-provider directory

Open
  • Is something wrong?
#7,954 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

@knowhycodata is already working on this.

Since Oct 29, 2026.

  • #7955 by @knowhycodata — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
28/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
ai, backend

Research direction

Read the existing Runcrate directory entry and its focused test, referenced as #7726, then inspect the provider adapter directory and its tests. Add an LLMTR directory row with the stated base URL, docs and key links, and the six listed zero-price chat models; preserve live discovery for other models. Done means the row and test cover the requested catalog behavior. The author says a small PR is ready, so check for that work before starting.

Written by the indexing model from the issue text.

Description

enhancement provider
Area

Provider adapters

What are you trying to accomplish?

Route Codex traffic through LLMTR, an OpenAI-compatible gateway at https://llmtr.com/v1. Disclosure: I maintain LLMTR (Knowhy, Istanbul). Chat uses Authorization: Bearer with a key starting with llmtr-; GET /v1/models is public.

What prevents this today?

opencodex has no LLMTR row. A custom OpenAI-compatible provider works, but each user has to look up the base URL, the key dashboard, and which models are actually free.

What should OpenCodex do?

List LLMTR in the free-provider directory, the same way Runcrate landed in #7726: base URL https://llmtr.com/v1, docs https://llmtr.com/docs/gateway/chat-completions/, keys at https://llmtr.com/dashboard/api-keys. Seed the standing zero-price chat models and keep live discovery for the rest of the catalog.

As of 2026-10-29, GET /v1/models returns 382 rows. These six chat ids have a zero list price with no end date:

  • qwen/qwen3.8-27b-free, nvidia/nemotron-3-ultra-550b-a55b, nvidia/nemotron-3.5-super-vl-free (daily quota)
  • openai/gpt-oss-safeguard-20b, agnes/agnes-2.5-flash, agnes/agnes-3.0-flash

A key is still required. Other zero-price rows are dated promotions or bring-your-own-key routes; everything else is paid, including llmtr/qwen3-8-27b. Pricing: https://llmtr.com/pricing. Where a model accepts reasoning, the field is a boolean.

This should be a directory row, not a canonical preset: most of the catalog is paid and LLMTR routes third-party models.

Example usage or interface
ocx provider add llmtr --adapter openai-chat --base-url https://llmtr.com/v1 \
  --auth-mode key --default-model qwen/qwen3.8-27b-free --set-default
printf '%s' "$LLMTR_API_KEY" | ocx account add-key llmtr
curl -sS http://127.0.0.1:10100/v1/chat/completions -H 'Content-Type: application/json' \
  -d '{"model":"qwen/qwen3.8-27b-free","messages":[{"role":"user","content":"Say hi in one word."}]}'
Alternatives or workarounds

A hand-written OpenAI-compatible provider with the same base URL.

Additional context

I couldn't find an existing LLMTR issue. I have a small PR ready against dev that adds the row and a focused test, and will link it here.

Checks
  • I searched existing issues and documentation.
  • This request describes a concrete OpenCodex workflow rather than merely naming a desired technology.
  • I removed secrets and personal data.
Dominant language
TypeScript
Stars
16.9k
Forks
1.3k
Avg merge
16h 42m
Merged PRs (30d)
695

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lidge-jun/opencodex

All issues in lidge-jun/opencodex

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.