models.dev
ActiveAn AI agent for models.dev. It works in a scene with a live connection to models.dev. It asks before it writes, and every run is traced.
Access the models.dev catalog — provider metadata (API URLs, env vars, SDK packages) plus per-model context windows, pricing, capabilities (tool_call, reasoning, attachment), modalities, and release dates. Use to pick a model that fits a job's constraints, or to keep an internal model registry in sync with upstream.
What you can connect
Add these to your scene and AI gets access.
Public models.dev catalog access
An LLM provider entry from the models.dev catalog
An LLM model entry from the models.dev catalog
Connect models.dev over MCP
Daslab is itself an MCP server.
Connect models.dev in a scene, then pin that scene's URL in Claude Code, Cursor, or any MCP client. The agent there gets your models.dev tools, and your approval gate and trace travel with them.
https://daslab.run/mcp/<your-world>/<your-scene>One scene can hold models.dev and everything else you connect, so a single endpoint carries them all. Set up a client.
Use cases
- Find the cheapest model that supports tool calls and 200k context
- Look up pricing for a specific provider/model
- Enumerate every model a provider offers
From models.dev
Similar integrations
Others in Developer Tools.
Ready to try models.dev with Daslab?
Get started with CLI