[Owaid0723666]

This is a self-submission: I run onomeo, and this PR comes from the site owner's account.

Summary

• Adds onomeo (https://onomeo.com), a small, solo-run OpenAI-compatible API-key gateway: https://onomeo.com/v1, Bearer auth, default executor, passthroughModels: true with live discovery from /v1/models. Same registry shape as EURouter (feat(providers): add EURouter as an OpenAI-compatible gateway #13025) and ainetcafe (feat(providers): add ainetcafe as an OpenAI-compatible provider #13862).
• onomeo routes each model to a third-party upstream, so it is added to AGGREGATOR_PROVIDER_IDS (the EURouter call, not the GreenPT one), and the apiHint says some upstreams may train on prompts. Each model page (https://onomeo.com/models/<id>) states it per model.
• onomeo is in public beta. Not every feature is guaranteed to work, and we are actively collecting user feedback; it is welcome at https://onomeo.com/feedback. The apiHint says this too.

The free allowance, stated as it is

hasFree: true, with a freeNote that says what a new account gets.

Site change on 2026-10-06: onomeo removed its site credits and its daily check-in. What the site offers today:

• Sign in with an email code, Google or GitHub. No card needed.
• About 30 free models (DeepSeek, GLM, Gemini, Qwen, Mistral and others) are counted by calls: 30 calls per 5 hours per account and 12 requests/min per key, plus a site-wide pool shared by all accounts.
• Claude, GPT and other big models and a DeepSeek coding line are paid. They are charged by usage from a US-dollar balance, at per-model prices listed at https://onomeo.com/models#pricing. During the beta an account can use at most $0.50 a day on the big models.
• Paid option: topping up is optional and starts at $5, by card or PayPal. The balance does not expire and nothing renews automatically; for 35 days after a payment the free-model limit is 90 calls per 5 hours. Nothing in this PR depends on it.

Not yet updated in this branch: the freeNote string, the comment above it, the changelog fragment and the test that pins the note's wording (check in daily, 60 requests per 5 hours per account) still describe the old check-in. They have to change together, and the branch also conflicts with release/v3.8.52, so the code is left as it is for now and only this description is corrected.

Sources: https://onomeo.com/models and the public config at https://onomeo.com/api/info (field rate), checked 2026-10-06.

Related Issues

• None.

Validation

• Change type: provider
• Focused tests when opened: onomeo-provider, providers-constants-split, provider-node-reserved-prefix, provider-translate-path-golden, removed-providers-blocklist, canonical-provider-order, discontinued-providers-2026, provider-alias-uniqueness, openvecta-provider-registration, kimi-partner-aff-links, greenpt-provider, eurouter-provider: 90/90 pass (Node 24.14, Windows)
• eslint and prettier --check on every touched file: clean when opened
• check:file-size, check:provider-consistency (bun), check:provider-order-sync, check:provider-assets, check:docs-sync, check:changelog-integrity, check:any-budget:t11: pass when opened
• Production-code change includes a new test

Not done: a live chat or streaming call through OmniRoute. No API key is used or committed here, so, as in #13025, nothing about streaming or tool calls is declared in the entry (supportsTools / supportsVision / capabilities stay unset, and a test pins that). GET /v1/models returns 401 with no key or a bad key, so the endpoint does need auth.

Tests Added Or Updated

• tests/unit/onomeo-provider.test.ts (new, 7 tests)
• tests/unit/providers-constants-split.test.ts: APIKEY count 242 -> 243
• tests/unit/provider-node-reserved-prefix.test.ts: reserved prefixes 413 -> 414 (id == alias, one member)
• tests/snapshots/provider/translate-path.json: regenerated with UPDATE_GOLDEN=1; the only change is the new onomeo block

Coverage Notes

• The new registry module and the gateway entry are covered by tests/unit/onomeo-provider.test.ts (registry shape, endpoint, executor, passthrough validation, aggregator membership, free note and hint content, no unverified capability flags).

Reviewer Notes

• config/quality/file-size-baseline.json: gateways.ts 1520 -> 1541 for this one declarative entry, with a _rebaseline_ note (same as the ainetcafe PR).
• Changelog fragment: changelog.d/features/14297-onomeo-provider.md.
• Refresh (2026-09-26): only the freeNote, apiHint, their comments and the changelog fragment changed, to the numbers the site had at the time and the public beta note. The entry keeps the same line count, and the phrases the test pins are unchanged. The branch has not been rebased, since the PR is parked for v3.8.52; the counts in the two count tests and the file-size baseline will need a re-measure on whichever release branch it lands on.

🤖 Generated with Claude Code

[Owaid0723666]

Refreshed on 2026-09-26: the onomeo freeNote, apiHint and changelog fragment now carry the current credit numbers (the daily check-in is 50,000 credits on day 1, up to 200,000/day from day 7; they were 1,200 -> 3,500) and a public beta note. The entry keeps the same line count and the phrases the test checks. I left the branch as it is since this is parked for v3.8.52, and can rebase onto whichever release branch it ends up on.

[Owaid0723666]

Merged the latest release/v3.8.51 into this branch to resolve the conflicts (file-size baseline, reserved-prefix count 413, apikey count 242). The onomeo freeNote, comment and changelog fragment now use today's numbers from onomeo.com: check-in 20,000 on day 1 up to 50,000/day from day 7, 36 free models (60 requests per 5 hours per account), 12 premium models capped at 50,000/day for unpaid accounts, $5/month for 3,000,000 credits. Nothing else changed.

[diegosouzapw]

Re-homed to release/v3.8.52: v3.8.51 entered its release freeze, so the branch now belongs to the release captain and development continues on the next cycle. Nothing is wrong with this PR — it just needed a live base. No action needed from you; CI will re-run against the new base.