Ship audit-grade Indian portfolio parsing without reverse-engineering registrars.
Portfolio Intel turns CAMS and KFintech CAS PDFs into structured JSON — holdings, NAV, units, cost basis, transactions, and folio data. Integrate via REST API, MCP transport, or the browser-based tool.
Start here
Pick the guide that matches your use case — from first API call to production integration.
Quickstart in five minutes
Generate a key, parse your first CAS, and understand the response shape before writing any integration code.
Platform setupClaude, Cursor, VS Code, ChatGPT
OAuth connector for Claude Desktop, bearer-header config for IDEs, and OpenAPI import for ChatGPT actions.
ReferenceREST and MCP endpoints
Parse, enrich, MCP transport, and authentication — everything you need to integrate.
ExamplesCode you can paste today
Node.js, Python, and cURL samples for every endpoint and MCP tool.
Platform setup guides
Step-by-step instructions for connecting Portfolio Intel to your AI client or IDE.
Claude Desktop / claude.ai
Add as an MCP connector with OAuth — no API key in config files.
Claude Code CLI
Remote MCP over HTTP with a bearer header.
Cursor IDE
Drop-in JSON config using remote MCP headers.
VS Code + Copilot
MCP server configuration snippet for Copilot.
ChatGPT Actions
OpenAPI import and OAuth discovery for custom GPT actions.
Frequently asked questions
Common questions developers ask before integrating. Full answers on the FAQ page.
What password formats do CAS PDFs usually use?
Default is PAN + DOB in DDMMMYYYY format (e.g. ABCDE1234F01Jan1990). Users who generate CAS directly from CAMS/KFintech can set a custom password.
Which statement types and registrars are supported?
CAMS and KFintech Consolidated Account Statements — both detailed and summary formats, including password-protected PDFs.
Should I use REST API or MCP for my product?
Use REST if your product owns the workflow. Use MCP if your users work inside Claude, Cursor, Copilot, or another MCP-capable client.
How does pricing work for test and live keys?
Test keys (sk_test_*) are free and return sample data. Live keys (sk_live_*) are metered per parse — see the pricing page for details.