Terms of service

Document version: 2026-09-22.2. Operator-specific publication draft.

These terms are drafted for the operator of Trident Protocol. Before public use, the operator must publish its legal name, contact information, effective date, applicable jurisdiction, and any required licensing or registration disclosures. Configuring those details does not replace legal review.

1. Scope and acceptance

These terms govern access to the operator's interface, token registry, payment conversion, and inference service. By affirmatively accepting these terms you agree to them to the extent permitted by applicable law. You must be at least 18, have authority to act for any represented entity, and be legally permitted to use the service in your location.

Nothing in these terms excludes, restricts, or modifies a right, guarantee, remedy, duty, or liability that cannot lawfully be excluded, restricted, or modified. This includes applicable Australian Consumer Law guarantees. Where these terms conflict with mandatory law, that law prevails.

2. Independent service and third parties

Trident Protocol is independent of OpenRouter, model providers, Pump.fun, Pons, Uniswap, Solana, Robinhood, and wallet providers. Names and logos identify third-party services; they do not imply sponsorship, approval, official token issuance, or partnership.

Third-party services have separate terms and technical rules. Trident Protocol cannot control their availability, indexing, transaction ordering, fees, model withdrawals, output, outages, or protocol changes. The operator remains responsible for its own obligations under applicable law.

3. Tokens and model associations

Tokens launched through the interface are community-created blockchain assets. Linking a token to a model creates an application association only. It provides no equity, ownership of intellectual property, entitlement to provider revenues, guaranteed redemption floor, guaranteed liquidity, profit expectation, or price peg.

Displayed model prices are service tariffs. They are not guarantees of token market value. No statement on the platform is personalised investment, legal, tax, or financial advice. Users are responsible for their decisions and independent assessment.

4. Wallet authorization and transactions

You control your wallet and approve each transaction. Review the network, recipient, contract, amount, allowance, and fees before signing. The operator never requests your recovery phrase or private key.

Blockchain transactions may be irreversible. A failed transaction may consume network fees. Quotes may expire, change before execution, or fail because of slippage, liquidity, provider availability, or protocol rules. Receipt verification can be delayed. An external indexer's delay is not evidence that a transaction failed.

5. Compute balances and payments

A confirmed payment buys an operator-provided inference service balance under the quote shown. It is not a bank deposit, a guaranteed investment, an OpenRouter account balance, or a claim to an onchain reserve. The operator receives the specified cryptocurrency and bears responsibility for maintaining service funding.

Native exchange references, FX buffers, transaction fees, and inference markups must be disclosed before the relevant payment or request. No price quote is binding beyond its stated validity or outside the stated transaction conditions.

An inference request may reserve an upper cost bound. Actual charges are reconciled to provider usage under the disclosed pricing rules. Uncertain requests may be held for a reasonable reconciliation period. The operator must investigate reported errors and correct verified duplicate or incorrect charges.

Balances have no promised cash conversion or token exchange feature. This does not remove any statutory refund or other remedy. If paid service cannot be supplied, the operator will address unused paid balances as required by applicable law and the circumstances, including any required refund. Users can contact the published support channel with the account and transaction identifiers.

5A. Community access and contributions

A community uses an existing token balance as an eligibility condition for a shared inference budget. Registration is not verification of the registrant's identity or issuer authority. Holding more than the threshold does not increase the per-wallet daily allowance. Access depends on continued eligibility, available funding, current terms and reasonable technical limits. No perpetual or unlimited service entitlement is promised.

Community contributions are sent to the disclosed operator treasury. A confirmed deposit is not immediately usable provider credit: conversion, provider top-up and allocation are separate operator actions. The operator must describe the treatment of any unallocated proceeds accurately. No automatic transfer of creator or liquidity fees is implemented or promised by this build.

Community budgets are not individual cash accounts, transferable claims, proportional revenue interests or representations that the holder owns provider credit. They have no advertised redemption facility. These descriptions do not override a different classification imposed by law or exclude a remedy for a paid service that cannot be supplied.

The operator may apply published spending limits and proportionate anti-abuse controls. Changes should be prospective and communicated where material; they must not retrospectively eliminate accrued mandatory rights. Requests already forwarded may incur provider charges despite cancellation. Disputed or uncertain charges will be investigated.

