find-models

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Docs

文档

Search

搜索

  • Use the search API (
    GET /v1/search?query=...
    ) to find models by task. Returns models, collections, and docs.
  • Search returns metadata for each model including
    tags
    ,
    generated_description
    , and
    run_count
    .
  • The search API also returns matching collections alongside model results.
  • Avoid listing all models via API. It's a firehose. Use targeted queries.
  • 使用搜索API(
    GET /v1/search?query=...
    )按任务查找模型。返回结果包含模型、合集和文档。
  • 搜索结果会返回每个模型的元数据,包括
    tags
    generated_description
    run_count
  • 搜索API还会在模型结果旁返回匹配的合集。
  • 避免通过API列出所有模型,数据量过大。请使用针对性查询。

Collections

合集

  • Collections are curated groups of models maintained by Replicate staff.
  • The
    official
    collection contains always-warm models with stable APIs and predictable pricing.
  • Use collections to narrow a shortlist before deep comparison.
  • List collections with
    GET /v1/collections
    . Get one by slug with
    GET /v1/collections/{slug}
    .
  • 合集是由Replicate团队维护的精选模型组。
  • official
    合集包含始终处于就绪状态的模型,这些模型拥有稳定的API和可预测的定价。
  • 可以利用合集缩小候选范围,再进行深度对比。
  • 使用
    GET /v1/collections
    列出所有合集,使用
    GET /v1/collections/{slug}
    通过别名获取单个合集。

Reading model schemas

读取模型架构

  • Every model exposes its input/output schema via the models API (
    GET /v1/models/{owner}/{name}
    ).
  • Schema path:
    model.latest_version.openapi_schema.components.schemas.Input.properties
  • Each property may include:
    type
    ,
    description
    ,
    default
    ,
    minimum
    /
    maximum
    ,
    enum
    ,
    format
    (e.g.
    uri
    for file inputs).
  • Always fetch the schema before running a model. Schemas change.
  • 每个模型都会通过模型API(
    GET /v1/models/{owner}/{name}
    )暴露其输入/输出架构。
  • 架构路径:
    model.latest_version.openapi_schema.components.schemas.Input.properties
  • 每个属性可能包含:
    type
    description
    default
    minimum
    /
    maximum
    enum
    format
    (例如,文件输入的
    uri
    格式)。
  • 在运行模型前务必获取最新架构,架构可能会发生变化。

Picking the right model

选择合适的模型

  • Prefer official models. They're always warm (no cold boot), have stable APIs, and predictable pricing.
  • Prefer the latest version. If search returns v2.5 and v3.0, use v3.
  • Run count can be misleading. Old models accumulate runs over time but may be outdated. A model with 10M runs from 2023 is likely worse than a model with 100K runs from 2025.
  • Prefer recently released models. The AI space moves fast.
  • Check model tags to help filter by task (
    image-generation
    ,
    video
    ,
    audio
    , etc.).
  • 优先选择官方模型。这些模型始终处于就绪状态(无需冷启动),拥有稳定的API和可预测的定价。
  • 优先选择最新版本。如果搜索结果包含v2.5和v3.0,请使用v3版本。
  • 运行次数可能具有误导性。旧模型的运行次数会随时间累积,但可能已过时。一个2023年获得1000万次运行的模型可能不如2025年获得10万次运行的模型。
  • 优先选择近期发布的模型。AI领域发展迅速。
  • 查看模型标签以按任务筛选(如
    image-generation
    video
    audio
    等)。

Model identifiers

模型标识符

  • Official models use
    owner/name
    format (e.g.
    black-forest-labs/flux-2-klein-9b
    ). Routes to the latest version automatically.
  • Community models require
    owner/name:version_id
    . You must pin a specific version. Community models can cold-boot and take time to start.
  • If you must use a community model, be aware that it can take a long time to boot. You can create always-on deployments, but you pay for model uptime.
  • 官方模型使用
    owner/name
    格式(例如
    black-forest-labs/flux-2-klein-9b
    ),会自动指向最新版本。
  • 社区模型需要使用
    owner/name:version_id
    格式,必须固定特定版本。社区模型可能需要冷启动,启动耗时较长。
  • 如果必须使用社区模型,请注意其启动可能需要很长时间。你可以创建始终在线的部署,但需为模型运行时间付费。