Use Cases
Serial entrepreneur
Fourth or fifth company. Applies a saved template, reuses a single registered agent across the portfolio, expects everything to work the same way it did last time.
Last updated
A repeat founder spinning up the next company. They have a saved formation template — share structure, par value, bylaws toggles, registered-agent vendor, default webhook destinations — and a portfolio of prior entities. They don't want to re-decide anything they decided last time. The whole API surface is built around template_id, the Portfolio resource, and cross-entity reuse.
Create
Bring the entity into existence — formation, founder equity, EIN, registered agent.
You don't fill out a fresh formation packet — you instantiate from your saved template. The new entity inherits your share-class, par value, bylaws toggles, default webhook destinations, and your shared registered agent. Your only inputs are the new entity's name, a one-liner, and the portfolio it joins.
POST /v1/entitiesOne template_id, one portfolio_id, one company name. The new entity inherits every field your prior entities use. The intent resource carries a template_provenance back-reference so the lineage is queryable.
POST /v1/registered_agents/{id}/attachAttach the new entity to the existing RegisteredAgent resource. The RA contract amends to add the entity rather than re-signing; billing reflects bundled-portfolio pricing rather than a per-entity fee.
POST /v1/entities/{id}/share_classesApply the saved ShareClassTemplate — single class of common, your preferred authorised count, your preferred par value, any baseline rights/preferences you've standardised across the portfolio. The founder issuance ledger records 100% to you in one call.
POST /v1/entities/{id}/equity_plansApply the saved EquityPlanTemplate — option-pool size, default vesting (4 / 1), exercise window, 409A cadence, plan-document body. The plan exists in a ready state with zero issued grants until you hire.
Manage
Operate the live entity — equity programs, board cadence, compliance, qualifications.
The first customer contract instantiates from your saved MSA; the first SAFE instantiates from your saved variant. Counter-parties and stakeholders dedupe at the portfolio level so one customer paying two of your entities shows up once. The portfolio compliance rollup returns one calendar across every live entity.
POST /v1/documentsGenerate the contract from your saved template_id. Counter-party-specific fields (name, address, amount, term) are the only inputs; limitation-of-liability, indemnification, IP-ownership, governing-law all come from the template. The counter-party records at the portfolio level, deduped across entities.
POST /v1/convertiblesSaved variant, saved cap-derivation rule, saved side-letter clauses (pro-rata, information rights). The valuation cap is the only field you supply at issuance; everything else is template-resolved.
GET /v1/portfolios/{id}/complianceOne query returns the unified upcoming-filings calendar across every live entity, the next-30-days deadlines per entity, a stale-entity flag for anything inactive past N months, and your effective ownership across the portfolio. The companion endpoint /cap_table_rollup does the same for cap-table aggregation.
Exit
Wind the entity down — dissolution cascade or M&A envelope.
When one of your prior entities goes stale, preview the wind-down before committing. The full dissolution envelope lives in the wind-down walkthrough — this preview surface is the on-ramp.
GET /v1/entities/{id}/dissolution_readinessRead-only. Returns the required filing sequence (Form 966 → final franchise tax → Certificate of Dissolution → BOI closure), any blockers (open contracts, unresolved compliance, employees on the books), and an estimated total cost. No state mutation. Schedule the dissolution when you're ready.