outcometick
The Python strategy SDK for outcometick.com — tick-level data for Polymarket and Predict.fun crypto Up/Down markets.
pip install outcometick
from outcometick import Strategy, Order
class MeanReversion(Strategy):
def on_market_open(self, ctx, market):
self.entered = False
def on_tick(self, ctx, tick):
z = ctx.zscore(tick.value, window=180)
if self.entered or abs(z) < ctx.p.entry_z:
return None
side = "DOWN" if z > 0 else "UP"
limit = ctx.book().best(side)
if limit is None:
return None
self.entered = True
return Order(side=side, size=ctx.p.size, limit=limit)
What is in here
The SDK surface your strategy imports, and nothing else:
Strategy |
the base class you subclass |
Order |
what a hook returns; validates side, size and limit on construction |
SIDES |
("UP", "DOWN") |
It is typed (py.typed), so your editor and mypy know the API. Everything a
strategy can actually do arrives through ctx, which the runner constructs —
there is deliberately nothing here to reach out with.
The hooks are not defined on the base class on purpose. A default no-op
on_tick would turn "you declared a hook you did not implement" — a rejection
fixable in seconds — into a run that quietly never trades and bills you for an
empty equity curve.
Testing
pip install . && python -m unittest discover -s tests
Running a backtest
Submitting and replaying is done with the ot command line, which is
distributed on npm because there is exactly one of it for both languages:
npm i -g outcometick
ot check . # the same validator the queue runs
ot run . # replay locally against sample data
ot submit . # send it to the queue
It runs Python strategies by spawning your local python3. Two CLIs would mean
two copies of the validator, and the second copy is what makes
"if it passes locally it will not be rejected on submit" stop being true.
Full reference: https://outcometick.com/docs/sdk
1 maintainer
Metadata
1 maintainer
Release files for outcometick 1.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| outcometick-1.4.1.tar.gz | 5.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| outcometick-1.4.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.3 kB
Release files / outcometick-1.4.1.tar.gz
| Download URL | outcometick-1.4.1.tar.gz |
|---|---|
| Size | 5.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d7cec80979498ee6511aa1bcd6a6d8f53c6560f997768de9a57c6526381ddf20
|
|
BLAKE2b-256 checksum How to use checksums |
dc6d0960b85b001235e790272ebd0d8429c40a0bbd6fefc288212f5e52464273
|
| 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 Aug 23, 2026.
Transparency logRelease files / outcometick-1.4.1-py3-none-any.whl
| Download URL | outcometick-1.4.1-py3-none-any.whl |
|---|---|
| Size | 4.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e871853a0d5c3f0d0b4fefe21ed16e72021790d454f122e5d221bcc9c517b13b
|
|
BLAKE2b-256 checksum How to use checksums |
63554fed67b482148f6e1b2cb12bc8965b6f0e19ec4b3d5f94592055549bbb7c
|
| 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 Aug 23, 2026.
Transparency log
