Research Mode

What Research Mode grants

Research Mode grants an approved project scope on the model ids named in the entitlement. Calls made under that higher-risk scope require an active entitlement naming the selected model. Ordinary standard calls do not use the entitlement. In either case, approval never activates an unqualified, disabled, or unhealthy release.

Approved work bills like any other request, per input and output tokens against eligible purchased credits. Approval does not supply Preview capacity funding.

How to apply

Apply from Research Mode in the app. The application is reviewed by a human; you can have one active application at a time, and its status moves through pending, needs_info, and then approved, rejected, or revoked. Existing eligible memberships can differ in review priority, but new membership checkout is paused during Preview; see the pricing page. Approval is tied to your organization and the project scope you describe, not to your individual login.

What the application asks

The review needs enough to verify that the work is lawful, that you are who you say you are, and that the requested access matches the project. You provide:

• Applicant identity: your name, organization, role, country, and a verifiable professional or institutional profile URL.
• Research vertical: security, life sciences, software engineering, robotics and systems, chemistry theory, or other frontier work.
• Project scope: a concrete description of the project the access is for. Approval is bound to this scope.
• Intended use: what you will actually do under the approved scope.
• Models: whether the scope covers Klara Base Preview v1, Klara Base Preview v2, or both.
• Data sensitivity: whether the project handles public, internal, regulated, or classified data.
• Risk tier: your assessment of the work's risk. Higher tiers get closer review.
• Authorized-work attestation: you confirm the work is authorized and lawful, and you accept the Research Mode policy.

Be specific. A vague scope or a mismatch between the stated use and the described project is the most common reason an application is sent back for more information.

Approval scope and expiry

An approval produces an entitlement with explicit bounds:

• Named models: the entitlement names the models it covers.
• Project scope: the entitlement carries the scope you were approved for. Using the access for unrelated work is outside the grant.
• Expiry: every entitlement has an expiry date. After it expires, the approved scope lapses until you renew or reapply.
• Risk tier: recorded on the entitlement and reflected in how the access is monitored.

You can see your current entitlement, its named models, scope, and expiry, in Research Mode in the app.

Data handling

Every public route currently declares 30-day operational retention, and prompts and completions are never used to train or improve any model, by us or our providers. The handling in force is recorded on every request, so you can confirm how each call was treated. See the no-training policy for the full commitment.

The boundary

Approval does not remove safeguards. The access is bounded:

• It is scoped to an approved project, the named models, and an expiry date.
• Every request is logged with its model and cost.
• An entitlement can be revoked, and high-risk access is reviewed on an ongoing basis.
• Clear abuse is blocked regardless of approval.

Next steps

• Apply for Research Mode from the app.
• Review the Research Mode policy and the acceptable use policy before you submit.
• Understand how requests bill in Preview funding & usage.