Add institutional holdings to your app
Give your agent 13F data. Call it as an MCP tool to read a fund manager's quarterly holdings and changes, or list the institutions holding a stock. You switch it on with a single toggle — no SDK and no endpoint wiring — and it answers over MCP or REST using the same key as every other skill.
A real response from the Institutional Holdings Skill — exactly what your agent gets back when it makes the call.
{
"cik": "1067983"
}Enable Institutional Holdings and your app can add institutional holdings to your app through one connection — no client library for a finance API, no keys to rotate per provider. The skill answers over MCP or REST using the key you already have.
Over MCP, Institutional Holdings shows up as the institutionalholdings tool your model calls whenever a task needs live numbers — it decides when, you don't write the glue.
Flip the skill on and call it from your backend the same day; there's nothing to deploy and nothing to maintain as the underlying data changes.
Once enabled, this skill is reachable two ways — pick whichever fits how you build. Both use the same key.
It appears to your model as a callable tool. No extra code — the agent invokes it when a task needs it.
institutionalholdingsCall it from your server with one request and your key. Node, Python, Go — anything that can send a GET.
GET /v1/institutionalholdingsHow to connect it over MCP or REST.
Same data, same VerveKit account, same credit balance — one key works on all of them.
The same key runs from your first prototype to millions of calls — on APIVerve's rails, 99.9% uptime.
See pricing