5B. Initial liquidity and fee rights

For a direct Robinhood pool, the creator supplies the liquidity and receives an unlocked LP position. The operator does not represent that liquidity is permanently locked, that a third-party marketplace will list the token or that market prices will track a model tariff. API-price snapshots are historical references only.

A creator must not market a fee allocation as automatic unless it has actually been implemented. Any separate fee commitment must identify the responsible party, calculation, collection method, deductions and interruption policy. Merely mentioning creator fees in token metadata does not execute that commitment.

6. Creator responsibilities

Creators are responsible for the accuracy and legality of token names, tickers, descriptions, images, links, and representations. You must have rights to submitted content. Do not impersonate a model provider, claim an unsupported partnership, promise unimplemented mechanics, or conceal fees.

You retain rights in your submitted content and grant the operator a non-exclusive licence to display, reproduce, and distribute it as necessary to operate and promote the relevant listing. Public IPFS metadata and blockchain records may persist after a listing is removed.

7. Prohibited activity

Do not use the service for fraud, deception, unlawful market manipulation, unauthorised access, exploitation of accounting defects, deliberate service overload, illegal content, infringement, or activities prohibited by applicable law or the relevant provider's enforceable rules. Do not submit the same transaction to claim multiple credits or represent a model-linked token as official provider equity or guaranteed compute backing.

8. AI output

AI output can be wrong, incomplete, harmful, or unsuitable for a particular purpose. Users must independently assess important results and must not rely on output as the sole basis for high-stakes decisions. The operator does not promise accuracy, originality, fitness for a particular task, or uninterrupted access beyond obligations that applicable law imposes.

9. Availability, suspension, and corrections

The operator may pause launches, payments, or inference to address security, funding, legal, or technical issues. Restrictions should be proportionate to the issue. Paid balances and pending claims will be handled consistently with mandatory law. The operator may correct demonstrable accounting errors, maintain records of corrections, and provide an explanation through support.

10. Warranties and limitation of liability

To the maximum extent permitted by law, the service is provided on an “as available” basis, and warranties not expressly stated here or imposed by mandatory law are disclaimed.

To the maximum extent permitted by law, the operator excludes liability for indirect or consequential loss, lost trading opportunities, anticipated profits, market-price movements, and losses caused solely by independent third parties or events outside its reasonable control.

For liabilities that may lawfully be capped, the operator's aggregate liability arising from the service is limited to the greater of (a) fees paid to the operator for the service in the preceding twelve months, excluding third-party network and protocol charges, and (b) AUD 100. This cap does not apply to mandatory refunds or non-excludable remedies, fraud, wilful misconduct, or other liability that applicable law prevents limiting.

No provision excuses the operator from its own non-excludable duties. The treatment of negligence and other fault depends on applicable law; these terms do not represent that every claim can be waived.

11. Responsibility for unlawful conduct

To the extent lawful and proportionate, a user is responsible for direct losses and reasonable third-party claim costs caused by that user's fraud, wilful unlawful conduct, or knowing infringement through the service. This does not require a consumer to indemnify the operator for the operator's own negligence, misconduct, or breach of non-excludable duties.

12. Complaints and disputes

Contact the published support address with the relevant account, transaction hash, request ID, and description of the issue. Never send secrets. The parties should attempt a good-faith resolution before commencing proceedings, except where urgent relief or mandatory rights require otherwise. Nothing requires mandatory arbitration or restricts access to a regulator or court where law protects that access.

13. Changes and severability

Material changes will be published with an updated version and, where appropriate, require renewed acceptance. Changes do not retrospectively remove accrued mandatory rights. If a provision is invalid, the remainder continues only to the extent lawful. Mandatory consumer protections in the user's jurisdiction remain unaffected.

14. Governing law and operator particulars

The final publication must identify the contracting legal entity, registration details where relevant, service address, contact channel, effective date and governing Australian State or Territory. Those particulars are not supplied by this code repository and must not be inferred from a domain name. A governing-law choice must preserve mandatory rights that apply notwithstanding that choice.

The liability cap and exclusions above are publication drafts requiring assessment against the actual transaction, customer category and applicable law, including unfair-contract-terms rules. Their presence is not a representation of enforceability. Using an external factory or a user-signed transaction does not transfer all responsibility for the operator's conduct to software.