Addepar vs Arch: API, MCP and investor access compared
Both are used by family offices and wealth managers to track private fund holdings, and Arch integrates with Addepar. This page sets the two registry entries side by side: how investors log in, whether an API or MCP server exists and for whom, what files can be exported, and what the terms say about automation.
Side by side
| Field |  Addepar Client Portal |  Arch |
|---|---|---|
| Vendor | Addepar, Inc.Country: US Vendor site | Arch Labs, Inc.Country: US Vendor site |
| Category | Reporting platform | Reporting platform |
| Regions | North America, Global, Europe | North America |
| Asset classes | Private equity, Venture capital, Private credit, Real estate, Hedge funds, Other | Private equity, Venture capital, Private credit, Real estate, Hedge funds, Fund of funds, Other |
| Web and SSO | AvailableSSO: None | AvailableSSO: not recorded |
| API | AvailableStyle: REST Auth: basic auth and OAuth 2 authorization code Audience: partner and fund administrator Sandbox: yes API docs | AvailableStyle: REST Auth: JWT and OAuth 2 client credentials Audience: LP, fund administrator and partner API docs |
| Investor-side API | Not offeredFrom the registry assessment | DocumentedFrom the registry assessment |
| MCP | BetaMaintainer: vendor Endpoint: https://mcp.addepar.com/Auth: OAuth 2 MCP docs | Not offered |
| SFTP | Unknown | Partner only |
| Webhooks | Unknown | Unknown |
| Email notifications | Available | Available |
| Export formats | PDF, XLSX, JSON | PDF, CSV, XLSX, JSON |
| Capabilities | Documents, Performance, NAV, Fund reports, Tax documents, Other | Documents, Capital calls, Distributions, Capital account statements, NAV, Performance, Tax documents, Fund reports, Other |
| Standards | OpenAPI, OAuth 2 | OpenAPI |
| Difficulty | 3 / 5Exports, SFTP or email feeds, no investor-side API | 2 / 5Partner or client API with some friction |
| Automation policy and terms | UnknownTerms URL not recorded | UnknownTerms URL not recorded |
| Known deployments | 0 | 0 |
| Verification | UnverifiedUpdated 2026-11-07 | UnverifiedUpdated 2026-11-07 |
"Not documented" and "Unknown" mean the researchers found no public statement either way, not that the feature is missing.
Key differences
- API. Addepar: available (REST, basic auth and OAuth 2 authorization code, for partner and fund administrator users, public docs, sandbox). Arch: available (REST, JWT and OAuth 2 client credentials, for LP, fund administrator and partner users, public docs).
- MCP server. Addepar: in beta (vendor-maintained, endpoint published, OAuth 2). Arch: not offered.
- SFTP. Addepar: not documented. Arch: partner only.
- Investor-side API. The assessment records access for the investor as not offered for Addepar and documented for Arch.
- Difficulty. The registry rates Addepar 3 of 5 (exports, SFTP or email feeds, no investor-side API) and Arch 2 of 5 (partner or client API with some friction). The rating describes how hard programmatic access is for an investor, not product quality.
- Capabilities. Listed for Arch only: Capital calls, Distributions and Capital account statements.
- Export formats. Listed for Arch only: CSV.
- Regions. Listed for Addepar only: Global and Europe.
- Asset classes. Listed for Arch only: Fund of funds.
- Standards. Listed for Addepar only: OAuth 2.
What the entries have in common
- Email notifications: both are recorded as available.
- Neither entry documents webhooks.
- Automation policy: unknown for both.
- Known deployments: none documented for either yet.
Which fits which need
Neither product is right for every team. The statements below are conditional and come straight from the registry fields above.
For investors and LP operations teams
- If your investors or your operations team need documents and data through an API, the registry records the API as available (aimed at partner and fund administrator users) for Addepar and available (aimed at LP, fund administrator and partner users) for Arch. Access for the investor itself is recorded as not offered for Addepar and documented for Arch.
- If you want to reach the data from an AI assistant, the MCP server is in beta for Addepar and not offered for Arch. A vendor MCP server can still be limited to the vendor's direct customers, so read the research notes below for who may sign in.
- If you process capital call and distribution notices from your inbox, email notifications are available for both.
- If you load files into your own systems, the registry lists PDF, XLSX and JSON for Addepar and PDF, CSV, XLSX and JSON for Arch.
- If you plan to automate your own login, automation in the terms is unknown for both. Where it is prohibited or unknown, ask the GP or the vendor for a sanctioned channel first.
For GPs, fund administrators and buyers
- If you need to connect the product to your back office, Addepar records API available, webhooks not documented and SFTP not documented; Arch records API available, webhooks not documented and SFTP partner only.
- If the product must carry the core LP reporting items (capital calls, distributions, capital account statements and tax documents), the structured capabilities cover tax documents for Addepar and all four for Arch.
- If your investors are concentrated in particular markets, the regions recorded are North America, Global and Europe for Addepar and North America for Arch.
- If you manage a specific strategy, the asset classes recorded are private equity, venture capital, private credit, real estate, hedge funds and other for Addepar and private equity, venture capital, private credit, real estate, hedge funds, fund of funds and other for Arch.
- If you want to see who already runs each product, the registry has no documented deployments for either yet. Operators can add theirs to the registry.
- If your investors will want programmatic access later, the difficulty rating is 3 of 5 for Addepar and 2 of 5 for Arch, where 1 is a documented self-serve API an investor can use and 5 is web login only with MFA.
For a structured shortlist beyond these two products, see the guide how to choose an investor portal.
What the research says
Addepar Client Portal
Assessment. Fully documented REST API with OpenAPI, Files and Portfolio endpoints, but keys are issued only to the licensing firm; a Client Portal end user has no self-serve API or MCP; firm-level family offices rate 2.
Research notes. Treated here as a portal (Client Portal), not as an aggregator. Confidence: high on API facts (vendor developer portal). The documented API is for the firm (advisor/family office) that licenses Addepar; the end investor viewing a Client Portal has no documented self-serve API or MCP. A family office that is itself the Addepar licensee gets full API access to positions and files. Rate limits unspecified (increase on request). Terms not reviewed. Correction 2026-11-07: vendor MCP server exists (closed beta), see access.mcp.
- Web: Firm-branded Client Portal (firmdomain.addepar.com): clients sign in with email/password, view holdings, allocations, performance and files published by the advisor; file vault includes advisor- and client-uploaded files. MFA methods not confirmed in public docs; API Tracker lists SSO/social login without detail.
- API: JSON:API REST with published OpenAPI spec. Keys created by firm administrators (Firm Settings > API Access Key); OAuth clients via partners@addepar.com. Resources: portfolio query/views, transactions, positions, entities, Files (/v1/files list/download), Generated Reports, Client Portal publish (/v1/portal/publish_files, scopes FILE_WRITE, PUBLISH_FILE). Environments: firmdomain.addepar.com/api, api.addepar.com (3rd parties), clientdev, partner sandbox. End investors (portal users) cannot obtain keys; access is firm-level.
- MCP: Official Addepar MCP server, Anthropic-verified Claude connector added August 2026, documentation marks it closed beta. Sign in with an Addepar account; permission aware. 15 tools including get_private_fund_cash_movements and get_upcoming_private_fund_capital_activity (capital calls, distributions, NAVs, unfunded). Aimed at advisor firm users; end-client access not stated.
- Email: publish_files API can notify clients when files are published.
Sources: developers.addepar.com/docs/resource-overview · developers.addepar.com/docs/faqs · developers.addepar.com/docs/urls · developers.addepar.com/docs/client-portal · developers.addepar.com/docs/tools-sdks
Arch
Assessment. Aggregator, not a GP portal: documented Client API (OpenAPI, JWT client credentials) exposing holdings, cash flows, activities and tax documents to the investor organisation or its delegate, plus SFTP/flat-file delivery; requires paid Arch subscription and docs are not readable anonymously.
Research notes. Classification: Arch is an AGGREGATOR / digital admin layer, not a GP-issued LP portal. It pulls 'statements, capital calls, and K-1s from portals and inboxes' on behalf of its clients (700+ customers, 50,000+ funds) and exposes the normalized data via its Client API and integrations (Addepar etc.). Confidence: high on API existence and resource list (API Evangelist index of OpenAPI files, 2026-07; vendor docs URL confirmed live but JS-rendered). Medium on SFTP/flat-file delivery (older vendor copy). Investor-side API: yes for the client organisation (investor or their delegate), gated by a paid subscription; auth is client-credentials JWT.
- Web: Client portal consolidating statements, capital calls, distributions and K-1s; digest emails of account updates and upcoming capital calls. MFA not published (trust.arch.com).
- API: Arch Client API (JSON REST, OpenAPI definitions per resource): Accounts, Activities, Cash Flows, Holdings, Investing Entities, Issuing Entities, Lookthroughs, Offerings, Tasks, Tax Documents, Users, User Roles, Firms, Addepar. Client-credential JWT bearer tokens. Available to Arch clients (family offices, wealth managers, institutional allocators, accounting firms). Docs site is a JS app; content not readable anonymously. Vendor also cites delivery via SFTP drop-offs and flat files (older site copy).
- MCP: No MCP server found (API Evangelist 2026-07; official registry empty).
- SFTP: Earlier arch.co site: 'delivers data to downstream systems via API integrations, SFTP dropoffs, flat files, or Open Data Program' (not on current arch.com page).
- Email: Digest email: account updates, upcoming capital calls, document summaries.
Sources: providers.apievangelist.com/providers/arch/ · arch.co/client-api/api-docs/ · arch.com/solutions.html · www.wealthmanagement.com/advisor-support-platforms/alts-platform-arch-raises-52m-in-series-b-round
Frequently asked questions
Does Addepar or Arch have an API investors can use?
Addepar: API available (REST, basic auth and OAuth 2 authorization code, for partner and fund administrator users, public docs, sandbox), investor-side access not offered. Arch: API available (REST, JWT and OAuth 2 client credentials, for LP, fund administrator and partner users, public docs), investor-side access documented. These are registry records from public sources, so confirm current terms with the vendor.
Do Addepar and Arch offer an MCP server?
Addepar: in beta (vendor-maintained, endpoint https://mcp.addepar.com/, OAuth 2). Arch: not offered. Vendor MCP servers often serve the vendor's direct customers first, such as GP teams, rather than every investor.
How hard is it to get data out of Addepar and Arch automatically?
The registry rates Addepar 3 of 5 (exports, SFTP or email feeds, no investor-side API) and Arch 2 of 5 (partner or client API with some friction). The scale runs from 1, a documented self-serve API an investor can use, to 5, web login only with MFA.
May I automate my login to Addepar or Arch?
Addepar's position on automated access is not recorded; check the terms before automating. Arch's position on automated access is not recorded; check the terms before automating.
Is this comparison affiliated with Addepar or Arch?
No. OpenInvestorPortal is independent community research built from an open registry. It is not affiliated with, sponsored by or reviewed by Addepar, Inc. or Arch Labs, Inc.. Both entries were last updated on 2026-11-07, and corrections are welcome by pull request or email to hello@openinvestorportal.com.