Terms for TRMesh product, APIs and data-access services
This page outlines baseline terms for the public website, trial registration, authenticated workspace, AI assistant, combined queries, public APIs, billing and referral rewards. It helps visitors understand acceptable use, permission boundaries, billing behavior, data responsibility and service responsibilities. TRMesh provides social data access and API orchestration infrastructure; it does not own, endorse or resell the underlying data of target platforms. Enterprise contracts may extend or supersede these terms for managed commercial deployments.
Service role
TRMesh is API development and data-access infrastructure. It provides unified authentication, routing, data forwarding, billing, usage logs, AI-assisted querying and workspace governance, but does not guarantee that target-platform data will always exist, remain complete, stay accurate or fit any specific business conclusion.
Account responsibility
Users must protect account credentials, sessions, developer tokens, payment credentials and team permission settings. Access may not be shared, resold, rented or leaked, and users may not attempt to bypass authentication, billing, permissions, RPS limits, risk controls or access controls.
Public and authorized data
Users may use the service only within lawful, authorized and target-platform-compliant boundaries. The platform does not authorize bypassing login walls, privacy settings, technical limits, regional limits, platform terms or third-party rights. Users must determine whether their requests, exports, storage and downstream use have a lawful basis.
Acceptable use
The service may not be used for unlawful activity, harassment, discrimination, infringement, spam, abusive monitoring, impersonation, platform-limit circumvention, bulk trial abuse, data-service disruption, abusive load testing, reverse engineering, vulnerability exploitation or behavior that harms the platform, data-service providers, target platforms or third parties.
APIs and intelligent analysis
Users may access only the API and analysis capabilities available to their account and may not bypass controls, seek unauthorized access, or prompt the service to fabricate data. Generated summaries, classifications, and recommendations are assistive and should be checked against their sources before important decisions.
Fees, balance and charging
The platform is priced in USD. Users must maintain enough balance to cover the estimated cost of paid APIs, AI model usage, combined queries or higher RPS capabilities. Final charges follow request execution, model usage, service costs, discount tier, trial quota and platform pricing rules.
Recharge, payments and refunds
Recharge balance is used for platform-service consumption. Payment channels, settlement timing, blockchain confirmations, fees, exchange rates, refund rules and disputes may be affected by third-party payment providers. Except where required by law, duplicated charges or platform-confirmed errors, consumed quota and completed services are generally non-refundable.
Referral rewards
Referral rewards apply only to eligible customers, eligible orders and rewardable transaction types under platform rules. The platform may cancel rewards, recover balance or restrict accounts for abnormal registrations, artificial traffic, fake transactions, self-referrals, refunded orders, risk-control hits or terms violations.
Data use responsibility
The platform provides social data access, orchestration and governance. Users remain responsible for determining how retrieved data is used, stored, exported, displayed, resold, used for model training, authorized, handled for data-subject requests and processed downstream. Users may not use outputs for unlawful or rights-infringing purposes.
Data-service dependencies
Some capabilities depend on external data-service providers. The platform manages gateway forwarding, routing, billing, logging and reliability controls, but cannot guarantee independence from data-service availability, API changes, platform risk controls, quotas, pricing, policies, regional limits or data visibility restrictions.
Service availability
The platform is built for reliability, but trial-stage features, route coverage, commercial policies, pricing, discounts, payment channels, data capabilities and third-party capabilities may change as the product, service providers, legal requirements or risk controls evolve.
Intellectual property
The website, workspace UI, documentation, SDK examples, Skill copy, orchestration logic and system implementation remain owned by TRMesh or its licensors. Users retain rights to their submitted content and business data while granting the platform the processing rights needed to provide the service.
Suspension and limits
The platform may limit requests, reduce RPS, suspend tokens, freeze accounts, request additional verification, refuse service or terminate access when abuse, unpaid balance, refund disputes, risk events, security concerns, unlawful activity, third-party-right violations or terms violations are detected.
Disclaimer
The service is provided as is. Unless expressly committed in writing, the platform does not warrant data completeness, continuous availability, merchantability, fitness for a particular result, target-platform behavior or business decisions made by customers based on retrieved data.
Limitation of liability
To the extent permitted by law, the platform is not liable for indirect damages, lost profits, business interruption, data loss, third-party claims or issues arising from customer integrations and compliance choices. Any direct liability is limited to fees actually paid for the relevant service during a reasonable period before the dispute, subject to applicable contracts or law.
Changes and notice
Terms, pricing, quotas, payment channels, reward rules, product scope and data capabilities may change over time. The website and workspace documentation should be treated as the current public reference, and material changes will be communicated through product pages, workspace notices or email when practical.
Order of precedence
If public pages, workspace notices, orders, enterprise contracts or data-processing agreements conflict, signed enterprise contracts or written agreements confirmed by both parties control. Without a signed agreement, the current public terms and workspace rules apply.