anomalyco / anomalyco/models.dev

Add a citations capability to the model schema

Open
#5,625 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
6.9k
Forks
1.7k
Avg merge
3h 21m
Merged PRs (30d)
873

Description

Problem

The schema can represent attachments, reasoning, tool calls, structured output, temperature, and modalities, but it cannot say whether a model returns source citations.

This is a model/API capability, not just a UI label. Consumers need it to decide whether citation options are valid and whether citation-bearing response fields should be expected.

Concrete examples

RubyLLM previously maintained local model-ID rules for this fact. During an audit we removed those rules because broad family matching becomes stale and can assign unrelated metadata to new snapshots. There is currently no models.dev field to replace the citation facts.

Suggested shape

A top-level optional boolean would match the existing capability fields:

citations = true

It should be allowed in model metadata and provider overrides because citation support can depend on the serving API, not only the underlying model.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Locate the existing top-level capability fields in the model metadata schema and the provider override definitions. Follow how a boolean capability is validated and represented, then add citations support for both locations and verify that model metadata and provider overrides accept the suggested citations = true shape.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
ai, api
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
66/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.