journalize.

Terms of Service

Last updated: 2026-07-03

These Terms govern access to the Journalize API and MCP server (the "Service") at journalize.dev, operated by Web Content Creators, registered in Hong Kong (Business Registration No. 41133353) at Unit B, 12/F, Hang Seng Causeway Bay Building, Hong Kong ("we", "us"). By calling any endpoint of the Service, you ("you", the calling agent or its operator) agree to these Terms.

1. What the Service is

The Service stores and validates double-entry accounting records — literal Beancount directives — that you create, and computes reports (balances, income statements, trial balances) from them. We provide the signed, paid transport and storage layer, and mechanical validation (balance checks, booking rules, account-existence checks) against Beancount's own engine. We do not generate, source, or vouch for the underlying financial data — it is entirely what you submit. Correctness of a report reflects correctness of what you entered; the Service guarantees the arithmetic and booking rules were applied correctly, not that your categorization or accounting treatment is right for your purposes.

2. Not financial, legal, tax, or accounting advice

Nothing returned by the Service constitutes financial, legal, tax, or accounting advice. A balance sheet or income statement the Service computes is a mechanical summary of the entries you provided — it is your responsibility to determine whether those entries, and any decisions made from the resulting reports, are correct, complete, and appropriate for your jurisdiction and purposes.

3. Your ledger identity and its private key

Registering generates an Ed25519 keypair. We show you the private key exactly once and never store it. If you lose it, we cannot recover it, restore your access, or produce a replacement — there is no account recovery, because there is no account, only the key. Safeguarding it is entirely your responsibility.

4. Data durability

We do not currently guarantee any specific level of data durability, backup frequency, or recovery point. We recommend retrieving your complete ledger via GET /export (or the export_ledger tool) periodically and keeping your own copy. This section will be updated if and when a formal backup/durability commitment is established.

5. Payment

  • Pricing varies by endpoint/action; see journalize.dev or llms.txt for current indicative pricing. The live 402 response (REST) or payment_required result (MCP) at the time of your call is the authoritative price — if published pricing and the actual response ever disagree, the response governs.
  • Paid actions require payment per the x402 protocol, settled in USDC on the Base network.
  • Payment is irreversible once confirmed on-chain. We do not offer refunds. A write that is rejected by validation (unbalanced, unopened account, malformed syntax) is never charged in the first place — nothing is settled unless the write actually succeeds, or a read genuinely runs to completion. If you believe a successful, charged call behaved incorrectly due to an error on our end, contact us (Section 8) — we may issue a goodwill credit at our discretion, but this is not a contractual right.
  • Prices are subject to change without prior notice.

6. Acceptable use

You may not:

  • Attempt to bypass per-call payment, including replaying, forging, or tampering with signed requests or payment proofs.
  • Place load on the Service disproportionate to payment made, including automated retries at high frequency without corresponding payment.
  • Use the Service to create or maintain records intended to deceive a third party (e.g. fraudulent bookkeeping for regulatory or tax evasion purposes). We are not responsible for verifying the truthfulness of what you submit, but reserve the right to refuse service where misuse is apparent.

We may rate-limit, block, or refuse service to any caller at our discretion.

7. No uptime guarantee

The Service is provided "as is." We do not guarantee any specific uptime, response time, or availability.

8. Liability

To the maximum extent permitted by law, our total liability arising from your use of the Service is limited to the amount you paid us in the 30 days preceding the claim. We are not liable for indirect, consequential, or incidental damages, including decisions made based on Service output, or loss resulting from losing your private key.

9. Governing law

These Terms are governed by the laws of Hong Kong. Any dispute is subject to the exclusive jurisdiction of the courts of Hong Kong.

10. Changes and contact

We may update these Terms from time to time; the "Last updated" date above reflects the current version. Continued use of the Service after a change constitutes acceptance.

Contact: [email protected] Web Content Creators (Business Registration No. 41133353) Unit B, 12/F, Hang Seng Causeway Bay Building, Hong Kong