On .bloom*, Ivy plans sessions across 500+ biomedical tools and 50+ databases, and every result names the tool, parameters and run that produced it.
Fold, dock, screen and plan the synthesis — in one question. Ask Ivy and it plans the run, submits each job and feeds its output into the next — from the browser, the ivybloom terminal, curl, or your agent over MCP — or curl a single job yourself. On .bloom*, Ivy plans sessions across 500+ biomedical tools and 50+ databases — for you or your agent. Every result names the tool, parameters and run that produced it. You leave with what the run made — a structure, a ranked table, an export. Signed-in runs from the web app, the terminal, curl or MCP leave a tamper-evident record you can check. The web app, curl to /api/v1/orchestrate, the ivybloom terminal app and any MCP client all reach Ivy; a single tool job can also be dispatched directly with curl to /api/v1/jobs, ivybloom run, or a studio project.