Submit a system

Spotted a system the catalog is missing? Fill this form and we'll open a pre-filled GitHub Issue with your submission. A curator will verify and slot it into the next ingestion round.

No login required for the form itself — but the final step opens a GitHub Issue, so you'll need a GitHub account to actually post it. Nothing is stored server-side; the form lives in your browser until you click "Open issue".

Identity

Canonical project / vendor URL.

Placement

If none fit, choose "other / new section" and explain in the subsection / notes.
Optional. Free text.
Optional. The curator will re-tier if needed — tier is a classification, not a quality score.

Description

~140 chars target; 240 hard cap.
Optional. Longer free text is fine.

Signals

Cost (Phase 2)

Optional. The research bot scrapes the vendor pricing page when the pricing model is "hosted-api" or "hosted-service" and these are blank. If you already know the numbers, fill them in — submitter values are never overwritten.

Tells the bot whether to scrape a vendor pricing page. OSS / academic systems usually have no per-token price.

Capability (Phase 2)

Optional. Paste benchmark sources — URLs to MMLU / HumanEval / memory-eval leaderboards, ideally with the relevant score. The bot HEAD-checks each URL and pulls one score; absent submission means the bot guesses a capability band marked unverified.

One source per line is easiest for the bot to parse. URLs with scores beat URLs alone.

Use-case (Phase 2)

Pick the use-cases this system is built for. The bot may add additional tags from the same controlled vocabulary, but will never remove your selections.

Use-case tags
Use only if the eight tags above genuinely don't cover the system's intended use-case.

Submitter notes