Skip to main content

strike-ai

Python client for the Strike API. You send content and typed questions. You get one answer per question, with probabilities.

pip install strike-ai
import os
from strike_ai import Client

client = Client(api_key=os.environ["STRIKE_API_KEY"])
result = client.decide(
    "My card was charged twice for the same order. Please fix this today.",
    {
        "is_urgent": {
            "type": "noul",
            "instructions": "Does the customer express time pressure?",
        },
        "team": {
            "type": "choice",
            "instructions": "Which team should handle this message?",
            "criteria": {
                "billing": "Payments, refunds, invoices",
                "technical": "Bugs, outages, integrations",
                "other": None,
            },
        },
    },
)

STRIKE_API_URL overrides the default base URL, https://strike-ai.eu.

Strike is in beta. strike-1 returns real model probabilities. They are not calibrated for production routing yet.

This repository is the public client. Model weights, training, and the API server are not in it.

Endpoint

POST https://strike-ai.eu/v1/systemone

Type You ask You get
noul A yes/no question A value from 0 (no) to 1 (yes)
choice One option from a set you define The top option and a probability for every option
score A rating on levels you define A probability-weighted score and a probability per level

The same call with curl:

curl https://strike-ai.eu/v1/systemone \
  -H "Authorization: Bearer $STRIKE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "strike-1",
    "state": "My card was charged twice for the same order. Please fix this today.",
    "questions": {
      "is_urgent": {
        "type": "noul",
        "instructions": "Does the customer express time pressure?"
      },
      "team": {
        "type": "choice",
        "instructions": "Which team should handle this message?",
        "criteria": {
          "billing": "Payments, refunds, invoices",
          "technical": "Bugs, outages, integrations",
          "other": null
        }
      }
    }
  }'

Strike is not affiliated with TypeSafe. The hosted API speaks a System One-compatible wire format.

Metadata

Release files for strike-ai 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for strike-ai 0.1.1
File Size Uploaded
strike_ai-0.1.1.tar.gz 3.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for strike-ai 0.1.1
File Interpreter ABI Platform
strike_ai-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 7.1 kB

Release files / strike_ai-0.1.1.tar.gz

Download URL strike_ai-0.1.1.tar.gz
Size 3.3 kB
Tags Source
SHA-256 checksum
How to use checksums
b73640c2b69c15d9c5c05af8bd174f060cc31da98aae710a04c9b7b98e9b5ef8
BLAKE2b-256 checksum
How to use checksums
da1e31a8ae03c9f3ccd73f2b5c9ea2db99bc87f0cc7f87136df38fc5a896aa48
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.

Transparency log

Release files / strike_ai-0.1.1-py3-none-any.whl

Download URL strike_ai-0.1.1-py3-none-any.whl
Size 3.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
616ddca9679d3fdf226990ebdfac776f1be7b5cdc170868cf366fa9cc1281fcf
BLAKE2b-256 checksum
How to use checksums
dab8c836cc4b583dce18845a4ee13648a006fa62d00505cb18248129a6c2479c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page