I wrote and maintain axiomize, so treat this as the author talking. MIT, Python 3.11+, 1.14.3 is what pip installs today. Code: https://github.com/Furox-Art/axiomize
The part I think matters for people building physiological or pathway models is the export path, because that is where a model quietly changes meaning. axiomize keeps a versioned Model IR with units on every variable and parameter, and the SBML and CellML writers either emit XML or return a typed refusal with the reason and the portable IR attached. They never relabel your JSON as a standard.
Two refusals worth knowing before you trust the output:
CellML will not guess units. If any unit on the independent variable, a variable or a parameter is not in its known table, the export returns ADAPTER_REQUIRED with the detail "CellML export will not silently reinterpret unknown units" and an unsupported_units list naming exactly which ones failed. Known units become either a CellML builtin or an explicit custom units definition with base, exponent and multiplier written out.
Both writers are family-restricted. SBML L3V2 and CellML 2.0 accept ODE and algebraic models only. Hand them a DAE and you get ADAPTER_REQUIRED with "native SBML L3V2 export currently supports ODE and algebraic Model IR families" (the CellML message is the same shape). No partial XML, no best-effort conversion.
Run it like this:
pip install axiomize
axiomize model --action export --input-json request.json
with "format": "sbml-l3v2" or "cellml-2.0" in the request. The aliases sbml3v2 and cellml2 are accepted; the bare unversioned names are not, because you should be naming the schema version you want.
Limits I am not hiding:
The SBML writer emits one default compartment of size 1 and puts your variables in it as species. It does not build a multi-compartment physiological layout, and species carry initialConcentration only when the IR actually supplies an initial value.
Validation is reported in-band rather than assumed. Without python-libsbml installed the SBML response says schema_validation: NOT_RUN with the detail "XML structure was validated locally; install python-libsbml to perform full SBML semantic/schema validation". With it installed you get PASS or FAIL plus the first 20 libsbml error messages. CellML always reports NOT_RUN, because full libCellML validation is not bundled.
So the output is a conservative, explicit subset, not a claim that your model is now standards-compliant. Validate it in your own toolchain before you simulate it.
Repo: https://github.com/Furox-Art/axiomize Export format table: https://github.com/Furox-Art/axiomize/blob/main/docs/portable-export.md
Question for people who actually move models between simulators: when a unit is unknown, would you rather the exporter refuse outright as it does now, or emit the XML with the unit left as a free string and a warning? I chose refusal because a silent reinterpretation is the failure I keep seeing, but I would like to hear the case against it.