LinqAlpha
LinqAlpha is a domain-specialized multi-agent AI platform for institutional investment research, serving hedge funds, asset managers and investment banks. It runs retrieval-augmented, agentic analysis across SEC filings, earnings-call transcripts, IR materials, news and macroeconomic data covering 57,600+ companies in 120+ countries and 30+ languages, returning answers with inline citations that resolve to the exact source chunks. The LinqAlpha API exposes that engine over a REST surface at api.linqalpha.com — streaming analytics and chat over Server-Sent Events, document search, natural-language-to-SQL, scheduled research briefings, an RMS/Vault ingestion path for a firm's own internal documents, and a source-grounding judge that scores how well each claim in an answer is backed by the sources it cited. LinqAlpha also publishes a first-party remote MCP server exposing 22 financial-data tools to AI assistants.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles LinqAlpha the way a machine reads it — 16 machine-readable artifacts across 10 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — LinqAlpha scores 54.4/100 (developing), with a separate agent-readiness read of 62/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile LinqAlpha
Each block below is one kind of artifact we hold for LinqAlpha. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 10
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
LinqAlpha Briefing API
Briefing Agent — automated market briefings with scheduling and delivery
LinqAlpha Connectors API
Customer Connectors — customer-owned MCP connector management
LinqAlpha Data API
Data retrieval and mapping
LinqAlpha Feedback API
Conversation feedback
LinqAlpha MCP API
LinqAlpha MCP — Financial data tools for AI assistants via Model Context Protocol
LinqAlpha RMS API
Research Management System
LinqAlpha Search API
Search and generate responses
LinqAlpha Source Management API
Source batch and file management
LinqAlpha Status API
Sync status — check organization, document, and container sync progress
LinqAlpha Vault API
The Vault API from LinqAlpha — 3 operation(s) for vault.
Scroll within the panel for all 10 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
linqalpha-mcp.yml
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Linqalpha Rate Limits
RATE LIMITSSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for LinqAlpha — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Access & Security 5
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/linqalpha · machine-readable index on apis.io