|
| 1 | +--- |
| 2 | +name: find-models |
| 3 | +description: Find AI models on Replicate using search and curated collections. |
| 4 | +--- |
| 5 | + |
| 6 | +## Docs |
| 7 | + |
| 8 | +- Reference: <https://replicate.com/docs/llms.txt> |
| 9 | +- OpenAPI schema: <https://api.replicate.com/openapi.json> |
| 10 | +- MCP server: <https://mcp.replicate.com> |
| 11 | +- Per-model docs: `https://replicate.com/{owner}/{model}/llms.txt` |
| 12 | +- Set `Accept: text/markdown` when requesting docs pages for Markdown responses. |
| 13 | + |
| 14 | +## Search |
| 15 | + |
| 16 | +- Use the search API (`GET /v1/search?query=...`) to find models by task. Returns models, collections, and docs. |
| 17 | +- Search returns metadata for each model including `tags`, `generated_description`, and `run_count`. |
| 18 | +- The search API also returns matching collections alongside model results. |
| 19 | +- Avoid listing all models via API. It's a firehose. Use targeted queries. |
| 20 | + |
| 21 | +## Collections |
| 22 | + |
| 23 | +- Collections are curated groups of models maintained by Replicate staff. |
| 24 | +- The `official` collection contains always-warm models with stable APIs and predictable pricing. |
| 25 | +- Use collections to narrow a shortlist before deep comparison. |
| 26 | +- List collections with `GET /v1/collections`. Get one by slug with `GET /v1/collections/{slug}`. |
| 27 | + |
| 28 | +## Reading model schemas |
| 29 | + |
| 30 | +- Every model exposes its input/output schema via the models API (`GET /v1/models/{owner}/{name}`). |
| 31 | +- Schema path: `model.latest_version.openapi_schema.components.schemas.Input.properties` |
| 32 | +- Each property may include: `type`, `description`, `default`, `minimum`/`maximum`, `enum`, `format` (e.g. `uri` for file inputs). |
| 33 | +- Always fetch the schema before running a model. Schemas change. |
| 34 | + |
| 35 | +## Picking the right model |
| 36 | + |
| 37 | +- Prefer official models. They're always warm (no cold boot), have stable APIs, and predictable pricing. |
| 38 | +- Prefer the latest version. If search returns v2.5 and v3.0, use v3. |
| 39 | +- 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. |
| 40 | +- Prefer recently released models. The AI space moves fast. |
| 41 | +- Check model tags to help filter by task (`image-generation`, `video`, `audio`, etc.). |
| 42 | + |
| 43 | +## Model identifiers |
| 44 | + |
| 45 | +- **Official models** use `owner/name` format (e.g. `black-forest-labs/flux-2-klein-9b`). Routes to the latest version automatically. |
| 46 | +- **Community models** require `owner/name:version_id`. You must pin a specific version. Community models can cold-boot and take time to start. |
| 47 | +- 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. |
0 commit comments