Official2026-07-02

DeepSeek's current API reference exposes dedicated `/models` and `/user/balance` endpoints, making V4 model discovery and account-budget checks easier to verify from first-party docs

Checked on July 2, 2026: DeepSeek's official API reference documents a `GET /models` endpoint that currently examples only `deepseek-v4-flash` and `deepseek-v4-pro`, plus a `GET /user/balance` endpoint with `is_available`, currency, granted balance, and topped-up balance fields for direct budget checks.

Accepted official-source monitoring note

Today's publish-safe item stays DeepSeek-first and uses backup official documentation because the live @deepseek_ai X timeline still was not safely readable in this run. DeepSeek's English homepage still anchors the official X account, but the current first-party API reference exposes a clearer fresh support signal for developers who need to verify what the API itself can tell them about live model IDs and remaining balance.

What we verified on July 2, 2026

  • DeepSeek's official GET /models reference says the endpoint lists currently available models and its example response currently shows deepseek-v4-flash and deepseek-v4-pro owned by deepseek.
  • The same page tells readers to check Models & Pricing for supported models, which means the model-list endpoint is a runtime discovery surface, while the pricing page remains the public contract for rates and support framing.
  • DeepSeek's official GET /user/balance reference exposes a direct account-budget check with is_available plus balance_infos entries for currency, total_balance, granted_balance, and topped_up_balance.
  • The balance example currently documents CNY and USD as the possible currency values, which matters for teams reconciling promotional credits versus paid top-ups.
  • This is developer-account infrastructure guidance, not storefront inventory guidance: it does not create any new /pricing card, stock promise, or plan migration in this repo.

Why this is publishable

This is a current first-party API contract check from official DeepSeek docs, not a community wrapper, screenshot, or repost.

  1. It answers two practical support questions that appear together in real setups: which DeepSeek models are live right now, and whether the account still has usable balance.
  2. It stays inside official facts and avoids inventing unsupported billing behavior, quota semantics, or inventory claims.
  3. It is distinct from the July 1 pricing-permanence item because the story here is runtime discovery and account verification, not price cuts.
  4. It gives today's two long-tail guide pages a clean first-party source cluster instead of forcing another migration or pricing recap into the news slot.

Why this matters for DeepSeek-first SEO pages

  • Support pages can target DeepSeek list models API intent with official schema instead of copied SDK snippets.
  • Budget pages can answer DeepSeek user balance API searches with the exact official response fields rather than generic console screenshots.
  • Teams migrating old aliases can verify whether their app should trust static model strings or ask the live API what it supports today.

Rejected candidates today

  • Official X timeline as the primary source: rejected for this run because the homepage still anchored DeepSeek's X presence, but the direct timeline remained unreadable here.
  • The homepage V4 Preview anchor: official, but older and already overrepresented in existing coverage.
  • The official pricing page: still current and checked, but weaker than the API-reference pair for today's single news slot because July 1 already covered pricing as the headline.
  • The official status page: checked and healthy, but not stronger than model discovery plus balance introspection as a developer-facing update.
  • Official GitHub and Hugging Face surfaces: checked as backup official sources, but neither exposed a clearer DeepSeek API support headline than the docs pair used here.

Editorial takeaway

The clearest official DeepSeek developer signal today is that the public API reference is not only for chat calls anymore in practice: it also gives teams a documented way to check live model names and account balance programmatically. That is a better first-party headline for July 2 than recycling yesterday's pricing story or forcing an unreadable X surface into the publish slot.

Sources checked

View original source