Customer documentation

Martian Security

Find security failures with red teaming. Measure response quality with Evals. Keep both checks in your development workflow with the SDK and CI.

01Run your first assessmentConnect an agent, choose a small test, and inspect the evidence.02Run your first evaluationUse a published dataset to compare expected and actual answers.03Integrate the SDK and CIRun local callbacks and record repeatable checks for a tested revision.

Start with your workspace

Want a local preview first? Try a free two-record SDK evaluation without a Martian account or model key.

New to Martian? Accept your invitation and sign in, then read the concepts. You need an agent connection that you are authorized to test. Each tutorial explains the role, setup and limits before you start.

Choose the evidence you need

Red teaming

Can an attacker steer this agent outside its intended rules?

A bounded assessment with recorded attempts, findings and verification evidence.

Evals

Does this version answer a known set of cases correctly?

Dataset-version-pinned results, scores, comparisons and reviews.

SDK and CI

Should this tested revision pass my development checks?

Local test results, retained reports and a recorded gate outcome when configured.

Connect and approve an agent, choose endpoint or sandbox scope, select goals and tests, run a bounded assessment, then inspect evidence and verified outcomes. — The first assessment moves from an approved connection to evidence you can inspect. A finding’s strength depends on the verification actually recorded.Open full size Mermaid source

Explore the product

Use the console map to find each customer area, including the Evals dashboard, account menu and features that remain templates or previews.

Agents and connections — registration, validation and approval.
Environments — synthetic seed data and sandbox readiness.
Discovery — inventory and runtime evidence.
Permissions and limits — understand what your role and environment support.
Troubleshooting — recover without starting duplicate work.
Hermes documentation — the separate Hermes agent and its operator workflow.

These are beta product guides. The verification record identifies observed walkthroughs and any qualification still in progress.