A DeepSeek API service for coding tools

Give your coding assistantthe context your project has earned.

Connect your coding tools. Bring what your project has learned into every new task.

Project context travels with the requestIllustrative product scene. Not a live task.

AGENTS.md

Convention

Past lesson

Payment webhooks · Idempotency
payment-service
src/billing/webhook.tsProject context attached
export async function handleWebhook(event) {
− await creditWallet(event.userId, event.amount)
+ const claimed = await claimEvent(event.id)
+ if (!claimed) return { status: 'duplicate' }
+ await creditWallet(event.userId, event.amount)
return { status: 'credited' }
}
$ pnpm test billing/webhook

Change verified

pnpm test payments

The free plan includes 1M equivalent tokens. Tool access depends on the plan below.

Illustrative example
Explore the interactive task demo

This illustrates the workflow. It is not a running task or an actual charge. Your coding tool handles editing and execution. DeepCodex supplies model access, project context and request records.

deepcodex / live workspace
fix/idempotent-webhook
+0 −0

Goal

Stop duplicate webhooks from crediting twice, add a concurrency test

src/billing/webhook.ts
1 export async function handleWebhook(event) {
2−
3+
4+
5+
6 return { status: 'credited' }
7 }
$ pnpm test billing/webhook --run
running agents… 0%
Understand6 project memoriesBudget guard on

Continue in the tools you know

Tool availability and minimum plans are shown in the setup guide.

01 / A worked example

The same task, with your project’s accumulated context.

  1. Ask in your tool

  2. Include project context

  3. Receive a reply

  4. Inspect the record

View the complete request example

Follow a payment webhook review to see how a request can use project conventions and where you can inspect the record.

  1. Send a request from your coding tool.

  2. Supply relevant, enabled conventions.

  3. Continue working in the same tool.

  4. Check context, usage and cost.

payment-serviceIllustrative example

Your request

Review the payment webhook’s idempotency handling and suggest a minimal change.

Project context relevant to this request

Convention
Wallet credits must carry an idempotency key.
Past lesson
A repeated webhook must not credit the balance twice.
Verification command
pnpm test payments

Illustrative reply using that context

Check whether claiming the event and crediting the wallet share a transaction. Return the existing result for duplicate events and add a concurrent-webhook test.

Inspect the request record

Context entries
3
Equivalent tokens
4.2K
Cost
¥0.24

This illustrates the workflow. It is not a running task or an actual charge.

Explore project context

02 / Maintain project knowledge

Keep the knowledge. Move the work forward.

Project conventions, past decisions and request records form one continuous workflow.

Inspect the sourceChoose what takes effectAdjust the scope
Explore project context
Project profilepayment-service
stack.mdStack
AGENTS.mdConvention
decisions.mdPast lesson
CandidateEnabledDisabled
Illustrative product scene. Not a live task.
Explore project memory and controls

Inspect the source

Follow a project, task or request back to its original record.

Candidate · Check the source of a newly extracted lesson.

Choose what takes effect

Review candidate memories and retain useful conventions.

Enabled · Relevant requests can use the convention.

Adjust the scope

Disable an entry or turn off context injection for a project.

Disabled · Retire an outdated rule from future context.

03 / Connect your tools

Choose your tool. Check what it needs.

SDK / curl
Availability
Supported
Minimum plan
免费版
Connect SDK / curlRead the setup guide

Configuration example

SDK / curl
curl https://www.deepcodex.cn/v1/chat/completions \
  -H "Authorization: Bearer dck_xxx" \
  -H "Content-Type: application/json" \
  -d '{"model":"deepseek-v4.1-flash","messages":[{"role":"user","content":"Review this code"}]}'

Replace dck_xxx with your API key. Keep keys out of your repository.

  1. 01Register and verify your identity
  2. 02Create a key and copy the configuration
  3. 03Send a request and verify it in setup

04 / Plans and usage

Choose a plan for your tools and workload.

  • 免费版

    Price: CN¥0

    / 30 days

    1M

    Equivalent tokens

    Tools

    SDK / curl

    Plan details
  • 入门版

    Price: CN¥0.01

    / 30 days

    20M

    Equivalent tokens

    Tools

    SDK / curl

    Plan details
  • 专业版

    Price: CN¥99

    / 30 days

    100M

    Equivalent tokens

    Tools

    SDK / curl / Cursor (limited)

    Plan details
  • Pro Plus

    Price: CN¥199

    / 30 days

    250M

    Equivalent tokens

    Tools

    SDK / curl / Cursor (limited) / Claude Code / Codex CLI

    Plan details
  • Pro Max

    Price: CN¥599

    / 30 days

    800M

    Equivalent tokens

    Tools

    SDK / curl / Cursor (limited) / Claude Code / Codex CLI

    Plan details
Availability and limits

Check tool access first, then compare allowances. Model usage is accounted for in equivalent tokens; see pricing for the full rules.

Each tool’s compatibility restrictions still apply. See plan details for features, concurrency, renewals and overages.

View full pricing and limits

05 / Before you start

Know the conditions before connecting.

Do I need to change my coding tool?

Keep using a supported terminal or IDE and configure its API URL, key and model. Protocols, minimum plans and compatibility restrictions vary by tool; check the setup section above.

Where does project context come from? Can I disable it?

Profiles and memories are organized by project. They may come from conventions you add or candidate knowledge extracted from tasks. Inspect sources, disable entries and control context injection in project settings.

Do free tokens include access to every tool?

Token allowances and tool permissions are separate. Check the selected tool’s minimum plan. Registration and free tokens do not unlock every terminal, model or cloud capability.

How do I check a request’s cost or failure reason?

Open the request record in the console to inspect status, model, usage, cost and error details. Pricing and your actual bill define model conversion and charging rules, including failed requests.

How is data stored? Do plans renew automatically?

Check the privacy policy and account settings for retention and deletion. Check the plan description and purchase screen for renewals, balances and overages before purchasing.

Start with your first request.

After registration, the setup guide helps you verify your identity, create a key and check the first request from your chosen tool.

Start setupRead the setup guide first
Selected tool: SDK / curl