ByteDance Seed: Seed 1.6status active → deprecatedsource
What it means The OpenRouter row for bytedance-seed/seed-1.6 gained an expiration_date of 2026-11-11 in the snapshot fetched 2026-09-23T23:47:07Z (it was null in the 2026-09-21T12:20:00Z one, with pricing, context length and created unchanged), so the registry's expiration-date rule (absent -> active, within 365 days -> deprecated, in the past -> retired) derives deprecated — a genuine removal notice, set in the same fetch on all three of bytedance-seed/seed-1.6, bytedance-seed/seed-1.6-flash and bytedance-seed/seed-2.0-code and still held in the 2026-09-24T12:05:12Z snapshot. It matters as a migration cue rather than an outage: the row was still listed as of that 2026-09-24 snapshot, but OpenRouter's model schema defines expiration_date as the date after which the model may be removed, so listing through 2026-11-11 is not guaranteed and removal may follow that date; if the row is still present once the date is past, the same rule derives retired. Meanwhile bytedance-seed/seed-2.0-lite, bytedance-seed/seed-2.0-mini and bytedance-seed/seed-2-1-turbo carry a null expiration_date in that 2026-09-24 snapshot — though the feed declares none of them a successor.