Daepak

Daepak for Developers

Price, indicators, levels, positioning, kimchi premium, US stocks, options, backtesting — the tools analysts use, 100 tools delivered as API and MCP. The free plan includes 2,000 credits per month, so you can build something in an evening.

Try It Now

You can call public data without a key. With a key, you use the actual tools as-is.

Connect via MCP

Attach in a single line to engines that support MCP, such as Claude Code and Claude Desktop.

claude mcp add daepak -e DAEPAK_API_KEY=dpk_live_… -- uvx daepak-mcp

The server does not describe anything on its own. It fetches the catalog from GET /v1/tools, so it shows exactly what the key is allowed to and does not drift from the product.

Use Directly via REST

# Catalog: schema, permissions, pricing
curl -H "Authorization: Bearer dpk_live_…" https://daepak.com/v1/tools

# Tool call
curl -X POST https://daepak.com/v1/tools/get_price \
     -H "Authorization: Bearer dpk_live_…" \
     -H "Content-Type: application/json" \
     -d '{"coin": "BTC"}'

{
  "tool": "get_price",
  "credits_used": 1,
  "credits_left": 1999,
  "took_ms": 104,
  "data": { "coin": "BTC", "price": 78017.26, "change_24h": -1.2 }
}

Reference

All 98 tools are documented with argument schemas, required permissions, and credit prices. The specification is generated from the same schema that analysts receive, so it does not drift from the product.

OpenAPI 3.1 — readable as-is in Swagger UI, Redoc, Postman, Insomnia, code generators, and anywhere else. You can view it without a key.

Endpoint

Response envelope

Every tool call is wrapped in the same shape — along with the result, how much it cost comes back. Not settled later, but visible right there.

{
  "tool": "get_price",
  "credits_used": 1,      // Failed calls are 0 — you don't pay
  "credits_left": 1999,
  "took_ms": 104,
  "data": { … }           // The tool's own result
}

Conversations · Images · Files

/v1/agent/messages uses the same path as chat. The response returns a conversation_id, so if you send it in the next request, the context continues. Put a data-URL in images and it also reads chart screenshots.

curl -X POST https://daepak.com/v1/agent/messages \
     -H "Authorization: Bearer dpk_live_…" -H "Content-Type: application/json" \
     -d '{"message": "How's BTC right now?", "lang": "ko"}'

# Put the conversation_id from the response into the next request to continue the conversation
{ "answer": "…", "conversation_id": 1234, "lang": "ko", "took_ms": 8120 }

The image drawn by make_chart comes in the response's url — you can receive it directly with the same key.

curl -N -X POST https://daepak.com/v1/agent/stream \
     -H "Authorization: Bearer dpk_live_…" -H "Content-Type: application/json" \
     -d '{"message": "How's BTC right now?", "mode": "mentor"}'