PAYMENT
Every payment is deliberate.
- Every payment is explicit and user-approved in Nimiq Pay or the desktop Hub checkout.
- NimProof does not custody funds, operate escrow, hide wallet actions, or spend autonomously.
- There are no subscriptions and no automatic child payments.
- Agent Relay requires a separate approval for Transcribe a Clip and Translate Captions.
- A returned transaction reference is not proof of payment. The same transaction must be checked for network, recipient, value, commitment, successful execution, and final settlement.
SERVICE LIMITS
Inputs stay intentionally narrow.
| Service | Input and output | Current limits |
|---|---|---|
| Transcribe a Clip | Short MP4 → English SRT | Up to 25 MiB, 60 seconds, and an audio stream. |
| Translate Captions | English SRT → Spanish SRT | Plain-text SRT, up to 300 cues and 3,000 subtitle characters. The cue cap is a bounded processing safeguard, not a general subtitle-support claim. |
| Agent Relay | Transcribe → Translate → Verify | Both child limits and both explicit approvals apply. |
OUTCOMES
Processing and cancellation states are separate.
Inputs can be malformed, unsupported, oversized, missing audio, or beyond duration limits. Model inference can time out or return an empty or invalid artifact. Payment can be cancelled, remain pending, be included, fail execution, or become temporarily unavailable for verification.
If a provider returns a transaction reference, recovery keeps the same request ID and hash. NimProof does not silently create a replacement payment. A successful receipt is issued only after the payment and artifact checks complete.
AI LIMITATIONS
Useful output is not guaranteed.
Local models can make transcription and translation errors, omit words, mis-hear speech, or produce awkward language. Receipts do not certify content quality, legal compliance, ownership, safety, endorsement, or suitability for a particular purpose. Users remain responsible for reviewing the artifact before relying on it.
INFRASTRUCTURE
Verification depends on the network.
The configured public RPC may be rate-limited or temporarily unavailable. In that case payment verification remains retryable and is not reported as a payment failure. Finality and execution are separate from the provider's initial transaction response.