Skip to main content
This guide walks you through creating an account, getting your API key, and making your first intelligence query.
1

Create an account

Go to app.deepcurrent.app and sign up. The Developer plan is free — no credit card required.
2

Get your API key

In the dashboard, go to Settings → API Key and click Reveal API key.
Your API key is shown only once. Copy it and store it somewhere safe — you cannot view it again after closing the dialog. If you lose it, you will need to request a new one from support.
Your key starts with dc_ and looks like this:
dc_A1b2C3d4E5f6G7h8I9j0K1l2M3n4O5p6Q7r8S9t0
3

Make your first API call

The Intelligence resolve endpoint is the starting point for every intelligence query. Send it a package ID and a plain-language request — it returns clarifying questions and suggested result slots so you know exactly what you will get before spending any credits.
curl -X POST https://api.deepcurrent.app/api/v1/intelligence/resolve \
  -H "Authorization: Bearer dc_your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{"package_id": "vc-shortlist-v1", "request_text": "Find DeFi seed-stage VCs"}'
4

Understand the response

The resolve endpoint returns two things: the result slots it plans to fill, and any clarifying questions that would improve the results.
{
  "suggested_slots": {
    "focus_area": "DeFi",
    "stage": "seed",
    "count": 10
  },
  "clarification_questions": [
    "What geography are you targeting — US, Europe, or global?",
    "Do you need VCs with active deal flow right now, or historical DeFi investments?"
  ]
}
You can answer the clarification questions and re-call resolve, or proceed directly to the quote step with the suggested slots.
The resolve → quote → execute flow ensures you always see the credit cost before anything is deducted. See Intelligence Packages for the full flow.

​
Next steps

Intelligence Packages

Learn about all seven intelligence packages and the quote-then-execute flow.

Authentication

Understand API key vs. JWT token auth, and how to handle auth errors.