For Agents
Read AngelList fund data: investment vehicles, distributions, capital calls, capital accounts, valuation updates, financial statements, and portfolio companies. All operations are read-only GETs authenticated with OAuth2 read scopes.
Use for: Get the latest valuation updates for a fund vehicle, List the distributions paid out by a vehicle this quarter, Retrieve the financial statements backing a vehicle's asset figures, Find the capital calls scheduled for a vehicle
Not supported: Does not handle fund administration, capital call collection, or investor onboarding. Use for reading AngelList fund, vehicle, and portfolio data only.
The AngelList Funds API reads fund and investment-vehicle data for firms running SPVs, syndicates, and rolling funds. It returns distributions, capital calls, subscriptions, capital accounts, valuation updates, and the financial statements that back a vehicle's reported figures, plus the partners and portfolio companies tied to each vehicle. Every operation is read-only and scoped by OAuth2 permissions, so an agent can pull reporting data without any ability to change account state.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AngelList Funds API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fangellist.com%2Fangellist" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fangellist.com%2Fangellist" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with AngelList Funds API.
Read investment-vehicle details for SPVs, funds, and rolling fund quarters
List distributions, capital calls, and subscriptions tied to a vehicle
Pull the financial statements and capital accounts that back a vehicle's reported figures
Track valuation updates and portfolio asset positions held by a vehicle
Search and download documents attached to a vehicle
Look up firms, partners, and portfolio companies across the caller's organization
Patterns agents use AngelList Funds API for, with concrete tasks.
★ Fund Reporting Automation
An agent assembles a quarter-end report for a fund by reading its distributions, capital calls, and valuation updates from AngelList, then cross-referencing the financial statements that back those figures. Because the whole surface is read-only, the agent can gather the numbers for a vehicle without any risk of altering fund records.
Call GET /v1/distributions and GET /v1/capital_calls for a vehicle, then GET /v1/financial_statements to reconcile the reported figures
Portfolio Monitoring
A monitoring workflow pulls the portfolio companies and asset positions held by each investment vehicle, then checks valuation updates to flag material changes for an investor. The agent reads companies, assets, and valuation data per vehicle so it can surface movements without manual spreadsheet work.
Call GET /v1/companies and GET /v1/assets for a vehicle, then GET /v1/valuation_updates to detect changes since the last report
AI Agent Integration via Jentic
An AI agent reaches the AngelList Funds API through Jentic without handling the OAuth token itself. It searches by intent, receives the matching read operation with its input schema, and executes the call with the credential injected at run time, so it can pull fund and vehicle data as a step inside a larger reporting task.
Search Jentic for 'list fund distributions', load the GET /v1/distributions schema, and execute it with Jentic-managed credentials
33 endpoints — the angellist funds api reads fund and investment-vehicle data for firms running spvs, syndicates, and rolling funds.
METHOD
PATH
DESCRIPTION
/v1/me
Get the authenticated user
/v1/vehicles
List investment vehicles
/v1/distributions
List distributions for a vehicle
/v1/capital_calls
List capital calls for a vehicle
/v1/financial_statements
List financial statements for a vehicle
/v1/companies
List portfolio companies
/v1/documents/search
Search documents for a vehicle
/v1/valuation_updates
List valuation updates for a vehicle
/v1/me
Get the authenticated user
/v1/vehicles
List investment vehicles
/v1/distributions
List distributions for a vehicle
/v1/capital_calls
List capital calls for a vehicle
/v1/financial_statements
List financial statements for a vehicle
/v1/companies
List portfolio companies
/v1/documents/search
Search documents for a vehicle
/v1/valuation_updates
List valuation updates for a vehicle
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>What agents get from Jentic-routed access to this vendor.
Setup
Wiring the AngelList Funds API by hand means running its OAuth2 client-credentials flow against gateway.angellist.com, requesting the right read scopes, and refreshing tokens yourself. Through Jentic you install once, import AngelList from the API Directory, store the credential once, and your agent calls it.
Permission scoping
Every AngelList operation is a read (GET), and OAuth2 scopes such as vehicles:read, distributions:read, or financial_statements:read bound which data types the token can reach. You choose the scopes and operations the agent may call, so it can read distributions without being handed firm or document access it does not need.
Credential isolation
Your AngelList OAuth token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list fund distributions' or 'read a capital account', and Jentic returns the matching AngelList operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using AngelList Funds API through Jentic.
What authentication does the AngelList Funds API use?
The AngelList Funds API authenticates with OAuth2 per its OpenAPI spec, offering both the client-credentials and authorization-code flows against gateway.angellist.com, with granular read scopes such as vehicles:read, distributions:read, and financial_statements:read. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at execution time, so it never reaches the agent.
Can I read a fund's distributions and capital calls with the AngelList Funds API?
Yes. GET /v1/distributions and GET /v1/capital_calls return the cash-flow records for a vehicle, and GET /v1/financial_statements returns the workbooks that back the figures. Note that a capital call's status tracks its due date only and never reports collection, so treat it as a schedule rather than a settlement record.
What are the rate limits for the AngelList Funds API?
The AngelList OpenAPI spec does not specify rate limits. Watch for HTTP 429 responses and consult AngelList's developer documentation for the current limits before issuing high-volume reads across many vehicles.
How do I read a vehicle's distributions with the AngelList Funds API through Jentic?
Search Jentic for 'list fund distributions', and it returns the AngelList operation with its input schema. Load the schema and execute GET /v1/distributions for the vehicle with the credential injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there an AngelList Funds API MCP server?
You don't need an MCP server to give your agent the AngelList Funds API. Jentic connects it directly from the API Directory: import it, store your OAuth credential once, and your agent calls the read operations it needs. Operations are discovered on demand, so no extra server's tool definitions sit in the agent's context.
Can I limit what my agent is allowed to do with the AngelList Funds API?
Yes. Write a rule that grants only the read scopes and operations the task needs, for example vehicles:read and distributions:read, so the agent can pull a vehicle's cash flows while firm and document reads stay off the table. The whole API is read-only, and every call runs through your own instance where it is logged for review.
GET STARTED