One SEC analysis utility. REST or MCP.
Send a company-specific question about a public SEC filing. Both interfaces use the same request and return filing-linked findings with explicit limitations.
Create an organization workspace, authorize an agent, and reveal its bearer key once. One successful analysis uses one credit at the provisional $1 per-action rate; failed operations use zero credits. Top-ups are available in one-time $10, $25, and $50 bundles.
Authenticated JSON over HTTPS
POST /v1/financial/sec/analyzeSend the request body below with Authorization: Bearer YOUR_API_KEY. The optional Idempotency-Key header lets a retry reuse the same operation.
Streamable HTTP MCP endpoint
POST /mcpInitialize the MCP connection, then call caskveil_sec_analyze with the same bearer key and request fields as REST.
Shared request contract
Ask about one filing.
This shape is shared by the REST request body and MCP tool arguments. The identifiers below are format examples only; replace them with a real company CIK and filing accession number.
{
"company": {
"cik": "0000000000",
"name": "Company name"
},
"filing": {
"accessionNumber": "0000000000-00-000000",
"form": "10-K"
},
"question": "What material risks does this filing describe?"
}company.cikis 10 digits; company name is optional.filing.accessionNumberis required; filing form is optional.questionis required and must be 8–2,000 characters.
MCP call shape
Use the same operation through MCP.
After initialization, call the named tool at /mcp. Its arguments follow the shared request contract above.
{
"jsonrpc": "2.0",
"id": 3,
"method": "tools/call",
"params": {
"name": "caskveil_sec_analyze",
"arguments": { /* same request fields as REST */ }
}
}A successful response includes an answer, 1–12 key findings, and 1–12 limitations. Each finding includes a filing section and source URL.
The answer is limited to 6,000 characters; a finding to 900; a section label to 140; and each limitation to 500. Citations point to filing sources and do not make the result investment advice.
Success · usage quantity 1 · charged true
Failure · usage quantity 0 · charged false
One prepaid Caskveil credit (provisionally $1) is charged only when analysis succeeds. A failed operation reports zero usage and is not charged. Both REST and MCP responses report the charged credit quantity; the published USD rate is the same for either interface.
Agent access and billing
Set up your agent in the workspace.
Create the organization and agent you authorize, store its one-time API key securely, then buy credits from the workspace. Checkout verifies the buyer-paid amount before the balance changes. The REST API and MCP are the available client interfaces.