How the platform fits together in 90 seconds — one request becomes tools, a recorded run, and an artifact you can keep.

The platform turns a plain-language request into computational biology results. You describe a goal — fold this protein, dock this ligand, profile this compound — and the orchestrator picks the right tools, runs them, and returns a recorded result as an interactive card or export. This page is the 90-second map; the rest of the docs fill it in.

The shape of a request

Every request follows the same path, whether you type it in Chat, paste a curl request, use the CLI, or connect an MCP client. Studio is the project surface for direct control over files and parameters.

From a plain-language goal to jobs, canvas cards, campaigns and passports.

The five nouns in that path — tool, job, canvas card, campaign, passport — are the core vocabulary. Concept clusters groups them so they fit on one page.

Same registry, four ways in

Every surface reaches the same .bloom* registry, so pick by how you work. curl is the first call: no install, no key, no account. An API key needs a free account and adds your own quota and sessions you can resume. MCP and the CLI need the ivybloom CLI, installed and signed in.

Chat runs the same tools from the browser. Once you are signed in, Studio is a project workspace for direct control over files and parameters.

curl / API

Paste a guest request without an account, or add a key for sessions you can resume.

MCP server

Let an AI coding agent call the same registry through the Model Context Protocol.

ivybloom CLI

Scriptable batch processing, CI/CD, and reproducible pipelines from your terminal.

Chat

Start a run from the browser. Type a goal; the orchestrator picks and chains the tools.

Choose what to learn first

See what you can achieve

The outcomes the platform delivers, and which tool fits each.

Run your first job

Try a guest run, then create an account and chain a workflow.

Learn the vocabulary

Tools, jobs, cards, campaigns, passports — five clusters, one page.

Find the right tool

Match a scientific goal to the tool or workflow that answers it.

What these docs cover

This site documents the platform — Chat, curl/API, Studio, CLI, MCP, tools, workflows, and passports — plus the execution model behind each run. If you are deciding between close-cousin concepts (chat vs. studio, tool vs. workflow, job vs. batch), start with Decisions.

Platform overview