[Marketen]

Summary

GET /v1/models describes each model's capabilities in one field, capabilities: what the operator states the model accepts, published exactly as stored. The field names follow models.dev:

"capabilities": {
  "modalities": { "input": ["text", "image"], "output": ["text"] },
  "tool_call": true,
  "structured_output": true,
  "reasoning": true,
  "reasoning_options": [{ "type": "effort", "values": ["low", "high", "max"], "default": "high" }]
}

• Unknown is left out: a missing field means not stated, and a model with nothing stated has no capabilities field.
• features is removed. What it said is now in capabilities, kind (router) and proof_mode (Tinfoil attested transport).
• Gateway's model type no longer carries the five capability flags. Nothing in Gateway rejects requests because of capabilities.

Compatibility

• Clients that read features stop seeing it. The Nexus website moves to capabilities in dappnode/dappnode-nexus#145.
• Works with any Metering: with #145 the record comes from Metering; with an older Metering it is rebuilt from the flags that Metering still sends.
• New capability fields are passed through without a Gateway change.

Tests

• Unit:
  • the record is published unchanged, including a field Gateway doesn't know;
  • an empty record is left out;
  • no features list is published;
  • with older Metering, the record is rebuilt from the flags.
• End to end: Metering from #145 and this Gateway, on a database migrated to 026. Every model in /v1/models has capabilities and none has features. A model given image input and effort levels in the database shows them unchanged.

🤖 Generated with Claude Code