Pricing
Pricing assumptions & revision rules
Prices are revised annually (base year 2025). Blank/non-numeric annual rates are treated as the same as the previous year. Final terms are fixed by individual contract.
Reference pricing includes: monthly capacity (defined by the availability calendar), fixing I/O spec, generating the Evidence Pack (audit trail) and acceptance readiness (verification info/procedure), and confidentiality operations.
Operating Model
Intake: monthly (capacity defined by the availability calendar)
Bid window: day 2 00:00 to month-end 23:59 (JST)
Submit via bid form (sealed bid)
Tally & notify: day 1 00:00–23:59 (JST)
Notify highest bid of previous month
Tie at top bid: first-come tie-break
Submission reaching our servers first is prioritized (announced if changed)
Eligibility: primarily B2B
Companies, research institutions, public institutions. Verification and usage limits are fixed by contract.
External delivery: one result set per engagement ID
No comparisons/sweeps
Example: Jan bid window (Jan 2–Jan 31) → tally & notify on Feb 1 (JST)
Execution flow (individual contract)
Phase 1: Contract
- Winner notification (day 1 each month)
- Execute contract → invoice deposit (30% of bid) → accept after payment confirmation.
Phase 2: Execution
- Submit input package (within 30 days after deposit confirmation)
- Validate input → lock-in notice (no changes afterward)
- Compute in private environment (re-run as needed)
- Provide Evidence Pack via access-controlled, time-limited URL
Phase 3: Acceptance
- Acceptance: if no notice is received within 14 days after delivery, it is deemed received (use `opaque_ref + evidenceHash` as the primary verification pair and confirm pack integrity with `pack_sha256` when needed; terms can be adjusted by contract).
- Invoice remaining balance (70%) → payment
- Delete data per retention policy
Delivery timeline (estimate): ~30 days from input lock-in (varies by engagement; contract terms prevail if separately agreed).
Bank details are stated on the invoice.
Deliverable
The core deliverable is an Evidence Pack (canonical JSON). It includes integrity verification and summary information required for acceptance.
Standard structure (TOC-level example)
- Metadata (identifiers/protocol version, etc.)
- Input conditions record (including hashes for reproducibility)
- Computation results (KPIs/summary tables, etc.)
- Integrity metrics (SHA-256)
- Acceptance criteria compliance record and acceptance procedure
Internal key names and detailed procedures are not disclosed publicly.
- Document integrity decision criteria (iterations/conditions, etc.)
- Tolerance can be fixed by individual contract.
- If a No-Go (no external delivery) condition applies, record the reason in the Evidence Pack.
Data Handling
We separate retention of work data (inputs/attachments/intermediates) from the Evidence Pack (audit trail) and fix it via retention policy.
| Policy | Work data | Evidence Pack |
|---|---|---|
| Strict | Delete within 24h | — |
| Standard | Retain 14 days | — |
| Audit-ready | Delete within 24h | 1 year encrypted |
Next step
Check the C0 guide for the return boundary, and if needed review the fixed demo for acceptance behavior before submitting your bid.
If you can accept publication of usage records and anti-exploration conditions, consider the Standard Track for the normal price range under public-use conditions. No slot limit. Current-year reference pricing is governed by /pricing with annual revision support.
See standard-track estimate →This page is not legal advice. Transaction terms are fixed by individual contract. Anonymous Track and Standard Track cannot be combined.