Turn raw email into a clear security decision.

Submit an .eml message and receive a compact verdict, risk level, signal codes, and explicit completeness metadata.

terminal

curl --request POST \
  "$HERMES_API_BASE_URL/v1/email-analyses" \
  --header "X-API-Key: $HERMES_API_KEY" \
  --header "Idempotency-Key: $IDEMPOTENCY_KEY" \
  --header "Content-Type: message/rfc822" \
  --data-binary @message.eml

200completed · suspicious · medium

Designed for production integrations

A narrow contract you can reason about.

01One endpoint

Submit a complete email

Send a raw RFC 822 message. Hermes returns a deliberately small, stable result model.

Read the guide →02Safe retries

Idempotency by default

Use a unique idempotency key for each logical submission and reuse it only when retrying that submission.

Read the guide →03Conservative output

Explicit completeness

Warnings and completeness make degraded analysis visible without exposing internal engine details.

Read the guide →

The integration loop

Three steps. No hidden workflow.

Hermes v1 is synchronous. Authenticate, submit the raw message, then handle the bounded response and RFC 9457 errors.

1
Prepare
Keep the original message bytes and generate an idempotency key.
2
Submit
POST the message as message/rfc822 over TLS.
3
Decide
Read verdict, risk, completeness, signals, and warnings together.

Ready when you are

Send your first synthetic email.

Open the quickstart