Beta · B2B API platform. Partner API access is subject to company verification, enabled products and agreed scope.
How it works
How it works

Validate the need before promising the product.

Capulse is in development. We’re working with institutional design partners toward a planned launch in approximately four months; the estimate is not a guarantee of timing or access.

01

1. Validate the buyer and use case

Speak with product, engineering and analytics teams, narrow the first workflows and recruit design partners. Share a partnership enquiry to begin a discussion; it does not approve access or provision credentials.

02

2. Review prototypes and schemas

Review proposed API schemas, sample workflows and illustrative outputs with the team. Documentation is a development reference for selected testing, not general-availability documentation. All static examples are illustrative.

03

3. Assess controlled-pilot readiness

Before any pilot, assess relevant data rights, methodology, reliability, security, monitoring, support, limits and commercial terms. Testing is considered only when the relevant components are ready and separately provisioned.

04

4. Prepare for launch

Prepare the supported API catalogue, access process, indicative pricing, technical documentation and limitations. Availability will be announced only when ready; no production-readiness claim is made here.

05

Existing testing policy, if provisioned

There is no guaranteed sandbox access on registration. If an approved company is separately provisioned, its existing sandbox trial is 1,000 shared requests over 30 days, sandbox-only. This policy is not a production quota or general access offer.

One partner platform · eight API families

Financial intelligence APIs for partners

Integrate the financial data and analysis your product needs through documented REST endpoints. Each API reference explains its inputs, response fields, access requirements and data limitations.

01Source-dependent

Market Data

Supported market and instrument lookups, company data, quotes, history, and market context.

02Partner-submitted

Financial Account & Asset Data

Submit and retrieve partner-authorized account snapshots, balances, transactions, holdings, and aggregates. Direct bank and broker connections are not implied.

03Structured analytics

Financial Intelligence & Scoring

Market, company, portfolio, F&O and trading-behaviour analysis returned as structured fields and evidence.

04Consent-bound

Credit, Lending & Risk

Partner-supplied cash-flow, debt-burden, affordability, SME-ratio, threshold-risk, anomaly, early-warning, and human-review APIs. No bureau score, fraud finding, or lending decision.

05Partner API · Beta

Payments, Banking & Reconciliation

Import tokenized partner transaction and settlement records, look up imported status, reconcile sources with versioned rules, review exceptions, and export results. No bank connection or money movement.

06Partner controls

DPDP, Consent & Data Governance

Partner-attested consent records and scope checks support limited account operations; the standalone governance family is not enabled.

07Caller-supplied data

Investment, Wealth & Planning

Portfolio, wealth-health, and goal calculations based on data submitted by the partner.

08LLM-assisted

CapLLM Financial AI

Financial language-model capabilities with CapLLM as the primary provider and Claude as the secondary provider when configured.

Capulse is a B2B beta platform. Specific endpoints and data sources depend on company verification, product entitlement, subscription or sandbox access, key scopes, and required consent. Review the API documentation or interactive reference for endpoint-level details. Account and credit data is partner-supplied; consent records are partner-attested, not independently verified by Capulse.

Planned, not promised

The eight families describe the longer-term roadmap, not a confirmed launch catalogue. Initial intended focus is stock analytics and i-Score; portfolio risk, F&O and behaviour analytics are in development or controlled testing depending on endpoint. Data display and redistribution rights depend on source permissions and partner terms.