# TOPY.AI

> TOPY.AI is an AI CEO for founders: it writes investor-ready business plans, revises them when a figure, milestone or the team changes, drafts SEIS Advance Assurance applications, and keeps the founder's CEO records (decisions, risks, investors, growth experiments).

## Pages

- [Home](https://topy.ai/)
- [AI CEO](https://topy.ai/ai-ceo): what the AI CEO does
- [Pricing](https://topy.ai/pricing)
- [Developers](https://topy.ai/developers): MCP server, CLI, skills and API
- [Blog](https://topy.ai/blogs)

## For agents

- Remote MCP server: https://topy.ai/mcp (streamable HTTP, OAuth 2.1 with PKCE; metadata at https://topy.ai/.well-known/oauth-authorization-server)
- CLI: `npm i -g @topy-ai/ceo-cli`, then `ceo-cli login`
- Local stdio MCP server: `npx -y @topy-ai/ceo-mcp` (after `npx @topy-ai/ceo-mcp login`, or with TOPY_API_KEY)
- Skills for Claude Code, Codex, Cursor, Gemini CLI and other agents: `npx @topy-ai/ceo-skills install` (42 skills; source https://github.com/TOPY-AI-LTD/TOPY-AI-CEO-Skills)
- REST API: https://topy.ai/api/v1 (bearer API key or OAuth token), reference at https://topy.ai/api/docs
- Tool catalogue (JSON with input schemas): https://topy.ai/api/v1/agent/tools
- Changes are previewed first and run only after the user confirms; plan generation costs 50 TOPY credits.

## Tools (423)

- account_get (R0): Who is signed in to TOPY.
- credits_get (R0): TOPY credit balance (paid and free), optionally with recent transactions.
- entitlements_get (R0): The user's plan and which features it includes (AI editing, project and template limits).
- dashboard_link (R0): A link to a page of the TOPY web app, when the founder asks to see it there. Everything can be done in the chat (credits_buy, integration_connect_link, delegation_set …); only managing API keys needs the web app.
- projects_list (R0): The user's projects (the companies or ideas TOPY works on). Most tools take one as project_id.
- project_get (R0): A project's details: what it does, market, industry, keywords and website.
- project_update (W1): Change a project's details. Changes the project given as project_id.
- project_create_from_idea (W1): Create a project from an idea: a title and a description of the business. (runs an AI generation.)
- project_create_from_website (W1): Create a project by reading an existing website (runs as a job; follow it with project_job_get). (runs an AI generation.)
- project_job_get (R0): Progress of a project job (created from a website or upload).
- project_delete (W1): Archive a project (restorable with project_restore).
- project_restore (W1): Restore an archived project.
- media_list (R0): The user's media library: images uploaded to TOPY or registered by URL (newest first, up to 200).
- media_add_url (W1): Add an image to the media library by its URL (stored as a link; nothing is downloaded).
- media_delete (W4): Delete an item from the media library permanently.
- ideas_generate (W1): Generate startup ideas around a topic or market. (runs an AI generation.)
- idea_get (R0): One idea with its details.
- idea_brainstorm (W1): Brainstorm an idea in depth (by idea_id, or a free-text term): market, competitors, angles. (runs an AI generation.)
- idea_to_project (W1): Turn a saved idea into a project.
- agent_actions_list (R0): The changes agents made for this user over MCP or the CLI (newest first), each after the user confirmed it.
- standing_permissions_list (R0): Standing permissions: which of the user's keys (a scheduled agent's) may add which records to which project without a preview, each tool's daily cap and today's use. Granted with standing_permission_grant and revoked with standing_permission_revoke (the founder's decision).
- plan_options_get (R0): Business plan templates, purposes, audiences and writing styles for a project, with the recommended template. Use these ids exactly.
- plans_list (R0): List a project's business plans (summaries with status, words and section list).
- plan_get (R0): A business plan: summary and section list; set full for the whole Markdown or section for one section's Markdown.
- plan_status (R0): Generation progress of a plan (or of a job: a generation, revision, Markdown fix or impact analysis).
- plan_estimate (R0): What a business plan generation costs in TOPY credits against the current balance (no charge).
- plan_generate (W2): Start writing a new business plan for a project with a template, purpose, audience and style from plan_options_get (about 7 minutes). Costs 50 TOPY credits. (spends TOPY credits; runs an AI generation.)
- plan_job_cancel (W1): Cancel a queued or running business plan job.
- plan_job_retry (W2): Retry a failed business plan generation. Costs 50 TOPY credits again (a failed job was refunded). (spends TOPY credits; runs an AI generation.)
- plan_update (W1): Replace a plan's Markdown: one section (with section) or the whole plan. Use for edits the user wrote or accepted.
- plan_rename (W1): Rename a business plan or star it.
- plan_delete (W1): Archive a business plan (restorable with plan_restore).
- plan_restore (W1): Restore an archived business plan.
- plan_section_suggest (R0): Ask the AI to rewrite one section from an instruction. Returns a suggestion only; nothing changes until plan_update. (runs an AI generation; needs a plan with the AI features.)
- plan_section_regenerate (W1): Rewrite one section from scratch with the plan's writer (replaces that section). (runs an AI generation; needs a plan with the AI features.)
- plan_fix_markdown (W1): Fix the Markdown of every section (diagrams to tables, no code blocks or HTML) without changing the content. Runs as a job; follow it with plan_status. (runs an AI generation; needs a plan with the AI features.)
- plan_revise_analyze (R0): Work out what a change (a figure, milestone, KPI or the team) means for the whole plan: old -> new facts, derived figures and the impact on each section. Changes nothing and costs no credits; follow the job with plan_status, then show the result to the user. (runs an AI generation; needs a plan with the AI features.)
- plan_revise_apply (W1): Write a change into a NEW version of the plan, updating the affected sections in order with a final consistency check (the source plan is kept, no credits). Needs a finished plan_revise_analyze. (runs an AI generation; needs a plan with the AI features.)
- plan_export (R0): A business plan as Markdown (plan_export_word gives the Word file as a link).
- plan_seis_assurance (R0): Draft the answers for a UK SEIS Advance Assurance application from a finished plan. (runs an AI generation; needs a plan with the AI features.)
- plan_defaults_set (W1): Set the project's default template, purpose, audience and style for new plans.
- templates_list (R0): The official business plan templates and the user's own templates for a project.
- template_create (W1): Create a custom template: clone an official or custom one, have the AI build one from a requirement (ai_prompt), or from a document's text (upload_file). (runs an AI generation.)
- template_update (W1): Change a custom template: name, description, industry or its structure (template_json).
- template_delete (W1): Archive a custom template (restorable).
- template_restore (W1): Restore an archived custom template.
- template_star (W1): Star or unstar a template (official or custom).
- template_assistant (R0): Ask the AI to change a custom template's structure from an instruction. Returns a suggestion only; keep it with template_update. (runs an AI generation; needs a plan with the AI features.)
- research_sources_list (R0): List the project's records of a research source (market data, article, interview) behind the project's claims.
- research_source_get (R0): One record of a research source (market data, article, interview) behind the project's claims.
- research_source_create (W1): Add a research source (market data, article, interview) behind the project's claims.
- research_source_update (W1): Change a research source (market data, article, interview) behind the project's claims.
- research_source_delete (W4): Delete a research source (market data, article, interview) behind the project's claims permanently.
- decisions_list (R0): List the project's records of a decision the founder made, with its context and reasoning.
- decision_get (R0): One record of a decision the founder made, with its context and reasoning.
- decision_create (W1): Add a decision the founder made, with its context and reasoning.
- decision_update (W1): Change a decision the founder made, with its context and reasoning.
- decision_delete (W4): Delete a decision the founder made, with its context and reasoning permanently.
- journal_entries_list (R0): List the project's records of a founder journal entry.
- journal_entry_get (R0): One record of a founder journal entry.
- journal_entry_create (W1): Add a founder journal entry.
- journal_entry_update (W1): Change a founder journal entry.
- journal_entry_delete (W4): Delete a founder journal entry permanently.
- gtm_plans_list (R0): List the project's records of a go-to-market plan.
- gtm_plan_get (R0): One record of a go-to-market plan.
- gtm_plan_create (W1): Add a go-to-market plan.
- gtm_plan_update (W1): Change a go-to-market plan.
- gtm_plan_delete (W4): Delete a go-to-market plan permanently.
- memories_list (R0): List the project's records of a fact or preference to remember about the project.
- memory_get (R0): One record of a fact or preference to remember about the project.
- memory_create (W1): Add a fact or preference to remember about the project.
- memory_update (W1): Change a fact or preference to remember about the project.
- memory_delete (W4): Delete a fact or preference to remember about the project permanently.
- risks_list (R0): List the project's records of a risk with its likelihood, impact and mitigation.
- risk_get (R0): One record of a risk with its likelihood, impact and mitigation.
- risk_create (W1): Add a risk with its likelihood, impact and mitigation.
- risk_update (W1): Change a risk with its likelihood, impact and mitigation.
- risk_delete (W4): Delete a risk with its likelihood, impact and mitigation permanently.
- investor_contacts_list (R0): List the project's records of an investor contact in the fundraising pipeline.
- investor_contact_get (R0): One record of an investor contact in the fundraising pipeline.
- investor_contact_create (W1): Add an investor contact in the fundraising pipeline.
- investor_contact_update (W1): Change an investor contact in the fundraising pipeline.
- investor_contact_delete (W4): Delete an investor contact in the fundraising pipeline permanently.
- investor_updates_list (R0): List the project's records of an investor update (a periodic letter to investors).
- investor_update_get (R0): One record of an investor update (a periodic letter to investors).
- investor_update_create (W1): Add an investor update (a periodic letter to investors).
- investor_update_update (W1): Change an investor update (a periodic letter to investors).
- investor_update_delete (W4): Delete an investor update (a periodic letter to investors) permanently.
- growth_experiments_list (R0): List the project's records of a growth experiment with its hypothesis, metric and result.
- growth_experiment_get (R0): One record of a growth experiment with its hypothesis, metric and result.
- growth_experiment_create (W1): Add a growth experiment with its hypothesis, metric and result.
- growth_experiment_update (W1): Change a growth experiment with its hypothesis, metric and result.
- growth_experiment_delete (W4): Delete a growth experiment with its hypothesis, metric and result permanently.
- memory_context (R0): What the AI cofounders remember about this project (topy-memory): the founder's preferences, the project's conventions, lessons from fixed mistakes and recent errors — active and unexpired only, the most relevant first. Read it at the start of work on a project and follow it; `markdown` gives the repo's .topy/memory.md. `founder` is who the founder is as a person, as the CEO keeps it for you (with role): fit your work to it, and for_you says what a note means for your work.
- memory_remember (W1): Remember something about this project for every cofounder: a preference of the founder, a convention of the project, or a lesson from a fixed mistake (with the problem, the solution and the evidence). It is a candidate until the founder confirms it — status active only when they said so. Never a key, token or password.
- memory_review (W1): Confirm a candidate (active), or retire an item (superseded, archived) — history is kept, never deleted.
- memory_record_error (W1): Record a failure in the project's error history (the same fingerprint counts again instead of repeating). A fixed error needs its resolution and how the fix was validated; it never becomes a lesson by itself.
- milestones_list (R0): List the project's records of a milestone (a state the company commits to reach by a date: launch, revenue, funding, hire, compliance).
- milestone_get (R0): One record of a milestone (a state the company commits to reach by a date: launch, revenue, funding, hire, compliance).
- milestone_create (W1): Add a milestone (a state the company commits to reach by a date: launch, revenue, funding, hire, compliance).
- milestone_update (W1): Change a milestone (a state the company commits to reach by a date: launch, revenue, funding, hire, compliance).
- milestone_delete (W4): Delete a milestone (a state the company commits to reach by a date: launch, revenue, funding, hire, compliance) permanently.
- kpis_list (R0): List the project's records of a KPI with its target, baseline and cadence (each comes back with its latest value and health).
- kpi_get (R0): One record of a KPI with its target, baseline and cadence (each comes back with its latest value and health).
- kpi_create (W1): Add a KPI with its target, baseline and cadence (each comes back with its latest value and health).
- kpi_update (W1): Change a KPI with its target, baseline and cadence (each comes back with its latest value and health).
- kpi_delete (W4): Delete a KPI with its target, baseline and cadence (each comes back with its latest value and health) permanently.
- objectives_list (R0): List the project's records of an objective: a company goal (plan_json.level company) or a quarterly objective under one (plan_json.parent_id), with its key results (KPIs) and health.
- objective_get (R0): One record of an objective: a company goal (plan_json.level company) or a quarterly objective under one (plan_json.parent_id), with its key results (KPIs) and health.
- objective_create (W1): Add an objective: a company goal (plan_json.level company) or a quarterly objective under one (plan_json.parent_id), with its key results (KPIs) and health.
- objective_update (W1): Change an objective: a company goal (plan_json.level company) or a quarterly objective under one (plan_json.parent_id), with its key results (KPIs) and health.
- objective_delete (W4): Delete an objective: a company goal (plan_json.level company) or a quarterly objective under one (plan_json.parent_id), with its key results (KPIs) and health permanently.
- tasks_list (R0): List the project's records of a task (an action with an owner and a due date).
- task_get (R0): One record of a task (an action with an owner and a due date).
- task_create (W1): Add a task (an action with an owner and a due date).
- task_update (W1): Change a task (an action with an owner and a due date).
- task_delete (W4): Delete a task (an action with an owner and a due date) permanently.
- personas_list (R0): List the project's records of a customer persona (segment, pains, gains, jobs to be done, budget, objections, channels).
- persona_get (R0): One record of a customer persona (segment, pains, gains, jobs to be done, budget, objections, channels).
- persona_create (W1): Add a customer persona (segment, pains, gains, jobs to be done, budget, objections, channels).
- persona_update (W1): Change a customer persona (segment, pains, gains, jobs to be done, budget, objections, channels).
- persona_delete (W4): Delete a customer persona (segment, pains, gains, jobs to be done, budget, objections, channels) permanently.
- ceo_briefs_list (R0): List the project's records of a CEO brief or review (daily, weekly, monthly, quarterly, board).
- ceo_brief_get (R0): One record of a CEO brief or review (daily, weekly, monthly, quarterly, board).
- ceo_brief_create (W1): Add a CEO brief or review (daily, weekly, monthly, quarterly, board).
- ceo_brief_update (W1): Change a CEO brief or review (daily, weekly, monthly, quarterly, board).
- ceo_brief_delete (W4): Delete a CEO brief or review (daily, weekly, monthly, quarterly, board) permanently.
- financial_scenarios_list (R0): List the project's records of a financial scenario (plan, current, conservative, optimistic) with its assumptions.
- financial_scenario_get (R0): One record of a financial scenario (plan, current, conservative, optimistic) with its assumptions.
- financial_scenario_create (W1): Add a financial scenario (plan, current, conservative, optimistic) with its assumptions.
- financial_scenario_update (W1): Change a financial scenario (plan, current, conservative, optimistic) with its assumptions.
- financial_scenario_delete (W4): Delete a financial scenario (plan, current, conservative, optimistic) with its assumptions permanently.
- meetings_list (R0): List the project's records of a meeting (board, investor, team) with its agenda, pack, minutes and resolutions.
- meeting_get (R0): One record of a meeting (board, investor, team) with its agenda, pack, minutes and resolutions.
- meeting_create (W1): Add a meeting (board, investor, team) with its agenda, pack, minutes and resolutions.
- meeting_update (W1): Change a meeting (board, investor, team) with its agenda, pack, minutes and resolutions.
- meeting_delete (W4): Delete a meeting (board, investor, team) with its agenda, pack, minutes and resolutions permanently.
- journeys_list (R0): List the project's records of a customer journey for a persona: stages with touchpoints, pains, KPIs and experiments.
- journey_get (R0): One record of a customer journey for a persona: stages with touchpoints, pains, KPIs and experiments.
- journey_create (W1): Add a customer journey for a persona: stages with touchpoints, pains, KPIs and experiments.
- journey_update (W1): Change a customer journey for a persona: stages with touchpoints, pains, KPIs and experiments.
- journey_delete (W4): Delete a customer journey for a persona: stages with touchpoints, pains, KPIs and experiments permanently.
- cap_share_classes_list (R0): List the project's records of a share class on the cap table.
- cap_share_class_get (R0): One record of a share class on the cap table.
- cap_share_class_create (W1): Add a share class on the cap table.
- cap_share_class_update (W1): Change a share class on the cap table.
- cap_share_class_delete (W4): Delete a share class on the cap table permanently.
- cap_holders_list (R0): List the project's records of a cap table holder (founder, employee, investor, or the option pool).
- cap_holder_get (R0): One record of a cap table holder (founder, employee, investor, or the option pool).
- cap_holder_create (W1): Add a cap table holder (founder, employee, investor, or the option pool).
- cap_holder_update (W1): Change a cap table holder (founder, employee, investor, or the option pool).
- cap_holder_delete (W4): Delete a cap table holder (founder, employee, investor, or the option pool) permanently.
- cap_holdings_list (R0): List the project's records of a holding: shares of one class held by one holder.
- cap_holding_get (R0): One record of a holding: shares of one class held by one holder.
- cap_holding_create (W1): Add a holding: shares of one class held by one holder.
- cap_holding_update (W1): Change a holding: shares of one class held by one holder.
- cap_holding_delete (W4): Delete a holding: shares of one class held by one holder permanently.
- rounds_list (R0): List the project's records of a funding round (planned, open or closed).
- round_get (R0): One record of a funding round (planned, open or closed).
- round_create (W1): Add a funding round (planned, open or closed).
- round_update (W1): Change a funding round (planned, open or closed).
- round_delete (W4): Delete a funding round (planned, open or closed) permanently.
- convertibles_list (R0): List the project's records of a SAFE or convertible note.
- convertible_get (R0): One record of a SAFE or convertible note.
- convertible_create (W1): Add a SAFE or convertible note.
- convertible_update (W1): Change a SAFE or convertible note.
- convertible_delete (W4): Delete a SAFE or convertible note permanently.
- alert_rules_list (R0): List the project's records of an alert rule on a KPI (below, above, or a change of at least delta_pct).
- alert_rule_get (R0): One record of an alert rule on a KPI (below, above, or a change of at least delta_pct).
- alert_rule_create (W1): Add an alert rule on a KPI (below, above, or a change of at least delta_pct).
- alert_rule_update (W1): Change an alert rule on a KPI (below, above, or a change of at least delta_pct).
- alert_rule_delete (W4): Delete an alert rule on a KPI (below, above, or a change of at least delta_pct) permanently.
- incidents_list (R0): List the project's records of an incident (outage, security, customer, financial) with its impact, root cause and mitigation.
- incident_get (R0): One record of an incident (outage, security, customer, financial) with its impact, root cause and mitigation.
- incident_create (W1): Add an incident (outage, security, customer, financial) with its impact, root cause and mitigation.
- incident_update (W1): Change an incident (outage, security, customer, financial) with its impact, root cause and mitigation.
- incident_delete (W4): Delete an incident (outage, security, customer, financial) with its impact, root cause and mitigation permanently.
- kpi_values_list (R0): A KPI's recorded actual values, newest first, each with its source.
- kpi_value_record (W1): Record a KPI's actual value for a period (replaces that period's value). Say where the number comes from.
- kpi_value_delete (W4): Delete one recorded KPI value permanently.
- operating_board_get (R0): How the company is doing: every objective with its health (on_track / at_risk / off_track / unknown) and key results, every active KPI's latest value against where it should be, stale KPIs, milestones due in 14 days or overdue, open and overdue tasks. Health is computed, not judged.
- plan_operating_extract (W1): Fill the operating records from a finished business plan: milestones, KPIs with targets, customer personas, draft objectives and the plan's financial forecast. Runs by itself after every generated or revised plan; this re-runs it. Records the founder edited are left alone. Async (poll plan_status with the job id); no credits. (runs an AI generation.)
- financial_projections_list (R0): A financial scenario's forecast by month and metric.
- financial_projections_upsert (W1): Add or replace a scenario's forecast rows by (month, metric).
- plan_financials_extract (W1): Extract only the plan's financial forecast into the 'plan' financial scenario. Async; no credits. (runs an AI generation.)
- plan_vs_actual_get (R0): Plan against reality: each forecast month next to the recorded actual (matched by KPI key), the variance, cumulative variance and the forecast assumptions the actuals have broken.
- runway_get (R0): Cash, the 3-month average net burn and runway in months at the current burn, plus the zero-cash month under a scenario's forecast. From recorded cash_balance and net_burn values.
- books_stripe_preview (R0): Stripe in the books: the QuickBooks entries for the Stripe account (one journal per finished month: sales, refunds, Stripe fees; one transfer per payout to the bank) and which are already there, with a check that the Stripe account then equals Stripe's balance. Writes nothing; returns the plan_hash to approve.
- books_stripe_apply (W3): Write an approved Stripe-in-the-books preview to QuickBooks. Writes to the founder's accounting outside TOPY: show the preview and always ask first. Refuses if Stripe or QuickBooks changed since the preview; never books twice.
- investor_update_draft (W1): Draft the month's investor update from the records (KPIs, cash and runway, plan vs actual, milestones) plus the highlights, lowlights and asks you give. Saved as a draft investor update; nothing is sent.
- investor_update_send (W3): Email an approved investor update to chosen investor contacts. Sends outside TOPY: always ask first. If email isn't set up, the founder exports it and sends it themselves.
- board_pack_generate (W1): Assemble the board pack for a meeting from the records (objectives, KPIs, finance, milestones, risks, decisions). Saved on the meeting.
- meeting_actions_to_tasks (W1): Turn a meeting's agreed actions into tasks with owners and due dates.
- cap_table_get (R0): The cap table: basic and fully diluted shares, each holder's shares by class and percentage, the option pool and outstanding SAFEs. A record and a model, not the legal register.
- round_simulate (R0): Model a priced round on the current cap table without saving anything: SAFEs convert (lower of cap and discount price), the pool is topped up pre-money, then the new money comes in. Returns everyone's stake before and after.
- data_rooms_list (R0): The project's data rooms, each with its completeness (ready and missing documents).
- data_room_get (R0): One data room: its items by folder (available or still missing) and its shared links.
- data_room_create_from_plan (W1): Create a fundraising data room with the standard folders, filled from TOPY (plan, forecast, KPIs, cap table, personas, latest deck) and placeholders for the documents to upload.
- data_room_item_add (W1): Add an item to a data room: an uploaded file (media_id), text (body), or a live TOPY export (export_ref: {kind: plan|deck|financial_scenario|kpis|cap_table|personas}).
- data_room_item_remove (W1): Remove an item from a data room.
- data_room_link_create (W3): Share a data room with one recipient through a private link (optionally expiring). Shares documents outside TOPY: always ask first.
- data_room_link_revoke (W1): Revoke a data room link at once.
- data_room_views_list (R0): Who opened the data room and which documents, when and for how long.
- deck_estimate (R0): What generating a pitch deck costs in credits against the balance (no charge).
- decks_list (R0): The project's pitch decks.
- deck_get (R0): A pitch deck with its slides (title, bullets, speaker notes, chart data).
- deck_status (R0): Where a deck generation is (queued, running, success, failed).
- deck_generate (W2): Generate a pitch deck from a finished business plan and the current KPIs (8–16 slides with speaker notes). An async job that costs TOPY credits (see deck_estimate); refunded if it fails. (spends TOPY credits; runs an AI generation.)
- deck_update (W1): Change a deck's title or replace its slides.
- deck_export (R0): A deck as Markdown (deck_export_pptx gives the PowerPoint file as a link).
- integrations_list (R0): Connected data sources that fill KPIs automatically, and the KPI queries each offers.
- integration_connect_link (R0): The sign-in link for a data source, to give the founder in the chat: quickbooks and quickfile go straight to their own sign-in; for stripe (a restricted key) and cmo_admin the founder pastes the key in the chat instead (integration_key_connect). Signing in is the founder's; keys are never shared with agents.
- integration_sync (W1): Pull the latest numbers from a connected source into the KPIs bound to it.
- kpi_source_set (W1): Bind a KPI to a data source query so it fills itself (stripe: mrr, active_subscriptions, revenue_monthly, new_customers, churn_rate_monthly; quickfile and quickbooks: cash_balance, revenue_monthly, net_burn, gross_margin; cmo_admin: paid_domains, domain_connection_rate_48h, approval_completion_rate).
- alerts_list (R0): Alerts raised by KPI alert rules and stale KPIs (default: open ones).
- alert_ack (W1): Acknowledge an alert (someone is on it).
- alert_resolve (W1): Resolve an alert, saying what was done.
- cfo_brief (R0): The CFO's daily look, in one call: cash (QuickBooks bank accounts + Stripe), runway from the last 3 months, last month's close, the next filing or tax deadline, alerts, and the health of each CFO goal. Start here.
- cfo_goals_get (R0): The CFO's goals (objectives owned by the CFO under the CEO's goal tree) and the standard ones not set yet: cash safety, books closed on time, zero late filings, healthy unit economics.
- cfo_goals_setup (W1): Set the CFO's standard goals as objectives (owner CFO, with their key results), so every CFO workflow serves a goal. Skips those already set.
- cfo_company_get (R0): The company facts the CFO works from: Companies House number, incorporation date, next accounts and confirmation statement dates, VAT registration, books start, cash floor.
- cfo_company_set (W1): Set the company facts; with a Companies House number the dates are read from Companies House.
- cfo_deadlines (R0): UK deadlines from the company facts: annual accounts, Corporation Tax payments and CT600 returns (a first period over 12 months is split in two), confirmation statement, VAT. Each with days left and status.
- cfo_close_status (R0): The month-end close checklist for a month: Stripe booked and equal to Stripe's balance, no uncategorised transactions, each bank account reconciled to a recorded statement balance, the bank feed empty (checked in Chrome), books locked. Says how to fix each item.
- cfo_bank_balance_record (W1): Record a bank account's statement balance for a day, so the close can reconcile the books to it.
- cfo_management_accounts (R0): Management accounts for a month: profit and loss (with last month and the last 12 months), changes, cash and runway. From QuickBooks and Stripe.
- cfo_report (R0): The CFO's report for one c-level or the board, from QuickBooks and Stripe only: ceo (results, cash, runway, deadlines), cmo (marketing spend by supplier, CAC), cto (infrastructure and software by supplier), cro (sales, MRR, refunds, failed payments), cpo (sales and refunds), coo (recurring suppliers, close status), cso (finance connections, new or large payments, disputes), board.
- cfo_vat_watch (R0): VAT registration watch: taxable turnover over the last 12 months against the £90,000 threshold.
- cfo_share_capital (R0): Share capital still unpaid, by shareholder (from QuickBooks' 'Called up share capital not paid').
- stripe_overview (R0): Stripe now: available and pending balance, MRR, active subscriptions and the last payouts. Also says how to reach Stripe's official MCP for refunds and payment links (TOPY only reads).
- stripe_payouts_list (R0): Stripe payouts with their arrival dates (what reaches the bank).
- stripe_revenue_summary (R0): One month in Stripe: gross sales, refunds, fees, payouts, the change in Stripe's balance, new customers.
- stripe_failed_payments (R0): Open and overdue invoices and failed charges (for the CRO to chase).
- stripe_disputes_list (R0): Stripe disputes (chargebacks) with their status and evidence deadline.
- qbo_report (R0): A QuickBooks report, flattened into lines: ProfitAndLoss, BalanceSheet, CashFlow, GeneralLedger, TrialBalance, AgedReceivables, AgedPayables.
- qbo_accounts_list (R0): QuickBooks chart of accounts with types and balances.
- qbo_vendors_list (R0): QuickBooks suppliers.
- qbo_customers_list (R0): QuickBooks customers (shareholders owing for shares are customers too).
- qbo_transactions_list (R0): QuickBooks transactions of one type in a date range, with their lines and accounts: Purchase, Deposit, JournalEntry, Transfer, Bill, BillPayment, Invoice, Payment, SalesReceipt.
- qbo_vendor_create (W3): Add a supplier in QuickBooks (an existing one with the same name is returned instead).
- qbo_account_create (W3): Add an account to the QuickBooks chart of accounts.
- qbo_journal_create (W3): Book a journal entry in QuickBooks: debits must equal credits, the number must be new (never booked twice), accounts and customers or suppliers by name. For accruals, prepayments, reclassifications and share capital.
- qbo_bank_feed_expectations (R0): What the bank feed should be matched to: every transfer in the books (Stripe payouts, money between the company's own accounts) with its exact date, amount and the bank feed it appears in. QuickBooks' bank feed has no API: a Chrome-driving agent matches each pending line only when date and amount are equal (skill qbo-bank-feed-match).
- qbo_bank_rules_list (R0): The company's bank rules as the CFO keeps them (conditions, category, supplier, expected matches, whether they're created in QuickBooks yet). QuickBooks rules have no API: they're created in Chrome (skill qbo-bank-rules).
- qbo_bank_rules_suggest (R0): Bank rules worth having: each supplier paid lately with the account it's always booked to (one-offs get an exact-amount condition). Check the bank text with Test rule before saving in QuickBooks.
- qbo_bank_rule_save (W1): Save a bank rule to the CFO's list (checks the account and supplier exist in QuickBooks). Status proposed until it's created in QuickBooks in Chrome, then save it again with status applied.
- coo_health (R0): Is the company running by itself: when the Routine scheduler last ticked, runs and failures in the last 24 hours, what waits on the Founder, and whether approval links and email are set up.
- coo_routines (R0): Every AI cofounder's active Routines: trigger, whether the scheduler runs it, next run, missing inputs and the last run.
- coo_runs (R0): Recent Routine runs from the scheduler's log, newest first.
- coo_waiting (R0): Runs paused on the Founder: what each waits for, since when, and when its approval link expires.
- coo_efficiency (R0): How well the Routines run: runs, success rate, retries and cost over the last days, by cofounder, and the steps that fail most.
- coo_schedule_check (R0): Check every scheduled Routine: runs a day, starts on the hour, starts that clash, the daily cap, missing inputs and Routines that never report.
- coo_schedule_plan (R0): Plan a Routine's schedule: check a cron in a timezone, list the next runs and any clash with the Routines already scheduled. It plans only; the Routine file holds the trigger.
- coo_find_automation (R0): Find repeated manual tasks (3 or more times) worth turning into a Routine.
- coo_evaluate (R0): Compare vendors, contractors or tools: weighted fit, and value for money when costs are given.
- coo_status_report (R0): The COO's status report for the CEO: its KPIs (Routine success rate, Founder minutes per outcome) with source and date, blockers, asks and risks; null with a reason where there is no data.
- coo_resources (R0): The servers' resources: every mount's disk and inodes, memory, swap and load per core on the company's servers (with the Founder's read-only consent) and the OneMan host, the biggest memory users, and how fast each disk grows (full in about N days). 80% is noted, 90% urgent.
- coo_server_jobs (R0): The servers' scheduled work: pm2 processes not online or restarted since the last check, systemd services enabled but not running, failed units and timers, crontab entries.
- coo_publishing (R0): The publishing schedule on the chosen cmo.so websites: blog delivery (paused, overdue, quota), the autopilot's daily jobs and the social queue (overdue or failed posts, drafts waiting).
- coo_retry_failed (W1): Rerun failed Routines once a day when it is safe: the run failed on a read, nothing was sent or written outside, and it wasn't a permission or token error. The rest are listed for a person.
- coo_remind (W1): Email the Founder again about runs that have waited longer than older_than_hours (default 24), each with a fresh one-click approval link; once a day per run.
- coo_report_send (W1): Gather and send the operations report now: daily (health, failures, waiting; only when something needs attention) or weekly (plus 7-day efficiency and the schedule check), to the Founder by email or to the CEO.
- coo_routine_run (W1): Run one AI cofounder's Routine now, logged like a scheduled run. Its steps that need the Founder still stop for the one-click approval.
- cso_doctor (R0): What applies to this project: site type, domains, which checks run, scanners and feeds, verified domains, granted hosts, the findings ledger.
- cso_scan (R0): A full security check in one step: the right detectors for the project (inventory, vulnerabilities, dependencies, secrets, code, end-of-life; web checks for a verified domain), then a report.
- cso_report (R0): The security report: a one-line verdict, what to do this week (p0 first), what was fixed and what was checked.
- cso_vuln_watch (R0): New vulnerabilities against what the project runs: OSV, Node core, CISA KEV (exploited now), EPSS, end-of-life; new versus already reported.
- cso_osv_query (R0): Look up a package, a version or an advisory (CVE / GHSA) in OSV.
- cso_deps (R0): Known vulnerabilities in every lockfile ecosystem and JavaScript copied into the site.
- cso_secrets (R0): Keys and passwords in git history, files and build output: where (file, line, a preview), never the value. Rotate first, then remove.
- cso_code_scan (R0): Unsafe code patterns (injection, unsafe deserialisation, personal data in logs, …).
- cso_headers (R0): Grade a verified site's HTTP security headers and cookies (A+ to F).
- cso_tls (R0): TLS protocols, certificate trust and expiry for a verified host.
- cso_eol_watch (R0): Runtimes, databases, servers and distributions past end of life or behind on patches.
- cso_skills_scan (R0): Vet a skill or an MCP server before it is trusted (the App Factory gate).
- cso_mcp_self_check (R0): OWASP MCP checks on our own tool registry.
- cso_checklist (R0): The OWASP ASVS 5.0 checklist from the findings.
- cso_threat_model (R0): A STRIDE threat model draft for the project.
- cso_ledger (R0): The findings ledger: each finding's status (open, fixed, accepted until …, false positive).
- cso_inventory (R0): The stack inventory: lockfiles, manifests, images, runtimes, WordPress.
- cso_uptime_status (R0): Uptime and certificate expiry from the status monitor.
- cso_status_report (R0): The CSO's status report for the CEO: open critical exposure, policy violations (null with a reason where there is no source), blockers and asks.
- cso_fix_plan (W1): A reviewed remediation runbook from the findings, each step tagged with a fix-risk tier (T1 batch-safe to T4 stage first). A person applies it under the host lock; it is never applied here.
- cso_domain_verify (W1): Prove the company controls a domain before any active check: start (gives the DNS TXT or file to add), check, status or revoke.
- cso_web_scan (W1): A safe scan (nuclei, no exploitation) of a site on a verified domain; it sends requests to that site.
- cso_incident (W1): Keep an incident's timeline (local records only): start, log an event, close, show or list.
- cso_report_send (W1): Run the watch and the report now and send them: daily (only when something is urgent unless always) or weekly, to the Founder by email or to the CEO.
- cro_review (R0): The weekly revenue review: MRR, ARR, subscriptions and last month's revenue (AI CFO), the open pipeline and its value, deals that need attention, won and lost in 30 days, win rate and revenue at risk from failed payments.
- cro_status_report (R0): The CRO's status report for the CEO: KPIs (MRR, new customers, churn, NRR, pipeline value, win rate; null with a reason where there is no source), risks and asks.
- cro_pipeline (R0): Leads and deals by stage, with amount, next step, close date and contact basis.
- cro_dunning (R0): Failed and overdue payments (AI CFO) and the recovery step for each by age: day 3 reminder, day 7 notice, day 14+ the Founder decides. Never charges or refunds.
- cro_funnel (R0): Visitors → signups → paid: conversion at each step and the biggest drop-off.
- cro_forecast (R0): MRR, ARR, LTV and LTV:CAC from subscribers, ARPA, monthly churn and CAC.
- cro_lead_capture (W1): Capture a lead with its source and lawful contact basis (opt_in, existing_customer, legitimate_interest; 'none' is stored but can never be contacted). Never scraped or bought lists.
- cro_lead_qualify (W1): Score a lead (BANT-lite: business email, company, budget, authority, timeline) and route it: 60+ qualified, 30–59 nurture, below keep warm.
- cro_deal_update (W1): Move a deal one stage along the ladder (up to negotiation) and keep its amount, close date and next step. Proposal needs an amount, negotiation a close date; won and lost are the Founder's.
- cro_quote (W1): A quote with the deal desk applied: a discount above the ceiling (20%) or a total above the approval amount (£5,000) is marked for the Founder with the reason.
- cro_outreach_draft (W1): Draft one message for a lead with a lawful contact basis: value first, a clear ask and an opt-out. It is kept on the deal; sending it is the Founder's on OneMan.
- cro_unsubscribe (W1): Stop all outreach to a person at once and for good (every lead with that email).
- cro_pricing_plan (W1): A pricing and packaging plan: value metric, tiers, annual plan, one change at a time. Changing a live price is the Founder's.
- cro_report_send (W1): Run the revenue review and the dunning plan now and send them to the Founder by email or to the CEO.
- cpo_review (R0): The weekly product review: feedback themes and what waits to be triaged, why deals were lost (AI CRO), the project's product KPIs (a KPI with no value is 'no data'), experiments, decisions and what needs attention.
- cpo_status_report (R0): The CPO's status report for the CEO: activation, weekly active users, PMF (null with a reason where there is no source), risks and asks.
- cpo_feedback_list (R0): Feedback by status or theme, with the theme counts (stored de-identified).
- cpo_decisions (R0): The decision log (why, evidence, falsifier) and the decisions due for a revisit.
- cpo_experiments (R0): Experiments (pre-registered metric, sample, stop rule) and those due for a read-out.
- cpo_prioritize (R0): Rank features by RICE: reach × impact × confidence ÷ effort, shown per feature.
- cpo_experiment_size (R0): The sample per variant and the days an A/B test needs (α 0.05, power 0.8).
- cpo_pmf_plan (R0): A product–market-fit plan: the ICP and job, the survey (40% 'very disappointed'), the metrics to watch.
- cpo_positioning (R0): A positioning statement: for whom, the need, the category, the benefit, unlike what.
- cpo_feedback_add (W1): Record feedback with its source and kind; emails and phone numbers are masked.
- cpo_feedback_triage (W1): Triage one item: accept, reject, duplicate (say of what) or needs_info; a size; the owner is a person whenever it touches billing, sign-in, permissions, security, privacy, legal text, a paid build or deleting data, or isn't small.
- cpo_decision_log (W1): Log a product decision with why, the evidence and its falsifier (what would change our mind); revisit_on brings it back.
- cpo_experiment_start (W1): Pre-register and start an experiment: hypothesis, primary metric, baseline, MDE, sample and stop rule — fixed before any data.
- cpo_experiment_read (W1): Read an experiment: before the planned sample it says keep running; after it, the effect with a 95% interval and p-value (flat is a result).
- cpo_spec (W1): A PRD: problem, users, evidence, goals, non-goals, risks, rollout, the success metric and how it is measured, open questions. Not ready without a success metric.
- cpo_roadmap (W1): The roadmap now / next / later, ordered by value ÷ effort; save keeps it for the review.
- cpo_build_check (W1): Build or not, before the CTO: reuse, a Routine, a private or a reusable Service App.
- cpo_report_send (W1): Run the product review now and send it to the Founder by email or to the CEO.
- cto_status_report (R0): The CTO's status report for the CEO: uptime and deploy frequency (null with a reason where there is no source), risks and asks.
- cto_health (R0): Health of the services the company runs (each one up or down, with its latency).
- cto_github (R0): The GitHub connection: the TOPY AI GitHub App, where it is installed and whether webhooks arrive.
- cto_repos (R0): Repositories the App can reach on an account or org.
- cto_repo (R0): One repository: default branch, visibility, last push.
- cto_commits (R0): Recent commits on a branch or path.
- cto_compare (R0): Commits and changed files between two refs.
- cto_prs (R0): Pull requests.
- cto_pr (R0): A pull request with its changed files.
- cto_pr_checks (R0): A pull request's checks: passing, pending or failing, and which failed.
- cto_ci_runs (R0): GitHub Actions runs, by branch, status or commit.
- cto_ci_run (R0): One run with its jobs and the steps that failed.
- cto_ci_log (R0): The part of a job's log that explains the failure.
- cto_checks (R0): Checks on a commit or branch: passing, pending or failing.
- cto_issues (R0): Issues.
- cto_releases (R0): Releases.
- cto_release_notes (R0): Draft release notes from the commits since the last release; nothing is written.
- cto_alerts (R0): Dependabot, code-scanning and secret-scanning alerts; a kind GitHub won't show comes back as not read, with GitHub's reason (never as zero).
- cto_events (R0): Webhook events received from GitHub (pushes, pull requests, workflow runs, releases, installation changes).
- cto_issue_create (W1): Open an issue (no personal data in it).
- cto_issue_comment (W1): Comment on an issue.
- cto_pr_comment (W1): Comment on a pull request.
- cto_ci_rerun (W1): Re-run a workflow run (the failed jobs only, unless failed_only is false).
- team_status (R0): Who is on the Founder's team of AI cofounders here (for this project, or the account), what each does, how many tools each brings, and who could join. Start here when the user asks what their cofounders can do.
- team_catalog (R0): Every AI cofounder that can join the team (CEO, CFO, COO, CSO, CTO, CPO, CRO), what each does and whether it is on the team. The AI CMO is cmo.so, installed separately.
- team_add (W1): Add AI cofounders to the team: their tools appear here after the client reconnects.
- team_remove (W1): Take AI cofounders off the team: their tools leave this server (nothing of theirs is deleted). The CEO stays.
- routine_list (R0): The project's routines, whatever runs them: TOPY-AI-Routines template instances (runner oneman, claude_ai), OneMan's built-in workflows and Maggie's Ops Autopilot. Each with its owner, status, schedule, daily write limits and last run. Filter by runner, status or kind (template, builtin, autopilot).
- routine_get (R0): One routine of the project, by id or key (e.g. 'yian.uk/cro-weekly-forecast').
- routine_propose (W1): Propose a routine for the project from a TOPY-AI-Routines template: it is saved as proposed and nothing runs until the founder (or the CEO within the delegation) approves it. Say why, with the evidence.
- routine_decide (W2): Decide on a routine: approve or resume switches it on, pause stops it, retire ends it, decline drops a request waiting on the founder. The founder's decision runs at once. A scheduled CEO's runs only within the project's delegation (delegation_get) and goes into the decision log; outside it, it waits on the routine as a request for the founder. Give the reason with the evidence.
- delegation_get (R0): The founder's delegation on this project: what the scheduled CEO may decide about routines on their behalf (approve or resume, pause, which runners, owners and templates, how many active, how often a day). Set with delegation_set, revoked with delegation_revoke (the founder's decision).
- task_progress (W1): Move a cofounder's task on — todo, in_progress or done — with a dated note (what happened, the evidence: an issue closed, a pull request merged). Only tasks a cofounder owns (details.owner_role); the founder's tasks are theirs.
- routine_update (W2): Change a routine: approve, activate, pause or retire it, move its time, lower its limits. The person's decision: an agent's key can't.
- founder_todos_list (R0): The founder's own list: what only they can do (decide, contact someone, keep a relationship warm, an event or visit), most urgent first, with each item's why, brief, window, expiry, planned slot and, once done, how it went. status: live (default), all, done, skipped, expired.
- founder_day_get (R0): The founder's day (default today): their timetable, the calendar's events, the free slots between them, the items planned for the day and the rest by urgency, and what was done today.
- founder_todo_add (W1): Add something only the founder can do to their list, with why now and, for people, a brief (context, talking points, an opener, the ask, what to bring). The same dedupe_key updates instead of adding twice; something the founder handled in the last 30 days isn't added again. Never contact anyone yourself.
- founder_todo_update (W1): Change an item on the founder's list: plan it into a slot (slot_start/slot_end), re-rank it, update its brief or window, mark it expired; the founder marks it done, snoozed or skipped with an outcome.
- contacts_list (R0): The founder's people for this project (customers, shops, partners, community, investors, people who introduced them): role, how they met, warmth, importance, what they care about, promises and the last contact. due: true lists those going cold (not heard from the founder within their rhythm), most overdue first.
- contact_get (R0): One of the founder's contacts with their last 20 interactions.
- contact_upsert (W1): Add someone to the founder's contacts, or update them (the same source, or the same name and organisation, updates). Only facts from TOPY's records or the founder's own words; never guess how to reach anyone.
- contact_log (W1): Log a conversation the founder had with one of their contacts (what was said, what comes next); their last contact moves. A to-do marked done for a contact logs itself.
- google_calendar_status (R0): The founder's Google Calendar as connected through topy.ai: the account, its calendars (and which count as busy time), and whether changes are allowed (can_write).
- google_calendar_events (R0): Events on the founder's chosen Google calendars between from and to (default the next 7 days): id, calendar_id, title, start, end, location, and added_by_topy (true for events a cofounder added).
- google_calendar_event_add (W1): Put an event on the founder's Google Calendar (default the primary calendar): a hold for something on their list, a reminder, a slot for a call they asked for. Never with guests — no invitation is sent; times in the founder's time zone. It is marked as added by topy.ai so it can be changed later.
- google_calendar_event_update (W1): Move or change an event a cofounder added (title, times, place, notes, busy/free). The founder's own events can't be changed by a cofounder.
- google_calendar_event_delete (W2): Remove an event a cofounder added from the founder's Google Calendar (the founder's own events can't be removed by a cofounder).
- founder_memory_get (R0): What the cofounders know about the founder as a person: preferences, habits, strengths, growth areas (with how to practise), energy (when they work best), boundaries and their own goals. status: active (default, confirmed by the founder), candidate (suggested, waiting for them) or all. Use it to fit plans to the founder and help them grow. role: one cofounder's share (notes for them or for everyone, with for_you: what it means for their work).
- founder_memory_suggest (W1): Suggest something about the founder as a person (a preference, habit, strength, growth area, energy pattern, boundary or goal) with the evidence. It waits as a candidate until the founder confirms it; never store anything private beyond working life, and nothing they didn't show or say. The CEO keeps it for the whole team: roles says which cofounders it matters to and guidance what it means for each one's work. When outcomes show an active note is out of date, suggest the revision with replaces (or retire: true to drop it).
- delegation_set (W2): Set the founder's delegation on this project: what the scheduled CEO may decide about routines on their behalf (approve or resume, pause, which runners, owners and templates, how many active, how often a day) and its authority over Maggie (all, internal or ask). The founder's decision.
- delegation_revoke (W2): Revoke the founder's delegation on this project: every routine decision waits on the founder again.
- standing_permission_grant (W2): Let an agent key add records on this project without a preview, up to a daily cap per tool (standing_permissions_list shows which tools are eligible). Default: the key making the call. The founder's decision.
- standing_permission_revoke (W2): Revoke a standing permission (standing_permissions_list): that key asks again.
- founder_preferences_get (R0): The founder's timetable: time zone, place, working hours and days, out-and-about days, how many items a day, when the day plan comes and where (slack or dashboard), and notes.
- founder_preferences_set (W1): Change the founder's timetable (only the fields given change). The founder's decision.
- google_calendars_choose (W1): Which of the founder's Google calendars count as busy time (ids from google_calendar_status).
- google_connect_link (R0): The Google sign-in link for the founder: Google Calendar, plus the ONEMAN service agents given in apps (gmail, drive, sheets, forms, tasks, contacts, analytics). Give the founder the link; signing in is theirs.
- calendar_feed_connect (W2): Connect a calendar by its private feed (an iCal URL), read only, for the day plan.
- calendar_feed_disconnect (W2): Remove a connected calendar feed.
- integration_disconnect (W3): Disconnect a data source from this project (stripe, quickbooks, quickfile, cmo_admin): its KPIs stop syncing. The founder's decision.
- company_domain_set (W2): Bind the project's company domain: the cofounders' company context is built from that website.
- company_context_edit (W2): Edit the company context every cofounder works from: company fields, or what one cofounder should know (roles: {role: text}).
- company_context_regenerate (W2): Rebuild the company context from the website (replace_edited: also overwrite edits).
- founder_memory_edit (W1): Edit a note about the founder (text, practice, kind, roles, guidance) or archive it (status archived). The founder's decision.
- integration_key_connect (W2): Connect a data source with the key the founder pasted in this chat: stripe (a restricted key with read access to subscriptions, invoices and customers), quickfile (a personal API token) or cmo_admin (a cmo.so admin key). Its KPIs then fill themselves. Never repeat the key back.
- service_keys_list (R0): Which outside services have the founder's keys on topy.ai (for ONEMAN's service agents: devto, datafast, sentry, posthog, notion, cloudflare …) and the key names. Never the values.
- service_key_set (W2): Keep the founder's key for an outside service, which they gave in this chat, for ONEMAN's service agents (devto: DEVTO_API_KEY; datafast: DATAFAST_API_KEY or DATAFAST_SITE_KEYS; sentry: SENTRY_TOKEN, SENTRY_ORG; posthog: POSTHOG_PERSONAL_API_KEY, POSTHOG_PROJECT_ID; notion: NOTION_TOKEN; cloudflare: CF_API_TOKEN, CF_ACCOUNT_ID, CF_SITE_TAG). Saved encrypted; never repeat the value back.
- service_key_remove (W2): Forget the founder's keys for an outside service.
- plan_export_word (R0): A link to the business plan as a Word file (15 minutes, no sign-in): give it to the founder.
- seis_export_word (R0): A link to the SEIS Advance Assurance application as a Word file, from the text plan_seis_assurance returned (15 minutes, no sign-in): give it to the founder.
- deck_export_pptx (R0): A link to the pitch deck as a PowerPoint file (15 minutes, no sign-in): give it to the founder.
- project_section_suggest (R0): AI rewrite of one section of the project profile with an instruction (as the profile page does): returns the edited section and a note; nothing is saved until project_update.
- media_upload (W1): Upload a picture the founder gave in the chat (JPEG, PNG, GIF or WebP, at most 10 MB) to their TOPY media; returns its media id and URL.
- project_create_from_document (W2): Create a project from a document the founder gave in the chat (PDF, Word or text): TOPY reads it and fills the profile (a job: project_job_get).
- data_room_document_add (W1): Put a document the founder gave in the chat (PDF, Word, text or Markdown) into a data room folder, as its text.
- credits_buy (W1): A Stripe checkout page to buy a TOPY credit pack (entitlements_get lists them). Give the founder the link: paying happens on Stripe.
- plan_subscribe (W1): A Stripe checkout page to subscribe to a TOPY plan. Give the founder the link: paying happens on Stripe.
- billing_portal (W1): The Stripe billing portal for the founder's subscription (change, cancel, invoices, card).
- site_status (R0): The founder's personal site: claimed subdomain and custom domains with their status (claims and hostnames), and LinkedIn verification.
- site_hostnames (R0): The site's hostnames (subdomain and custom domains) with ids and DNS / certificate status.
- site_subdomain_available (R0): Whether a subdomain label is free.
- site_subdomain_claim (W2): Claim a subdomain for the founder's site.
- site_custom_domain_add (W2): Connect the founder's own domain to their site (gives the DNS records to add).
- site_custom_domain_status (R0): A custom domain's DNS and certificate status.
- site_hostname_remove (W3): Remove a hostname from the founder's site.
- site_context (R0): What the site builder knows (profile, sections, presets) to plan a site.
- site_generate (W2): Generate the founder's site with AI from their profile and a brief (a draft to preview).
- site_preview (W1): Render a preview of the site with the given content (nothing is published).
- site_publish (W2): Publish the reviewed site to the founder's hostnames.
- site_templates (R0): Community site templates to start from.
- site_template_publish (W2): Publish the site from a community template.
- site_bio_edit (W1): Edit the site's bio with an instruction (AI).
- site_element_edit (W2): Change one element of the live site with an instruction (AI).
- site_homepage_get (R0): The site's homepage content.
- site_homepage_set (W1): Change the homepage content (a draft until published).
- site_homepage_publish (W2): Publish the homepage.
- site_posts_list (R0): The posts on the founder's site (drafts and published).
- site_post_generate (W1): Draft a post with AI (a preview: nothing is saved).
- site_post_save (W1): Save a post on the site as a draft.
- site_post_update (W1): Change a post.
- site_post_delete (W3): Delete a post.
- site_post_publish (W2): Publish a post on the site.
- site_post_unpublish (W2): Take a post off the site.
- linkedin_connect_link (R0): The LinkedIn sign-in link to verify the founder (claim) or to let the site publish to LinkedIn (publishing). Signing in is theirs.