Loading
Corbis is a research workspace built for source-backed analysis. You can use it for open-ended chat, structured workflows, project-based research, and organization access.
This guide walks you through the first steps in plain language.
New accounts usually land on chat after sign-up or login.
Before you start chatting, the app may ask you to:
Complete those steps when they appear. Then you are ready to use New Inquiry or Past Inquiries in the sidebar to work in chat.
Use the left sidebar as your map:
/projects. Expand it to see recent projects./workflows for a full catalog and overview of the same workflows.Settings (avatar or app menu) includes tabs such as Billing, Team (for org admins), and API Keys. MCP connection keys are created in Settings → API Keys, in the MCP section of that tab.
Use New Inquiry in the sidebar, or go to /chat. If you are not signed in, you will be sent to log in and then returned to chat.
On a new chat, you will see starter prompts and skills you can tap to pre-fill a first message. That is often the fastest way to send a useful opening question.
Concrete questions work better than very broad ones. For example:
Corbis is meant to show its work. When a reply includes citations or data references:
You do not need to start over each time. Follow-ups like these usually work well:
/workflows).Corbis can pull academic papers, economic data, and market context when tools support it, and answer with citations or linked sources when that path applies.
A project is a workspace that can hold:
For multi-day or multi-document work, move it into a project early.
More detail: How to Use Projects.
Workflows are guided runs for repeatable tasks. The app currently ships these five:
More detail: Guide to Structured Workflows.
Plans: Structured workflows use a monthly workflow allowance that depends on your subscription or organization seat. On the Free tier, workflow runs are not part of the included allowance (see Plans & Pricing and Settings → Billing for what applies to your account). If you are on Free, explore workflows after you upgrade or join a team whose plan includes them.
When an output supports downloads, export actions show up in the surrounding UI.
If your team uses Corbis through an organization, billing and access may be managed by an admin instead of only by you.
More detail: Organization Memberships.
To use Corbis tools from an MCP client, create a key under Settings → API Keys (MCP keys appear in that tab).
More detail: Understanding MCP Tools.
/workflows. If you are on Free, check Plans & Pricing or Settings → Billing before expecting to run structured workflows.No. Start in chat. Use a project when the work needs shared files, shared instructions, or saved papers kept in one place.
Use a workflow when you want the app to hold a fixed process for you. Use chat when you want maximum flexibility.
Use Settings → Billing, or read the public Plans & Pricing page.
Organization admins use Settings → Team.
Most full product use requires sign-in. Some deployments allow limited guest access; if you see a guest entry path, treat it as optional and environment-specific.
Corbis is a research workspace built for source-backed analysis. You can use it for open-ended chat, structured workflows, project-based research, and organization access.
This guide walks you through the first steps in plain language.
New accounts usually land on chat after sign-up or login.
Before you start chatting, the app may ask you to:
Complete those steps when they appear. Then you are ready to use New Inquiry or Past Inquiries in the sidebar to work in chat.
Use the left sidebar as your map:
/projects. Expand it to see recent projects./workflows for a full catalog and overview of the same workflows.Settings (avatar or app menu) includes tabs such as Billing, Team (for org admins), and API Keys. MCP connection keys are created in Settings → API Keys, in the MCP section of that tab.
Use New Inquiry in the sidebar, or go to /chat. If you are not signed in, you will be sent to log in and then returned to chat.
On a new chat, you will see starter prompts and skills you can tap to pre-fill a first message. That is often the fastest way to send a useful opening question.
Concrete questions work better than very broad ones. For example:
Corbis is meant to show its work. When a reply includes citations or data references:
You do not need to start over each time. Follow-ups like these usually work well:
/workflows).Corbis can pull academic papers, economic data, and market context when tools support it, and answer with citations or linked sources when that path applies.
A project is a workspace that can hold:
For multi-day or multi-document work, move it into a project early.
More detail: How to Use Projects.
Workflows are guided runs for repeatable tasks. The app currently ships these five:
More detail: Guide to Structured Workflows.
Plans: Structured workflows use a monthly workflow allowance that depends on your subscription or organization seat. On the Free tier, workflow runs are not part of the included allowance (see Plans & Pricing and Settings → Billing for what applies to your account). If you are on Free, explore workflows after you upgrade or join a team whose plan includes them.
When an output supports downloads, export actions show up in the surrounding UI.
If your team uses Corbis through an organization, billing and access may be managed by an admin instead of only by you.
More detail: Organization Memberships.
To use Corbis tools from an MCP client, create a key under Settings → API Keys (MCP keys appear in that tab).
More detail: Understanding MCP Tools.
/workflows. If you are on Free, check Plans & Pricing or Settings → Billing before expecting to run structured workflows.No. Start in chat. Use a project when the work needs shared files, shared instructions, or saved papers kept in one place.
Use a workflow when you want the app to hold a fixed process for you. Use chat when you want maximum flexibility.
Use Settings → Billing, or read the public Plans & Pricing page.
Organization admins use Settings → Team.
Most full product use requires sign-in. Some deployments allow limited guest access; if you see a guest entry path, treat it as optional and environment-specific.