StrikeStrike

Coming from TypeSafe System One

What stays the same when you point a System One client at Strike.

Strike is not affiliated with TypeSafe. The decision endpoint follows the same request and response shape as System One.

What you change

  1. Set the base URL to https://strike-ai.eu (SDK default).
  2. Send Authorization: Bearer with a Strike API key from the console.
  3. Keep POST /v1/systemone and the question types noul, choice, and score.

Optional header Idempotency-Key repeats a successful response for the same body. See Authentication.

Header names

Danger Zone opt-in accepts both names:

StrikeAlso accepted
Strike-Danger-Zone-Long-ContextTypeSafe-Danger-Zone-Long-Context
Strike-Danger-Zone-ImagesTypeSafe-Danger-Zone-Images

Both are off unless the request sets them. Image and box answers are a preview. See Danger zone.

Differences

  • Yes/no questions may use type yes_no on the request. Responses always use noul.
  • Answers can include confidence_band (high, leaning, low) when calibration bands are enabled. During beta the bands are off and the field is null. Probabilities are uncalibrated.
  • options.debias is off or permute (with debias_passes, 2 to 8). permute asks the API to average extra option orders.
  • usage.cost_eur is the EUR charged for the call when billing is on.
  • The public API version is a date (2026-10-12 today) on GET /health and the x-strike-api-version header. See API versioning.