Atominvest

Get full account details by ID. This is the authoritative source for which entities belong to an account — read the entities field. Also surfaces linked contacts, companies, and commitment relationship IDs. Resolve the account ID first using list_accounts.

get_account

Get full details for a specific asset by ID, including metric settings such as yearEnd. ALWAYS call this before calling get_metric_data to retrieve the required yearEnd value (asset.metricSettings.yearEnd).

get_asset_details

Get full details for a specific commitment record by ID.

get_commitment

Get full details for a specific company by ID.

get_company

Tracks investor engagement with a specific fund's dataroom and portal page. Use this to answer: - How many times has an investor visited/accessed this fund? → investmentViews in byUser - Who has downloaded or viewed documents? → downloads and views in byUser - Which documents are most accessed? → byDocument - How has engagement trended over time? → byDate WHAT EACH METRIC MEANS: - downloads: number of times an investor downloaded a document from the dataroom - views: number of times an investor previewed/viewed a document in the dataroom - investmentViews: number of times an investor visited this fund's page in the investor portal. This is the closest available proxy for "how many times did this investor access/log into this fund." Use this to answer questions about portal visit counts, engagement frequency, or investor activity on a fund. WHAT THIS TOOL CANNOT DO: - True platform login counts (LOG_IN events) are not captured by this endpoint — investmentViews is the best available proxy - Cross-fund activity (investmentId is always required) - Account-level grouping — byUser is flat, one row per person WORKFLOW NOTES: - investmentId is REQUIRED — use list_investments first if you only have a fund name - dateFrom is optional — omit to get all-time activity; use YYYY-MM-DD format - byUser is sorted by downloads descending - byDocument is sorted by downloads descending with a 1-based index - byDate shows daily download and view totals in ascending date order

get_dataroom_activity

