commit_bank_transaction_import
ChatGPTRequires a connected re:cap account. Write the approved import into company's bank account and start the processing that follows. This changes financial data: call preview_bank_transaction_import first, show the user its counts and warnings, and only call this once they have confirmed them — pass that preview's previewToken. It accepts no rows, files, balances or overwrite settings of its own; everything it writes comes from what the user approved. An edited import, an expired approval, or a bank sync that changed the affected transactions is rejected rather than applied. Repeated or concurrent calls with the same token return the original execution and run nothing twice. It returns as soon as the work is queued: poll get_bank_transaction_import until it reports completed or failed, and do not tell the user their transactions are imported before then.
continue_capital_readiness_assessment
ChatGPTRecord answers and read the existing capital readiness assessment. Send the slug alone for a read without questions or writes. Send every answer already available together. The chat agent decides how to ask what is still missing: ask nextQuestion in chat, or, when nativeForm.available is true, set form: true to open one native form for the next missing answers, prefilled with editable proposedAnswers. The form saves only fields the user submits and completes with the updated assessment and the remaining proposedAnswers. An unsupported host returns an error. After cancelled, skipped or unsupported forms, stay in chat unless the user requests another form. Use skip for optional answers the user does not know. For a company's own assessment, send companyId (and assessmentId) instead of slug; the form is not offered there.
create_bank_transaction_tag_definition
ChatGPTRequires a connected re:cap account. Create one transaction tag category for a company, after the user has confirmed it. Two shapes: origin 'custom' adds a subcategory under an existing parent category and inherits that parent's kind and re:cap tag type, so parentTagTypeDefinitionId is required; origin 'project' adds a flat, parentless informative tag (a product line, team, or cost centre) and must NOT carry a parent. Resolve the parent with list_bank_transaction_tag_definitions and pass a definition that is not itself auto-generated. Always call preview_bank_transaction_tag_definition first with the same arguments, tell the user what it says will be created — the new category under its parent, plus the generated 'Other <parent>' leaf, the transaction count when willGenerateAutoTag is true, and that any budget values, cash-flow entries, forecast chart settings and invoice line-item tags on that category move with them — and only call this once they confirm. When the preview reports willGenerateAutoTag true you MUST pass its transactionsToMove back as expectedTransactionsToMove, even when it is 0; the write is rejected if that number changed in the meantime, so re-preview and re-confirm. The new category records the MCP as its creation channel and the account's email as its author, which does not distinguish you from the person whose account you are acting for. This tool cannot rename or delete categories; project tags are renamed and deleted with rename_bank_transaction_project_tag and delete_bank_transaction_project_tag, everything else stays in the app.
create_bank_transaction_tags
ChatGPTRequires a connected re:cap account. Create transaction tags for company bank transactions, replacing any previously active tags of the same category. This overwrites financial data: call preview_bank_transaction_tags first, show the user the diff it returns, and only call this once they confirm. Pass that preview's expectedActiveTags as expectedActiveTags so a concurrent re-tag is rejected instead of silently overwritten. Only send an amount when splitting one transaction across multiple category tags, in which case the category-tag amounts must sum to the transaction total; a single category tag covering the whole transaction takes no amount. Use splitGroupKey to pair one project tag with one category split line. Resolve every tagTypeDefinitionId via list_bank_transaction_tag_definitions — project tags (origin 'project') and custom subcategories are applied exactly like built-in tags.
create_forecast_scenario
ChatGPTRequires a connected re:cap account. Create a liquidity forecast scenario for company, optionally as a copy: fromForecastId carries the source scenario's settings, planned cash flows, and budget values into the new one, keeping its type and company view. Without fromForecastId, type (monthly or weekly) is required and the company view is resolved from the existing scenarios or the company's single view; pass companyViewId only when the company has several views and no scenario yet (see list_company_views). Use a copy for what-if scenarios so the founder's main plan stays untouched.
create_manual_bank_connection_for_import
ChatGPTRequires a connected re:cap account. Create the manual bank connection a prepared import needs for company, using the account details the user gave. Only call this when preview_bank_transaction_import reported createsConnection true, and only after the user confirmed that preview: it takes the previewToken and refuses a token that no longer matches. Calling it twice returns the connection it already created rather than making a second one. The new connection is visible in the app whether or not the import that follows succeeds. Call commit_bank_transaction_import next.
create_saved_agent
ChatGPTRequires a connected re:cap account. Create a customer-owned saved agent in Home → Manage Agents with title, prompt and dashboard visibility. Returns guidanceRoutineId for use as agentId. Add a schedule separately with create_saved_agent_schedule.
delete_bank_transaction_project_tag
ChatGPTRequires a connected re:cap account. Delete one of the company's project tags (origin 'project', from list_bank_transaction_tag_definitions). Name the tag to the user and call with confirmed=true only once they approve. Only an unused tag can be deleted: while any transaction still carries it as an approved tag the call is refused with the count, so re-tag those transactions without it via preview_bank_transaction_tags and create_bank_transaction_tags first. Refuses categories of any other origin. Cannot be undone through this tool.
delete_forecast_scenario
ChatGPTRequires a connected re:cap account. Delete one liquidity forecast scenario of company, such as a what-if copy that is no longer needed. Take its forecastId and current name from get_forecast's scenarios, tell the user which scenario will be removed and whether it is the default, and call with confirmed=true only after they explicitly approve. expectedName must match the scenario's current name. Deleting the default scenario makes the newest remaining one the default; the response names the default afterwards, or null when no scenario is left. The scenario disappears from the app and this tool cannot restore it; a repeated call reports not found.
delete_manual_bank_transaction
ChatGPTRequires a connected re:cap account. Delete one manually added bank transaction from company. First use list_bank_transactions to identify its bankAccountId, bankAccountTransactionId and transactionSourceType. Only transactions whose transactionSourceType is manual can be deleted; synchronized transactions and transactions with an unknown source are rejected. Show the user the transaction's date, amount, currency and counterparty or purpose, explain that its invoice links will also be removed, and obtain explicit confirmation before calling this tool with confirmed=true. This removes the transaction from the app without changing the bank account's stored balance or deleting the account. Deletion cannot be undone through this tool; a repeated call reports not found.
delete_saved_agent
ChatGPTRequires a connected re:cap account. Delete a customer-owned saved agent and its schedules. Use guidanceRoutineId from list_saved_agents as agentId. Confirm the agent to delete with the user before calling.
delete_saved_agent_schedule
ChatGPTRequires a connected re:cap account. Stop scheduled runs and email delivery for a customer-owned saved agent while keeping the saved agent. Use guidanceRoutineActionId from list_saved_agent_schedules as scheduleId. Confirm the schedule to remove with the user before calling.
download_file
ChatGPTRequires a connected re:cap account. Get a short-lived download URL for a company file.
get_account_security
ChatGPTRequires a connected re:cap account. Read whether the signed-in user has two-factor authentication on, plus the settings page where they change their password or two-factor setup themselves.
get_accounting_document_coverage
ChatGPTRequires a connected re:cap account. Get accounting-data coverage for one of your companies.
get_accounting_document_tabs
ChatGPTRequires a connected re:cap account. Get the tabs of an accounting document for company.
get_accounting_profit_and_loss
ChatGPTRequires a connected re:cap account. Get the accounting profit & loss statement for company. Accrual basis: what was booked, not what was paid. Use months to bound history and format='flat' when deterministic checks need matching descendants as top-level rows.
get_bank_cashflow_statement
ChatGPTRequires a connected re:cap account. Get the bank-derived cash flow statement for company. Cash basis: money that moved, split by tag; a tag sharing its name with a P&L line is a different quantity.
get_bank_transaction_import
ChatGPTRequires a connected re:cap account. Report where an import of company stands: needs_input, invalid, validated, previewed, queued, importing, recalculating, completed, or failed, plus whether the transactions are actually in the account and any failure with its retry guidance. Completion means the transactions were imported and the processing that follows finished, not that the file was received. transactionsPersisted true with a failed state means a later stage failed after the transactions were written — the fix is to retry that stage, never to upload the file again. A connection created for this import is reported whether or not the import itself succeeded.
get_business_plan
ChatGPTRequires a connected re:cap account. Get the business plan for company.
get_capital_advisory
ChatGPTRequires a connected re:cap account. Get the latest founder-facing capital advisory for company. The memo is written by the advisory pipeline; to change what it says, correct the founder's inputs with update_advisory_inputs and the report is republished. While none is published, a company with a capital readiness assessment gets capitalAdvisory null with a status and nextStep instead of an error: generating means the report is still being written, which is not a failure. Call it at most once per turn; it never waits for the report.
get_company
ChatGPTRequires a connected re:cap account. Read one company's own profile: legal identity and country, industry and business model, headcount and reporting currency, the funding intent the founder gave re:cap, and how far onboarding, compliance, and the data connections have got. Use it to ground answers about the company itself — the figures live in the scorecard, liquidity, accounting, and forecast tools.
get_company_research
ChatGPTRequires a connected re:cap account. Get the latest company research for one of your companies — a customer-safe company profile derived from re:cap's research. Returns companyName, legalEntityName, website, industry, customerType, businessModel, pricingStructure, assetLightBusiness, countriesRegisteredIn, countryOfIncorporation, fundingSummary, redFlags, greenFlags, and financeabilityTeaser, plus a status: 'available' when research exists, 'pending' when it has not been produced yet.
get_covenant_monitoring
ChatGPTRequires a connected re:cap account. Get covenant monitoring data for company.
get_data_quality_check
ChatGPTRequires a connected re:cap account. Get the latest data quality check for company, or null when none exists.
get_forecast
ChatGPTRequires a connected re:cap account. Get the liquidity forecast for company: the cash plan the app draws on its forecast page. Per period it returns the opening and closing cash balance, the operating inflow, outflow and total rows, and one series per cash-flow tag — each split into actual (money that moved), budget, and forecast. A company can hold several scenarios; scenarios lists all of them and forecasts carries the values of the default one unless forecastIds or allScenarios asks for others. Values are aggregated into the scenario's own period, monthly or weekly, and every values array is aligned to periods. A parent tag already contains its children, listed in childTagIds — never add both.
get_forecast_inputs
ChatGPTRequires a connected re:cap account. List the editable inputs of a liquidity forecast scenario for company: every planned cash flow and budget value with its id, every tag they may be assigned to with its current trend and budget method, the period counts, and the invoice-inclusion setting. This is the only source of the row ids and tag ids that preview_forecast_scenario_update and update_forecast_scenario take, and of expectedInputsDigest. get_forecast shows the computed series; this tool shows the inputs behind them.
get_fundability_check
ChatGPTRequires a connected re:cap account. Get the latest Fundability Check for company, or a specific assessment when assessmentId is provided.
get_funding_summary
ChatGPTRequires a connected re:cap account. Get a company's funding totals: outstanding principal and remaining repayment (book figures), total paid out and payback due, and active and requested payout counts. Use it to answer what the company still owes.
get_invoice_receivables_summary
ChatGPTRequires a connected re:cap account. Get the receivables summary for company. Invoice-book basis: what was billed and paid on. A company with no subscription dataset returns a zeroed summary with hasSubscriptionData false rather than an error; that is a final answer, not a transient failure.
get_liquidity
ChatGPTRequires a connected re:cap account. Get liquidity figures for company. Bank cash basis: cash balance, burn and runway on operating cash.
get_metric_docs
ChatGPTRequires a connected re:cap account. Get re:cap's own definition of a metric — how it is computed, which data it is built from, and how to read it. This is the definition behind every figure the other tools return, so use it before explaining burn, runway, growth, margins, or any other scorecard metric, and quote it instead of a textbook definition. If list_faqs has an entry for the metric, answer in its wording. Takes no company data and returns none. Names match the computation, for example 'runway', 'burn_rate', 'cash_balance', 'rule_of_40'; a partial name resolves to the fuller one.
get_my_account
ChatGPTRequires a connected re:cap account. Read the signed-in user's own re:cap account: name, sign-in email, language, mobile number, and their role in each company they belong to.
get_notification_preferences
ChatGPTRequires a connected re:cap account. Read which re:cap emails the signed-in user receives for one company: Pulse Check frequency, significant-event Pulse Checks, financing emails, and data-collection emails.
get_qualitative_company_review
ChatGPTRequires a connected re:cap account. Get the latest qualitative company review for company.
get_scorecard
ChatGPTRequires a connected re:cap account. Get the latest scorecard for company. Metric key prefixes name the basis: C- bank cash, A- accounting accrual, I- invoice book, BP- business plan.
get_scorecard_series
ChatGPTRequires a connected re:cap account. Get the monthly scorecard series for company. Metric keys carry the same basis prefixes as get_scorecard.
get_task
ChatGPTRequires a connected re:cap account. Get one Task Center task with its comments, submissions and uploaded files.
list_accounting_documents
ChatGPTRequires a connected re:cap account. List the accounting documents for one of your companies.
list_accounting_files
ChatGPTRequires a connected re:cap account. List accounting files for company with processing status. Optional fileContentType and ignored filters are applied server-side before pagination.
list_bank_accounts
ChatGPTRequires a connected re:cap account. List customer-visible bank accounts connected to one of your companies, including disabled accounts. enabled reports whether the account is enabled; manuallyDisabled distinguishes an explicit deactivation from an automatic one. These account settings do not establish whether the provider connection is active or syncing.
list_bank_transaction_tag_definitions
ChatGPTRequires a connected re:cap account. List every transaction tag definition available for the company — the built-in re:cap hierarchy AND the company's own project tags (origin 'project') and custom subcategories (origin 'custom'). This is the only source of the tagTypeDefinitionId that preview_bank_transaction_tags and create_bank_transaction_tags require, and the only way to see the company's project tags: list_bank_transactions shows only tags already applied to the transactions it returns, so an unused project tag never appears there. Each entry carries origin, kind, recapTagType ('project' for project tags), tagHierarchy, and taggable — only taggable (leaf) definitions can be assigned. Filter with origin=project to list just the project tags; countsByOrigin shows whether the company has any.
list_bank_transaction_tag_overrides
ChatGPTRequires a connected re:cap account. List customer-applied bank transaction tag overrides for one of your companies. Returns every event where a non-re:cap user changed a transaction between Operating cash flow and Financing & Investing, or applied exclude_from_burn_rate. Data-quality checks use the full history to distinguish reviewed customer classifications from system tagging.
list_bank_transactions
ChatGPTRequires a connected re:cap account. List bank transactions for company with their active tags. Each active tag carries a tagTypeDefinitionId; the tagDefinitions map on the response resolves those ids to a readable tagHierarchy, so report tags by name rather than by id. The tags shown are only those already applied, so use list_bank_transaction_tag_definitions to enumerate what the company could be tagged with, including its project tags.
list_capital_suppliers
ChatGPTRequires a connected re:cap account. List the equity investors, debt providers and grant programmes re:cap assessed for this company, best fit first, with the fit band and reason codes behind it. Start broad and narrow together with the founder: on the first call send no minBand and no category. When the company's published capital advisory leads with equity, debt or grants, send that capitalType and name the other capital types only by their eligible counts from summary, which the card does not show; otherwise send no capitalType, so the result spans every capital type. Do not open with only the top few names, because too little is known about the founder and their goals yet. An unknown fact never excludes a supplier or lowers its band, so band 2 covers every eligible supplier nothing known speaks against; say so instead of calling those suppliers weak. Speak to the founder in the widget's words, never in band numbers or reason codes: band 3 is a strong match, band 2 a match, a lower eligible band a possible match, and an ineligible supplier no match. When the founder asks why the list looks as it does, explain it from selection: which rules ran on which company input, how many suppliers each removed, and which inputs are still unknown. total is every supplier left by the requested filters, eligible is the subset the company qualifies for, strongFits is the eligible subset at band 2 or 3, strongMatches the part of it at band 3, and rosterTotal every supplier in the database before any filter; matched is a compatibility alias for eligible. Filter by capital type, supplier type, category, stage, market, thesis, ticket range, minimum band or search. A ticket range keeps the suppliers with no recorded ticket and lists them after every supplier whose recorded ticket matches the range, each part best fit first, so a strong match with no recorded ticket can follow a possible match with one. Those rows carry ticketUnverified, and the ticketUnverified count says how many eligible suppliers they are, so eligible minus ticketUnverified have a matching recorded ticket; call their ticket size not known rather than a fit. onlyMatches defaults to true; set it to false to include ineligible suppliers. The response echoes the normalized callable arguments in filters. criteria contains the saved values with their source and last update; use it to inspect or preserve existing composite fields before recording a correction. summary contains company-wide counts before these filters, rosterVersion identifies the roster, and newSinceSeen counts unseen band-2-or-3 matches. Guide refinement with the founder, not in the widget. This tool only reads suppliers. When decisiveQuestions is non-empty, ask in the chat after showing the results the first question, by highest movesSuppliers, that the conversation has not already answered outside its narrowingAnswers; only those answers change the list, so say which answer narrows it and by up to how many suppliers. Record an answer the conversation already gave with refine_capital_suppliers instead of asking it, so the question does not come back. When asking, record the confirmed answer with refine_capital_suppliers, and continue one question at a time. Never ask a narrowing question of your own: a question that is not in decisiveQuestions, or whose answer is already known, changes nothing. For a broad result without a decisive question, offer relevant facet choices. Do not silently apply a preference the founder has not stated. To read one supplier in full, pass its supplierId in supplierIds with detail true: the row then carries detail with the website, what they look at, active markets, status and last review date. When locked is true the list is a preview: rows come in an order that follows neither name nor fit and carry the coarse public label, capital type, supplier type, categories and country but no ids, names, bands, reasons or detail, and search, supplierIds and minBand are ignored. Relay lockedReason if the founder asks why names are missing, and do not recommend changing plans.
list_companies
ChatGPTRequires a connected re:cap account. List companies
list_company_invitations
ChatGPTRequires a connected re:cap account. List a company's open invitations to join its re:cap account: invitation ID, invitee email, role, whether pending or expired, and when sent and expiring. Use invitationId to withdraw a pending invitation. Accepted invitations appear in list_company_members instead.
list_company_members
ChatGPTRequires a connected re:cap account. List the people with access to a company's re:cap account: account ID, name, email, role, whether they are the primary contact, and when they joined. Use accountId when changing a member's role or removing them.
list_company_views
ChatGPTRequires a connected re:cap account. List company views
list_data_connection_source_files
ChatGPTRequires a connected re:cap account. List source files uploaded for one of your company's data connections. Returns file metadata used to reconcile the connection inventory with processed accounting data.
list_data_connections
ChatGPTRequires a connected re:cap account. List the data connections feeding company, with each one's health and the action the user must take. Hidden connections are excluded by default; includeHidden=true includes them when connection management is enabled. Internal connections are never listed.
list_data_quality_checks
ChatGPTRequires a connected re:cap account. List the platform's latest deterministic data-quality results for one of your companies. Each row includes the check type, result, check-specific metadata, snapshot, and creation time. A failed row is evidence for the shared data-quality workflow to verify, not a standalone verdict.
list_faqs
ChatGPTRequires a connected re:cap account. Return re:cap's complete set of pre-approved answers to common questions in one call — every entry with its key, category, question and full answer. Two categories: platform covers using the app (uploads, bank connections, categorisation, forecasting) and metric definitions, funding covers the re:cap funding product itself — what it is, what it costs, who qualifies, and how the process runs end to end. Call this before answering any question about how re:cap or the app works and ground your reply in re:cap's own wording rather than describing the process from memory. Takes no company data and returns none.
list_files
ChatGPTRequires a connected re:cap account. List downloadable raw documents for company.
list_funding_infrastructure_fees
ChatGPTRequires a connected re:cap account. List customer-visible recurring infrastructure fees for a company, newest first, with payout, date, and lifecycle details. Draft fees are excluded.
list_funding_paybacks
ChatGPTRequires a connected re:cap account. List a company's funding payback schedule and history, including replaced entries. Only open installments of active and overdue payouts are owed; scheduled, pending and requested ones are planned. payoutId links to list_funding_payouts.
list_funding_payouts
ChatGPTRequires a connected re:cap account. List a company's funding payouts, newest first, with payout, repayment, and financing-term details. Draft and rejected payouts, which will not be disbursed, are left out.
list_funding_plans
ChatGPTRequires a connected re:cap account. List customer-visible funding plans for a company, including lifecycle state, financing terms, fees, facility limits, business-plan linkage, and covenant thresholds.
list_funding_transaction_fees
ChatGPTRequires a connected re:cap account. List customer-visible one-time funding transaction fees for a company, newest first, with linked payout and invoice details.
list_invoice_receivable_customers
ChatGPTRequires a connected re:cap account. List subscription customers for company. Depending on the available source data, this uses either customer records or contract records.
list_invoice_receivable_invoices
ChatGPTRequires a connected re:cap account. List subscription invoices for company.
list_saved_agents
ChatGPTRequires a connected re:cap account. List the company's saved agents from Home → Manage Agents, including title, prompt, dashboard visibility, schedule summary and the caller's latest result. Use guidanceRoutineId as agentId in agent and schedule tools.
list_tasks
ChatGPTRequires a connected re:cap account. List the Task Center tasks re:cap has sent the company, newest first.
open_recap
ChatGPTOpens re:cap in ChatGPT's sidebar: for a signed-in founder their companies' financial health and capital options, without an account re:cap's capital provider dot map. All conversation, including the assessment and its interactive intake forms, runs in ChatGPT's chat. Opened by the user from the sidebar; you do not need to call it. To run an assessment yourself, call start_capital_readiness_assessment.
prepare_bank_transaction_import
ChatGPTRequires a connected re:cap account. Stage bank transactions for one of company's bank accounts and report every problem found, without importing anything. Takes exactly one source: a CSV or XLSX the user attached (file), a file already in re:cap (sourceFileId, from list_files), a small CSV as text (csvText), or structured rows. Set target.bankAccountId to import into an existing account — resolve it with list_bank_accounts — or target.createManualAccount with the holder, identifier, currency, balance and balance date to create a new manual one; ask the user for those and never infer a balance from the transactions. The reply reports state needs_input with the exact missing fields, invalid with every blocking error at once, or validated. Each issue carries a stable code, the original one-based row and column, the offending value and a correction, so the user can fix a batch in one pass. Pass the returned importId back with mappings to correct source columns, static values, formats or status/currency translations, and edits to correct individual cells or exclude source rows. For XLSX, availableSheets lists exact sheet names. A workbook with multiple sheets needs parsing.sheetName before preparation; ask which sheet to use. One-sheet workbooks select it automatically. Omitted sheetName retains the selection. Changing the sheet resets saved mappings, edits and other parsing settings unless supplied again. The response returns sourceColumns, effective parsing, mappings and edits. Edit row is one-based in the original file, matching issue.row; columnIndex is zero-based in sourceColumns. Omitted parsing, mappings and edits retain existing choices. A supplied mappings list replaces the choices and detects unlisted fields again; mappings=[] resets all mappings, edits=[] clears all corrections. Replacing the source starts fresh. Every successful prepare, including an issue-page read, creates a new revision and invalidates the previous preview. Nothing is written to any bank account by this tool. Call preview_bank_transaction_import once the state is validated.
preview_bank_transaction_import
ChatGPTRequires a connected re:cap account. Work out exactly what a validated import would change for company, without writing a transaction, touching a balance, or creating a connection. Takes the importId and revision prepare_bank_transaction_import returned. Returns the destination account, the date range, how many transactions are new, updated, unchanged, excluded because the bank already synchronizes those days, or already present with no counterpart in the file, plus a page of the individual changes and any warnings. Show the user those counts and warnings and get their confirmation before calling anything else. It records what they are approving and returns a previewToken; commit_bank_transaction_import and create_manual_bank_connection_for_import both require that token. Changing the source, the mapping, the destination or overwrite invalidates it, and so does a bank sync that lands in the meantime — re-preview and re-confirm in that case rather than retrying the commit.
preview_bank_transaction_tag_definition
ChatGPTRequires a connected re:cap account. Dry-run creating one transaction tag category for a company: same arguments as create_bank_transaction_tag_definition, nothing is written. Returns willCreate (name, origin, parent, and the resulting tagHierarchy), willGenerateAutoTag with autoTagName, and transactionsToMove — how many transactions currently tagged with the parent would move onto that generated 'Other <parent>' leaf. willGenerateAutoTag is true only when the parent has no subcategories yet: that write makes the parent untaggable, generates the leaf, moves those transactions onto it, and triggers a scorecard recalculation. transactionsToMove counts every transaction carrying an active tag on that parent — rejected-but-never-ended tags included, and transactions on bank accounts that are now disabled or deleted included — so it is exactly the set of transactions the move re-points, and can exceed the count the app shows for that category. It is still not the full footprint: any budget values, cash-flow entries, forecast chart settings and invoice line-item tags on that category move with it uncounted. Show the user which categories appear and that those uncounted items travel with them, then pass transactionsToMove back to create_bank_transaction_tag_definition once they confirm.
preview_bank_transaction_tags
ChatGPTRequires a connected re:cap account. Preview bank transaction tag changes without writing anything, and show the caller the returned diff before calling create_bank_transaction_tags. Takes the same arguments. Resolve every tagTypeDefinitionId via list_bank_transaction_tag_definitions, which covers project tags and custom subcategories as well as the built-in ones. Pass the returned expectedActiveTags straight through to create_bank_transaction_tags.
preview_forecast_scenario_update
ChatGPTRequires a connected re:cap account. Preview input changes to a forecast scenario of company without writing anything: takes the items and settings update_forecast_scenario would apply, computes the scenario with and without them, and returns the per-period closing-balance path before and after plus the delta. Show the user this diff before calling update_forecast_scenario with the same items and settings, and pass the returned expectedInputsDigest through so a concurrent edit is rejected instead of overwritten. Resolve row ids and assignable tag ids via get_forecast_inputs first. Settings travel in the same change set: per-tag trend (dynamicTrend, periodCount, growthRate) and budget method (recurring_value, moving_average, imported), period counts, and invoice inclusion; period counts only change the window the app shows, never the computed series. A company without enough bank history cannot be forecast — that error is a final answer, not a transient failure.
refine_capital_suppliers
ChatGPTRequires a connected re:cap account. Record what the founder has said about the investors and programmes they want, and read the shortlist back in the same call. Send only the criteria the founder stated in words in this conversation; never infer one from the company's revenue, size, industry or research, and record nothing for a question the founder answered with not sure or did not answer. Send every criterion they stated in one call, such as all of grantProject's fields from one sentence. Each entry replaces the stored value for its key, so an object value (roundConstruction, grantProject, aiClassification) must carry every field the founder has stated, not only the one that changed; clear forgets a key so it counts as unknown again. The response carries saved criteria with provenance, company-wide match summary, remaining questions, delta, the eligible count before and after, and shortlist, the first 5 eligible suppliers at band 2 or above after the change, with supplierId, name, label, capital type, supplier type and band. Send the capitalType of the area under discussion; it scopes only the shortlist, and without it the shortlist spans every capital type. Report the change in one sentence and name the leading suppliers from shortlist for that area only; for another area call list_capital_suppliers with its capitalType, and call it too for more rows, reasons or tickets. instrumentTypes records the instruments the founder wants, as {"mode": "only" or "first", "instruments": [...]} with values from the instrumentTypes input of list_capital_suppliers: only removes every supplier offering none of them from the shortlist and the capital readiness assessment, first keeps them and lists them first. Sale and leaseback is a form of leasing that the leasing providers offer, so for a founder asking for it record leasing. restructuringRecent records, as true or false, whether the company has recently been through a financial restructuring with its creditors, such as renegotiated debt or insolvency proceedings; ask it only when decisiveQuestions lists it, in neutral words and without suggesting an answer. true removes banks and growth-underwritten lenders from the shortlist and the capital readiness assessment, while equity investors and other lenders stay. sponsorBacked records, as true or false, whether a venture capital or private equity investor backs the company; ask it only when decisiveQuestions lists it, in neutral words and without suggesting an answer. For a loss-making company false removes the lenders that lend against cash flow only because an investor backs the borrower, in the shortlist and the capital readiness assessment; true and an unknown answer keep them. A value re:cap's operations team recorded outranks the founder's; criteria shows which source applies. Shortlist rows come best fit first when locked is false and in preview order when locked is true. When locked is true the shortlist is a preview sample: its rows carry the coarse public label, capital type and supplier type but no ids, names or bands, so describe them as a sample by label, never as the leading or best suppliers, and relay lockedReason if the founder asks why names are missing, and do not recommend changing plans.
rename_bank_transaction_project_tag
ChatGPTRequires a connected re:cap account. Rename one of the company's project tags (origin 'project', from list_bank_transaction_tag_definitions) after the user confirms the new name. Transactions tagged with it keep the tag under the new name. Refuses categories of any other origin, and a name another project tag of the company already uses — to merge duplicates, re-tag the transactions onto the tag you keep and delete the other with delete_bank_transaction_project_tag.
request_company_research
ChatGPTRequires a connected re:cap account. Start stored company research when get_company_research reports 'pending'. Not for capital readiness assessments: start_capital_readiness_assessment runs their research. Safe to retry; existing or in-flight research is not duplicated. Results usually land in 20-40 seconds; then call get_company_research once.
save_data_quality_check
ChatGPTRequires a connected re:cap account. Save a data quality check for company.
start_capital_readiness_assessment
ChatGPTOpen re:cap's capital readiness assessment using the company's website and any answers already available. The website is required unless companyId is sent; resolve a named company to its domain when possible. This tool opens the assessment and records the answers sent with it directly. It opens a native form only when form is true; an unsupported host then returns an error. Show the results and inspect nativeForm.available, then either ask nextQuestion in chat and record answers with continue_capital_readiness_assessment, or call continue_capital_readiness_assessment with form: true and optional editable proposedAnswers. Use re:cap's assessment when the user asks what they can raise, which financing fits, or what holds financing back; do not substitute public-research reasoning. With a connected re:cap account, send companyId instead of website to run the company's own assessment: it resumes the one in progress, records the answers sent, and when every question is answered publishes the company's capital advisory in re:cap. The result then carries status, companyId, assessmentId and nextStep; a company whose advisory is already published gets status published and nothing is recorded.
update_forecast_scenario
ChatGPTRequires a connected re:cap account. Change a forecast scenario of company. Scenario details: rename it, make it the scenario the app opens by default (setAsDefault: true), or change its view settings (the deviation comparison, the chart type, and whether the app shows the budget, live-forecast, and deviation columns); view settings are display preferences stored on the scenario in re:cap and change no forecast input, and current values are in get_forecast's scenarios. Forecast inputs: items create, update, and delete planned cash flows and budget values, and settings change per-tag trend and budget methods, period counts, and invoice inclusion; they apply all-or-nothing in one transaction and recompute the scenario once. Changing inputs overwrites the company's cash plan: call preview_forecast_scenario_update with the same items and settings first, show the user the diff it returns, and only call this once they confirm; pass the preview's expectedInputsDigest so a concurrent edit is rejected instead of overwritten. Input changes run before scenario details, so a rejected change leaves the whole scenario untouched. For exploratory what-ifs, change a copy made with create_forecast_scenario rather than the default scenario, so the founder's main plan stays untouched until they adopt the change. Creating an imported budget value replaces the tag's previous imported values on this scenario. Returns the scenario; when inputs changed, also counts of what changed and the recomputed forecast in the get_forecast shape.
update_my_account
ChatGPTRequires a connected re:cap account. Change the signed-in user's own name, language, or mobile number. Send only what changes. The sign-in email cannot be changed here; for that the user contacts re:cap support.
update_notification_preferences
ChatGPTRequires a connected re:cap account. Change which re:cap emails the signed-in user receives for one company. Send only what changes. Before turning any email off, confirm it with the user. The last member receiving financing or data-collection emails cannot turn them off.
update_saved_agent
ChatGPTRequires a connected re:cap account. Edit a customer-owned saved agent's title, prompt or dashboard visibility. Omitted fields keep their current values; showOnDashboard=false unpins the agent. Use guidanceRoutineId from list_saved_agents as agentId.
