Prism API
Use Prism API keys to call common Prism research endpoints or the generic tool API over JSON.
The Prism API is a developer-facing JSON surface over the same scoped research tools used by Prism MCP. API keys are separate from MCP tokens and are shown once when created.
Workflow
Primary steps
- 1Create a Prism API key from the signed-in MCP & API dashboard.
- 2Send the key as an Authorization bearer token to /api/v1 routes.
- 3Use REST endpoints for common reads or /api/v1/tools/{toolName} for the complete scoped tool surface.
Authentication
Create an API key in the signed-in MCP & API dashboard, store it as a secret, and send it as Authorization: Bearer prism_api_...
MCP tokens do not authenticate API requests, and API keys do not authenticate MCP clients.
Endpoints
Common read routes include /api/v1/workspace/context, /api/v1/library/search?q=..., /api/v1/library/chunks/search?q=..., /api/v1/companies/{ticker}/context, /api/v1/articles/drafts, /api/v1/articles/posts?q=...&status=published&limit=50, and /api/v1/portfolios.
Posted article lists support q, status, visibility, linkedTicker, linkedCompanyId, limit, and sort filters.
For the complete scoped surface, call POST /api/v1/tools/{toolName} with { input: { ... } }. Responses return { data, meta }.
Write boundaries
Write tools are available only when Prism write tools are enabled for the deployment and the API key has the matching write scope.
API writes follow Prism's MCP boundaries: no publishing, scheduling, deletion outside exposed tools, subscriber emails, brokerage trades, or bypassing review surfaces.