Lists, per fund, which investor contacts are ALLOWED to see and download that fund's dataroom, and what level of access each contact has been granted. This is CONFIGURED ACCESS — not activity. NOT ACTIVITY — DO NOT CONFUSE WITH get_dataroom_activity: - This tool answers "who is allowed to access this dataroom, and can they download?" — i.e. the permission grant itself, as configured by the fund admin. - It does NOT tell you whether a contact has actually logged in, viewed, or downloaded anything. - For real usage/engagement (actual downloads, views, portal visits), use get_dataroom_activity instead. A contact can be granted full access here and still show zero activity there, and vice versa (e.g. access was later revoked after downloads already happened). Never infer download activity from the restrictDownload flag — the two are unrelated. FOUR SEPARATE CONCEPTS — DO NOT CONFLATE: - viewOn: whether the contact currently has dataroom/portal access switched on for this fund at all. Says nothing about which stage they see or whether they can download. - permissions: which dataroom stage(s)/folder(s) the contact can see — "all" (everything), "none" (nothing), or one or more of "s1"/"s2"/"s3" (specific dataroom stages). If the contact has no explicit stage assignment, this falls back to the fund's default dataroom permission. Independent of download rights. - restrictDownload: whether the contact can download, or is view-only. This is ORTHOGONAL to permissions — e.g. permissions:["all"] + restrictDownload:true means the contact can see everything but download nothing. true = view-only (cannot download). false = can download. Always present (defaults to false when not explicitly restricted). - sentEmail: whether an access-notification email has been sent to this contact for this fund. Says nothing about current access rights. FILTERING (all optional, can be combined — they AND together): - investmentIds: narrow to specific fund(s). Omit to return permissions across every fund in the environment — this can be thousands of rows, so prefer passing investmentIds when you know the fund(s). To resolve a fund name to an ID, call list_investments first. - contactIds: narrow to specific contact(s). - unpublished: true = only unpublished funds, false = only published funds. Omit for both. - restrictDownload: "true" = only contacts who CANNOT download (view-only). "false" = only contacts who CAN download. Omit to return both. ID GOTCHA — investmentIds here are Investment IDs, NOT Portfolio IDs: - investmentIds takes the same ID that list_investments / get_investment return (the fund's _id). - This is DIFFERENT from get_investment_transactions, get_investment_schedule, and list_asset_transactions, which all expect the portfolioId instead. Do not resolve or pass a portfolioId here — pass the plain fund ID directly. - contactIds takes Person IDs — the same ID used by list_persons / get_person. RESOLVING IDS: - resolveIds defaults to false — investmentId/contactId hold the raw ObjectIds. - With resolveIds=true, the investmentId/contactId KEYS REMAIN, but their VALUES are resolved in place: investmentId becomes the fund name; contactId becomes the contact's email — not their name. Same shape either way, just human-readable values. - Trade-off: once resolved, the raw ObjectIds are no longer available in that response. If you need the ID to act on afterwards (e.g. to call another tool), call without resolveIds, or resolve separately.

get_dataroom_permissions

Get the full raw entity record by ID. Use this only when the user explicitly requests the full entity record, or when fields needed are not available from list_entities.

get_entity

Get full details for a specific investment (fund) by ID.

get_investment

Returns holdings summary / investment schedule data — NAV, IRR, subscriptions, distributions, multiples, and ownership — broken down by security, asset, or fund as of a specific date. FOUR SECTIONS — request whichever you need: - showSecurityAsset: one row per security, in security native currency. Use when you need security-level detail or want native-currency figures. - showSecurityAssetFund: one row per (security × fund), in fund currency. Use when you need to see how a specific security performs within a specific fund. - showAssetFund: one row per (asset × fund), in fund currency. Use for asset-level rollup within a specific fund. - showFund: one row per fund, in fund currency. Use for top-level fund performance. Returns full fund totals — not filtered to any asset. CURRENCY — no currency param. Each section has a fixed currency: - showSecurityAsset → security native currency (matches "Security Currency" view in UI) - showSecurityAssetFund, showAssetFund, showFund → fund currency (matches "Fund Currency" view in UI) This means NAV values will differ between showSecurityAsset and showSecurityAssetFund for the same security — this is correct, not a bug. FILTERS — each section takes its own filter object with either assetIds or fundIds (not both): - { "assetIds": ["id1", "id2"] } → returns rows for those assets - { "fundIds": ["id3", "id4"] } → returns rows for those funds - showFund only accepts fundIds. BEFORE CALLING: - Get assetIds from list_assets. - fundIds here are Portfolio IDs — NOT the Fund Vehicle ID returned by list_investments. To resolve a fund name to a fundId: list_investments → get_investment → read portfolioId → pass here. - At least one section must be provided — the backend returns 400 if none are passed. READING THE RESPONSE: - All sections are under response.output — e.g. response.output.SecurityAsset, response.output.Fund. - response.rateLimits and response.filters are metadata — ignore when reporting results. - Each section is { columns: [...], rows: [[...]] } — use columns to map row values by name. - resolveIds is always true — assetId and fundId fields contain names, not ObjectIds. - ValuationDate across all sections is the date of the last booked VALUATION transaction — it is NOT the as-of date. It may lag the asOfDate and may be empty if no valuation transaction exists. This lag is expected — do not warn the user about it. NAV = 0 ON SecurityAsset ROWS: - This is correct when no VALUATION transaction exists in the security's native currency. - Use showSecurityAssetFund for the same security to get the fund-currency NAV. STATUS FIELD: - status on SecurityAssetFund and AssetFund rows is correct (active / partiallyExited / exited). - status on SecurityAsset and Fund rows may return "" — this is a known bug being fixed separately. Do not report "" as the actual status. Use SecurityAssetFund status for the same security instead. COMBINING SECTIONS: - You can request multiple sections in one call. Each runs an independent query in parallel. - showFund returns the full fund total regardless of what other sections are filtering to. Example: showAssetFund filtered to Octopus Inc + showFund filtered to CryptoAlpha Fund → AssetFund shows Octopus-only data; Fund shows the full CryptoAlpha Fund total (all assets). - Do not expect the numbers to reconcile across sections — they answer different questions.

get_investment_schedule

Returns investment transaction values and financial metric values for a fund as of a specific date. One result object is returned per type requested, inside response.output[]. BEFORE CALLING: - Get investmentId from list_investments. Never guess or construct an ID. - investmentId is a portfolioId, NOT the Investment ID from list_investments. To resolve a fund name: call list_investments → get the Investment ID → call get_investment with that ID → read portfolioId from the result → pass that as investmentId. - Get assetId from list_assets if narrowing to a specific asset. HOW TO PASS TYPES: - Pass as a comma-separated string e.g. "SUBSCRIPTION,NAV,DISTRIBUTION". - Results come back in the same order as types were passed. - Available types: SUBSCRIPTION, DISTRIBUTION, NAV, RETURN_OF_COST, ACCRUED_INCOME, COMMITMENT, EXPENSES, GROSSIRR, GROSS_MULTIPLE, REALIZED_MULTIPLE, REALIZED_CAPITAL, REALIZED_INCOME, VALUATION. WHAT EACH TYPE MEANS: - SUBSCRIPTION: capital called/invested - DISTRIBUTION: cash returned to investors - NAV: net asset value - GROSS_MULTIPLE: (NAV + distributions) / subscriptions - GROSSIRR: gross internal rate of return - RETURN_OF_COST: capital returned against cost basis - ACCRUED_INCOME: income accrued but not yet distributed - COMMITMENT: total committed capital - EXPENSES: fund expenses - REALIZED_MULTIPLE: distributions / subscriptions - REALIZED_CAPITAL: realised capital - REALIZED_INCOME: realised income - VALUATION: valuation transaction amount CURRENCY — IMPORTANT DEFAULT: - Default is "security" if currency is NOT passed. - To get fund reporting currency values, explicitly pass currency="fund". CUMULATIVE vs PERIOD: - isCumulative=true: cumulative value up until the date specified. - isCumulative=false (default): value for the period ending on the date only. - The following types ignore isCumulative — passing it has no effect: GROSSIRR, GROSS_MULTIPLE, NAV, REALIZED_MULTIPLE. - For SUBSCRIPTION, COMMITMENT, EXPENSES: Always pass isCumulative=true unless the user explicitly asks for a specific period's activity only. READING THE RESPONSE: - Results are in response.output — NOT at the root level. - response.filters echoes back what was requested (metadata only). - response.rateLimits is also metadata — ignore when reporting results. - Only investment, date, type, and value are always present in each output object. Optional fields (asset, security, currency, isCumulative, isInverted) only appear in the output if they were included in the request. ZERO VALUE WARNING: - A value of 0 does NOT confirm the metric is zero — it may mean no transactions of that type exist for the fund/date combination. - Do not report 0 as a definitive figure. Qualify it as "no data found or zero." SCOPE: - Without assetId: values cover the entire fund across all assets. - With assetId: values are filtered to that specific asset within the fund.

get_investment_transactions