Skip to content
System One

Submit an example

The form below is the whole process: say what you are sending, fill in what you know, and send it.

What are you sending?

Publish or last-push date, as YYYY-MM-DD.

0 / 400

What it does and what is notable. One or two factual sentences.

Use cases

Optional. Tick the jobs this covers.

Workflow control

Retrieval and knowledge

Safety and quality

Data and operations

Real-time and agents

Primitives

Optional. Only tick what it actually uses.

Comma separated, e.g. python, typescript.

Comma separated slugs.

Your relationship to it

Optional. Anything the listing should get right.

Only used to reply about this submission.

What gets listed

  • Projects: anything you built that calls a System One model.
  • Tools: SDKs, wrappers, MCP servers, framework providers, CLIs, workflow nodes.
  • Cookbooks: official worked examples and documented patterns.
  • Videos: walkthroughs and explainers, in any language.
  • Articles: write-ups, reviews, benchmarks, comparisons.
  • Discussions: threads worth reading, including critical ones.
  • Lists: awesome lists and roundups.
  • Alternatives: open-source models and libraries that cover similar ground.
  • New System One models from any vendor.

What gets skipped

  • Anything behind a paywall or a login.
  • Anything without a public link, including private repositories and internal demos.
  • Pure marketing with no technical substance to point at.
  • Duplicates. URLs are normalised before they are added, so the same link submitted twice lands once.

What happens next

Entries are added most days. Every submission is opened and written up in one or two factual sentences, so your description will probably be edited for length and neutrality. An entry is marked verified only once someone here has opened the link and checked it matches that summary. Nothing is listed sight unseen.

There is no acceptance email and no queue you can watch. If a week goes by and your link has not appeared, send it again through the form and say it is a second attempt.

Listing a new model

A new System One model from any vendor gets its own page. Pick List a new System One model above and the form asks for the minimum needed to write one honestly:

  • Model name and the version string the API accepts.
  • Vendor name and website.
  • The announcement URL, which is what every claim gets sourced against.
  • The primitives or output types it returns, and whether the answers carry calibrated probabilities.
  • Pricing, per million input and output tokens, with the page that states it.
  • API documentation URL, and the SDK packages if any exist.

Latency figures, context limits and rate limits are listed too when the docs state them, attributed to the vendor rather than presented as measured. If a number only appears in a launch post, the page says so.