FinQIR
Financial Quantum Intermediate Representation
FinQIR is an independent, Apache-2.0-licensed Python toolkit for structured quantum-finance modeling, compilation, and optimization on Qiskit. It is built for finance engineers who need recognizable financial concepts and quantum engineers who need inspectable mappings, constraints, circuits, and results.
[!IMPORTANT] FinQIR is an independent community project. It is not an IBM product and is not affiliated with or endorsed by IBM or the Qiskit project.
FinQIR begins with useful portfolio, pricing, probability-distribution, and market-data components derived from the Apache-licensed Qiskit Finance project. Its roadmap adds structured portfolio problems, traceable financial mappings, finance-aware compilation passes, constraint-preserving QAOA, and reproducible benchmarks.
Installation
After the first PyPI release, install FinQIR with:
pip install finqir
Until then, install the development version from source:
git clone https://github.com/bilgin-kocak/finqir.git
cd finqir
python -m pip install -e ".[test,dev]"
FinQIR 0.1 targets Python 3.10 or newer and Qiskit 2.5.2.
Example
import numpy as np
from finqir.applications.optimization import PortfolioOptimization
problem = PortfolioOptimization(
expected_returns=np.array([0.10, 0.08, 0.12]),
covariances=np.array(
[
[0.10, 0.02, 0.03],
[0.02, 0.08, 0.01],
[0.03, 0.01, 0.09],
]
),
risk_factor=0.5,
budget=2,
)
quadratic_program = problem.to_quadratic_program()
print(quadratic_program.prettyprint())
Planned structured API
The design and implementation roadmap cover:
StructuredPortfolioProblemwith named financial constraints;- binary, integer, unary, domain-wall, and fixed-cardinality mappings;
- finance-aware problem and circuit compilation passes;
- constraint-preserving QAOA mixers;
- conflict-graph portfolios and constrained MIS problems;
- multi-period rebalancing, risk, pricing, and benchmarking extensions.
These APIs are roadmap items and are not part of the initial package foundation. See the approved design and implementation plan.
Development
python -m pip install -e ".[test,dev]"
python -m unittest discover -s test -v
python -m build
python -m twine check dist/*
Project history and license
FinQIR is an independent derivative of Qiskit Finance. Existing copyright notices are retained in derived files. New FinQIR work is released under the same Apache License 2.0.
FinQIR is research software. It does not provide investment advice and must not be treated as a guarantee of financial performance or quantum advantage.
Metadata
Release files for finqir 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| finqir-0.1.0.tar.gz | 41.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| finqir-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 93.2 kB
Release files / finqir-0.1.0.tar.gz
| Download URL | finqir-0.1.0.tar.gz |
|---|---|
| Size | 41.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6a5ed877a6afd4201be7814d50d67abc3b50edbd63f39f57d63c91130c874310
|
|
BLAKE2b-256 checksum How to use checksums |
402de1c40aa056e462f19b26d79c697fbb4690ed7202960fe616e570b5eca027
|
| 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 Sep 12, 2026.
Transparency logRelease files / finqir-0.1.0-py3-none-any.whl
| Download URL | finqir-0.1.0-py3-none-any.whl |
|---|---|
| Size | 51.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0cdaf256489398f2c742812225fd735baa3111fdbcd6103bbe3fc1d57c6d4b02
|
|
BLAKE2b-256 checksum How to use checksums |
d276ea67879fa17045d492d2b3d96240e14ef4ccf223f2a36738d69a464aee32
|
| 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 Sep 12, 2026.
Transparency log