Segmind Release Notes (May 19–25, 2026)

1. New Observability Dashboard — API Health & Cost Analytics

What's new: A new Observability section is live on platform.segmind.com. It includes two dashboards: API Health (/api-health) showing real-time p50/p95/p99 latency, error breakdown by category, and recent failure history; and Cost Analytics (/cost-analytics) showing consolidated spend across all models, projections, and a CSV export for your records.
Impact: You can now monitor how your API usage is performing and track spending — all in one place, without any additional calls. Existing bookmarks to /usage or /metrics automatically redirect to the new Cost Analytics page.
Released: May 24–26, 2026

What's new: Team account Owners and Admins can now query per-member spending via GET /inference-request/team-usage-summary. Supports grouping by user, model, or user_model, filterable by date range.
Impact: If your team shares a wallet, you can now see exactly who is spending what and on which models — useful for internal cost tracking and quota management. Member-role API keys receive a 403 by design.
Released: May 23, 2026

What's new: Veo 2, Veo 3, Veo 3.1, Veo 3.1-fast, Veo 3.1-lite, Lyria 2, and Imagen-backed models now return meaningful HTTP status codes for client-side errors — 400 for invalid inputs, 403 for access issues, 429 for rate limits, and so on.
Impact: Debugging failed requests is now much easier. If the model returns a 400 with a clear message (e.g. "Provided image is not valid"), that's a signal about your input — not a platform outage. Previously these showed up as generic 500 errors.
Released: May 26, 2026

What's new: GPT-5.5 (/v2/gpt-5.5) and Gemini 2.5 Flash (/v2/gemini-2.5-flash) now accept a bare {"prompt": "your text"} body in addition to the full messages array format.
Impact: Simpler integrations just work out of the box. If you were hitting 400 or 406 errors using the prompt shorthand this week, those are fully resolved — no changes needed on your end.
Released: May 27, 2026

What's new: Auto-recharge billing now processes with multi-layer safeguards to prevent duplicate charges.
Impact: Wallet top-ups are reliable. If you experienced unexpected duplicate charges around May 23, those were a temporary issue that has been fully resolved. No action is required from your side — reach out to support if you'd like a review of your billing history from that window.
Released: May 27, 2026