HunterAlphaHub
OpenRouter model reference Facts from the public catalogue, dated and labelled
Jev Laya Fable 5.2 Verified
2026-11-13

Contribute

Send us a link

A project built with Jev, a post, a video, a correction, a tip about an anonymised release, a broken page. Two fields, and the rest is there if you have more to say.

Required a link, and an email to reply to. Optional everything else.

Add context — all optional

One or two sentences about what it does, in your words. We write the entry ourselves.

Cost, latency, a benchmark — anything you measured. We attribute these to you.

We store what you type and email it to ourselves. No IP address, no user agent, no referrer — the same rule as the mailing list.

What happens next

We open the link, check that it exists and says what you said it says, and write the entry — or fix the page. If we cannot verify a number we either drop it or say in the entry that it is yours. Nothing publishes automatically, and a submission that does not make it in usually means we could not open the link.

  • Built with Jev — repositories and posts, checked before they appear.
  • Model pages — corrections go into the snapshot in lib/openrouter-models.ts with the date moved, so the page says when it was last read.
  • Anonymous releases — the register records public listings only.

The catalogue itself is synced from OpenRouter's own API rather than submitted by hand, so a model that is missing from it is a correction like any other, not a new page.

Which platforms work, and where each one lands

All of them. The platform is read off the link rather than asked of you — so a paste can mix them, and you never have to work out where a thing "belongs". What differs is only what happens next:

Platform Where it lands What we fill in
arXiv A correction on a model page A paper: read by hand.
Bluesky Threads and write-ups, or wherever it fits Bluesky answers 403 to us, so a person opens these.
dev.to Threads and write-ups The dev.to API gives reactions and reading time.
GitHub Built with Jev The GitHub API gives stars, licence and last push.
Hacker News Threads and write-ups The Algolia API gives score and comment count.
Hugging Face A correction on a model page A model card or an open release: read by hand, and often a stealth-model lead.
Lobsters Threads and write-ups, or wherever it fits Lobsters answers 400 to us, so a person opens these.
Reddit Threads and write-ups, or wherever it fits Its API is closed to us (403, and app creation is blocked), so a person opens these.
X Seen on X No affordable read API — we open the post and write the quote, media and metrics in by hand.
YouTube Videos The Data API gives title, duration and thumbnail.
Web Threads and write-ups, or wherever it fits Any other host — nothing is read for us, so a person opens it.
Source lib/data/submission-sources.json Verified 2026-09-24 Stored in D1; the notification is a summary email, at most one every fifteen minutes.

Built with Jev Seen on X Contact What we store

Send us a link

A project built with Jev, a post, a video, a correction, a tip. We open the link, check it says what you said it says, and write the entry ourselves.

Required a link, and an email to reply to. Optional everything else.

Add context — all optional

One or two sentences about what it does, in your words. We write the entry ourselves.

Cost, latency, a benchmark — anything you measured. We attribute these to you.

We store what you type and email it to ourselves. No IP address, no user agent, no referrer — the same rule as the mailing list.

What happens to what you send →