Terms of Service

Last updated: 2026-10-26

1. Service Description

Nanotoll.dev ("the Service") provides a text-compression API for AI agents and automated systems. POST /v1/compress accepts text and returns a compressed document plus a signed receipt that discloses what was kept and dropped. Three squeeze modes are offered - deterministic, extractive and verified - with flat per-call prices (Section 2). The Service also exposes account endpoints (registration, optional trial keys, balance, account state, payment history), public limit discovery (GET /v1/limits) and server-side receipt verification (POST /v1/receipts/verify).

The Service is designed for autonomous agents and programmatic access. There is no web interface and no user accounts in the traditional sense; access is via API key only, with an optional email-verified free trial.

2. Fee Structure

Each billed call carries a flat per-call price by squeeze mode:

The live values are always available at GET /v1/limits (no auth required); this table restates them as of the Last updated date. The deterministic mode is free of charge - it runs in milliseconds without a model - but still requires a valid API key and is subject to the trial inflight limit. The first paid rung is extractive. Fees are deducted from a prepaid credit balance funded with USDC on Base. A single API key and balance works across all endpoints. When the balance is insufficient for a request, the Service returns HTTP 402 with the estimated cost and current balance - no request is processed and no fee is charged for that request.

Free trial: one trial key per email address and per IP address, with a $0.50 credit grant and a 30-day expiry, issued via POST /api/v1/trial and POST /api/v1/trial/verify.

3. Deposit and Credit Policy

3.1 Funding

Users fund their balance by sending USDC (Circle's stablecoin) to a deterministically-derived funding address on the Base L2 network. The funding address is returned at registration via POST /api/v1/register.

3.2 Confirmation Threshold

Deposits are credited after 12 block confirmations on Base (~24 seconds). Until the confirmation threshold is reached, the deposit is visible on-chain but not reflected in the credit balance. The Service will not credit a deposit that has not reached this threshold.

3.3 Minimum Deposit

Deposits below $0.01 USDC (10,000,000 nanos) are logged but not credited. This prevents dust-spam attacks. Send at least $0.01 USDC to ensure the deposit is credited.

3.4 Reorg Policy

If a previously confirmed deposit is orphaned due to a blockchain reorg (the block no longer exists at the expected depth), the Service reverses the credit as follows:

• If the user's balance can absorb the reversal (balance >= credited amount), the amount is subtracted and the deposit is marked reorged.
• If subtracting would drive the balance negative (the user already spent the deposit), the deposit is flagged reorg_pending_review and the balance is left untouched. An operator must resolve the shortfall manually.
• A reorged transaction that reappears in a new block is not automatically re-credited. The reorged status blocks re-processing. Contact the operator if you believe a deposit was incorrectly marked as reorged.

Reorgs deeper than 12 blocks are rare on Base but not impossible. The Service does not guarantee finality - it follows the chain's consensus.

3.5 No Interest

No interest is paid on credit balances. Balances represent prepaid service credits, not deposits in a banking sense.

4. API Keys

4.1 Key Generation

API keys are generated at registration (POST /api/v1/register) and returned exactly once. The Service stores only a SHA-256 hash of the key - the plaintext key is not retained. If you lose your API key, it cannot be recovered; you must register a new key.

4.2 Key Security

You are responsible for keeping your API key secure. The Service is not liable for unauthorized use of your API key. If your key is compromised, there is no self-service revocation mechanism - contact the operator.

4.3 Rate Limiting

Registration is rate-limited per IP address. API endpoints may be rate-limited to prevent abuse. Excessive requests may result in HTTP 429 responses.

5. Acceptable Use

The Service is intended for AI agents and automated systems. You agree not to:

• Use the Service for any unlawful purpose
• Attempt to overload, crash, or disrupt the Service
• Reverse-engineer, decompile, or disassemble the Service
• Use the Service to process sensitive personal data (PII, health records, financial records) without appropriate safeguards
• Resell or redistribute access to the Service without authorization
• Attempt to manipulate credit balances, bypass billing, or exploit bugs

Violations may result in suspension or termination of access under ToS Section 8, and forfeiture of remaining credit where the termination is for cause.

6. No Warranty

The Service is provided "as is" and "as available," without warranty of any kind - express or implied. The operator does not warrant that:

• The Service will be available at any given time (uptime is not guaranteed)
• The Service will be error-free or produce correct output
• Deposits will always be credited without issue
• The Service is suitable for any particular purpose

7. Limitation of Liability

Nothing in these Terms excludes or limits liability for intentional misconduct, gross negligence, death or personal injury, or any other liability that cannot be excluded or limited by applicable law.

Subject to the paragraph above, and to the maximum extent permitted by law, the operator shall not be liable for:

• Any indirect, incidental, special, consequential, or punitive damages
• Loss of profits, data, or business opportunities
• Any damages arising from temporary or unscheduled service interruptions
• Any damages arising from delayed deposit crediting
• Any losses resulting from blockchain reorgs, RPC outages, or network congestion

Subject to the paragraphs above, the operator's total aggregate liability for all claims arising out of or relating to the Service shall not exceed the greater of (a) the total fees consumed by your account in the 30 days immediately preceding the event giving rise to liability, (b) the unused paid USDC credit balance held in your account at that time, or (c) 25 USDC (or USD 25 equivalent).

The return of unused paid credit balances pursuant to Section 8 or the Refund Policy constitutes a return of prepaid funds, not damages, and neither counts toward nor is limited by this cap.

8. Termination

The operator may terminate or suspend access at any time. Where the termination is for cause (a breach of these Terms or of the Acceptable Use Policy, fraud, or a sanctions or legal restriction), remaining credit is forfeited. Where the termination is not for cause, unused paid credit is refunded on request under the Refund Policy.

9. Changes to These Terms

The operator may update these Terms at any time. Material changes are announced on the site before they take effect. Continued use of the Service after a change takes effect constitutes acceptance of the updated Terms.

10. Governing Law

These Terms are governed by the law of the operator's place of habitual residence. Disputes shall be resolved in the courts of that place.

11. Contact

For questions about these Terms, contact: admin@nanotoll.dev

12. Severability

If any provision of these Terms is held to be invalid, illegal, or unenforceable, the remaining provisions shall remain in full force and effect. To the extent permitted by applicable law, the invalid or unenforceable provision shall be replaced by the applicable statutory rules.