Beta · B2B API platform. Partner API access is subject to company verification, enabled products and agreed scope.
C Partner workspace / API console
API reference
Developer workspace

Build, test, ship.

Bring Capulse research into the product your team already owns. Retrieve data with the REST API; use chat only to explore a few research questions.

01 / Start here · REST + JSON

Your first intelligence request

Call Capulse from your backend. Keep the partner key on your server; never expose it in browser or mobile code.

Quickstart docs ↗
Request
GET /api/v1/iscore/RELIANCE
cURL · server-side
curl https://api.capulse.tech/api/v1/iscore/RELIANCE \
  -H "Authorization: Bearer tc_live_YOUR_API_KEY"

Replace the placeholder with a key created in your API workspace. Secrets are shown only once when created.

Response contract JSON
The i-Score response includes the stock symbol and explainable score data. The OpenAPI contract is the source of truth for fields, types, and required parameters.
Versioned API · authenticated with Bearer token View schema ↗
02 / Endpoint catalog

Choose what you are building

Use these endpoints directly from your product backend.

Full reference ↗
Exact schemas and parameters are maintained in OpenAPI. Download spec
Sandbox only

Test safe lookups

Use the authenticated partner workspace before wiring requests into your product.

Read-only runner. The workspace console currently supports sandbox GET requests for /me, /iscore/{symbol}, and /fno/signals/live. Other endpoints must be called from your integration.
Open partner API workspace →
A small test surface

Explore with chat

Try a few research prompts in Capulse chat. For partner data retrieval and product integrations, use the API and its documented JSON contract.