Numerical infrastructure for decisions that must hold up.
API23 is a precision-controlled computation system. It preserves computational state, runs demanding numerical work, verifies the result against a defined oracle, and produces a reviewable execution record.
The executive decision
API23/API23v2 is positioned as licensable financial and algorithmic software infrastructure for quantitative finance, risk, valuation, optimization, scientific computing, and regulated analytics.
Its value is control over numerical behavior: a buyer can define the precision, workload, comparison oracle, and acceptance receipt for a computation instead of receiving an unexplained number from an opaque pipeline.
Who buys
Quantitative finance teams, risk and valuation groups, financial software vendors, scientific-computing organizations, and enterprises that need auditable numerical workflows.
How it is packaged
Buyer-specific evaluation, field-of-use license, OEM integration, or recurring runtime agreement with an acceptance receipt and controlled technical disclosure.
Technical proof
What API23 does
API23 supplies precision selection, error-budget handling, deterministic output checking, and a C-compatible integration boundary.
What API23v2 adds
API23v2 supplies exact state composition, repeated-stage collapse behavior, and persistent wide-state execution.
What was measured
The retained public evidence reports 11/11 conformance tests passed, zero maximum API23↔API23v2 error in the recorded oracle comparison, zero five-stage collapse error, and six symbolic CPU operations with two fault boundaries.
Evidence basis: technical white paper and retained execution receipts in the controlled diligence package.
Accounting view
The portfolio is proprietary software, algorithmic know-how, and related intellectual property. The accounting workstream is organized around the applicable transaction and reporting facts.
| Framework | Public-facing purpose |
|---|---|
| ASC 820 | Fair-value measurement; unobservable inputs are treated as Level 3 when applicable. |
| ASC 350-30 | Identifiable intangible-asset analysis, useful life, and impairment workstream. |
| ASC 805 | Identifiable intangible treatment in an acquisition or business combination. |
| ASC 606 | Revenue analysis for licenses, subscriptions, support, and evaluation services. |
This is a public accounting framework summary, not an entity-specific GAAP opinion. Final treatment depends on executed agreements, reporting facts, and the reporting entity’s accounting advisers.
Valuation method
The public rNPV method is a probability-weighted discounted cash-flow model. Each dated inflow and outflow is assigned the probability of reaching the event that creates it, then discounted to the valuation date.
Public methodology references
| Reference | What it contributes | Use |
|---|---|---|
| Public primary filing — algorithmic software/IP | Disclosed technology-IP rNPV example | Methodology and market context only |
| Public primary filing — software IP | Level-3 fair-value example | Corroborative accounting method; not API23 rNPV |
Primary public filing — technology-IP rNPV example · Primary public filing — software-IP fair value example · Primary public filing — rNPV method
Commercial packaging
Evaluation
Buyer supplies a representative workload and acceptance metric. ZC returns a reproducible report and receipt.
License
Field-of-use rights, term, territory, support, and usage limits are defined in the executed agreement.
OEM
Controlled integration for a financial, scientific, or enterprise software product.
Executive next step
Start with a buyer-specific numerical evaluation. Use the buyer’s workload, incumbent baseline, and acceptance oracle to establish measurable value before production licensing.
Request a diligence conversation