{"version":"2.1.223","anchor":"gateway-model-discovery-accepts-model-ids-that-merely-contai","canonical_anchor":"gateway-model-discovery-accepts-model-ids-that-merely-contai","heading":"Gateway model discovery accepts model ids that merely contain claude or anthropic","tier":"notice","area":"Model Discovery","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/gateway-model-discovery-accepts-model-ids-that-merely-contai","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Gateway model discovery accepts model ids that merely contain claude or anthropic\n\nGateways whose model ids carry a vendor prefix now show up instead of an empty model list.\n\n**What**\n\nGateways that expose vendor-prefixed model ids no longer come back with an empty model list.\n\n**Details**\n\n- The filter over the gateway model list changed from an anchored-at-start match to an unanchored one, so ids such as `...\/anthropic.claude-...` now survive.\n- Previously discovery gave up with \"[gatewayDiscovery] 0 usable models after filter\".\n- Discovery requires ANTHROPIC_BASE_URL plus an auth token or header.\n\n**Evidence**\n\n`[gatewayDiscovery] 0 usable models after filter`\n\n- Area: Model Discovery\n- Names: `ANTHROPIC_BASE_URL`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}