Launches
Upvoted
Comments
Commented on Raziel · Nov 8, 2026
Thanks, really glad it's useful! Right now it's one snapshot at a time: you enter paid-in, cumulative distributions and NAV as of a single date, and it returns TVPI, DPI and RVPI for that point. To see the shift over time, run it once per capital account statement (say each quarter) and line the results up. You'll watch RVPI shrink and DPI grow as exits come in, while TVPI stays roughly flat unless marks change. If you'd rather script it, the same calculator is in our free API and MCP server (tvpi_dpi), no API key needed: raziel.co/developers. Loop it over your quarterly numbers and you've got the time series. A built-in multi-date view is a great idea though. Adding it to the list. :)
Commented on Raziel · Nov 8, 2026
Yes, the QSBS calculator reduces the per‑company cap by any gain you have already excluded from that company in earlier years. More: https://raziel.co/tools/qsbs-calculator
Commented on Raziel · Nov 5, 2026
Good question. The easiest way is to import the OpenAPI spec: in Postman or Insomnia, choose Import and paste https://raziel.co/api/openapi.json. That gives you a ready-made collection with every calculator, its input schema and an example body, so you can hit Send right away. No API key or auth setup needed. A typical flow: GET /api/v1/calculators/safe_conversion returns the schema and an example, then you POST the same path with your own numbers. It’s handy for checking the math before you wire it into an agent, or for saving a set of test cases (say an IRR with irregular cash flows) to rerun later.
Commented on Raziel · Nov 5, 2026
Thanks Aditya. Today it’s one SAFE per call: you send the cap, discount and SAFE type (pre or post-money) along with the priced round, and it returns that SAFE’s conversion price, shares and ownership, including any pool top-up. For a stack with different terms, an agent can call it once per SAFE, but that doesn’t capture how post-money SAFEs dilute each other when they convert together. Converting a full stack in one call is the right next step, so it’s on our list: an array of SAFEs in, a per-holder cap table out. Appreciate the SERP check too. YC’s own calculator owning page 1 makes sense, and being the one with an API is how we want to stand out.
Commented on Raziel · Nov 5, 2026
Thanks! That’s exactly why we built it. When an AI assistant estimates IRR or SAFE conversion in its head, it’s often a little off. With the MCP server it calls the real calculator and gets the exact number, plus the inputs it used, so it can explain the result. It’s free with no key at raziel.co/mcp if you want to plug it into Claude or Cursor.
Commented on Raziel · Nov 5, 2026
You can copy the URL for each set of inputs – each scenario is saved in the page URL, so you can open separate links and compare them side‑by‑side. More: https://raziel.co/tools/dilution-calculator
Commented on Raziel · Nov 4, 2026
Yes, our XIRR calculator uses the same equation as Excel and Google Sheets and returns the same results for irregular cash‑flow dates. More: https://raziel.co/tools/xirr-calculator
Commented on Raziel · Nov 3, 2026
Thanks! Every request is validated before any math runs. Bad input gets an HTTP 400 with a plain-English message naming the field to fix, never a guessed number: - invested_usd: 0 → "invested_usd" must be greater than 0. - Missing field → "value_returned_usd" is required. - A typo'd field → Unknown field "foo". Allowed: invested_usd, value_returned_usd, years. Errors always come back as { "ok": false, "error": "..." }, so you only need to check ok. If one output is undefined (like an annualized return over 0 years), that value comes back as null instead of failing the whole request. The MCP server uses the same validation, so AI agents can read the message and fix their own input.
Commented on Raziel · Nov 1, 2026
We built the Raziel Calculators API so developers can add precise finance math to apps and AI assistants without managing keys or storing data. It exposes 25 free calculators, guide search, a glossary, and an MCP server via simple HTTP/JSON. Could you try the MOIC calculator POST request and let us know what, if anything, breaks?