Terms of Service

3.1 Account creation

To access the Services, you must create a Reinx account by providing accurate, current, and complete information, including your name, email address, and a secure password. You agree to update your account information promptly if it changes.

3.2 Identity verification (KYC/KYB)

As a regulated financial services platform, Reinx is required to verify your identity before granting access to financial features. You agree to provide accurate identity verification information as required by our KYC and KYB processes (conducted through Dakota and its verification providers), supply additional documentation as reasonably requested, and consent to those providers processing the information needed for verification. Financial features will be unavailable until verification is complete. We reserve the right to refuse, suspend, or terminate your account if verification fails or reveals unacceptable risk.

By using financial features, you also agree to any Dakota or other provider terms presented during onboarding. If virtual cards are activated, the applicable issuing-bank and card-network terms will be presented before activation.

3.3 Account security

You are solely responsible for maintaining the confidentiality of your account credentials and for all activity under your account. You agree to use a strong, unique password with MFA enabled, never share credentials, immediately notify us of suspected unauthorised access, and secure all scoped API tokens for your AI agents. Reinx is not liable for loss arising from unauthorised access due to your failure to comply with these obligations.

4.1 Platform overview

Reinx is a business-facing fintech platform that enables users to create and manage cryptocurrency wallets for their AI agents, with spending limits, real-time approve/deny controls, expense tracking, analytics, and AI-powered navigation tools. Virtual card services are planned but are not currently active.

4.2 Core Services

• Virtual card issuance: Planned creation and management of virtual payment cards for AI agents. Card services are not currently active and will be subject to the applicable issuing partner terms if and when activated.
• Cryptocurrency wallets: A canonical RD wallet on Base plus supported USDC receive channels for EVM networks and Solana, operated on Dakota infrastructure (a FinCEN-registered MSB). Receive channels may normalize incoming USDC into the canonical balance and are not separate spend wallets. Reinx holds the ECDSA P-256 signing keys; you can revoke Reinx’s signing authority at any time.
• Financial account management: Funding, withdrawal, and balance management for the canonical RD balance and supported USDC interoperability rails through Dakota’s on-ramp, off-ramp, and conversion pipelines.
• Spending controls: Monthly and daily budgets, per-payment caps, velocity limits, approval thresholds, and policies enforced by Reinx before wallet payment execution.
• Dashboard and analytics: Real-time monitoring of agent transactions, spending trends, budget use, and financial reporting. Agent Health Score is a planned capability and is not currently calculated or displayed.
• AI copilot: AI-powered conversational assistant for reading permitted dashboard data and navigating platform workflows. It does not create agents, change policies, approve transactions, or move money. When you interact with the Reinx assistant, you are communicating with an artificial intelligence system, not a human. The copilot may provide general guidance but does not provide financial, legal, or investment advice. Copilot responses are generated by AI and may not always be accurate.
• API and MCP integration: Developer tools for AI agents to interact with the platform via REST API and MCP.

4.3 Not a bank

Funds held on the Reinx platform are maintained as RD and, where applicable, supported stablecoins such as USDC. They are NOT insured by the FDIC or any government insurance programme. These assets are not guaranteed by any government agency. You acknowledge and accept the risk that their values may fluctuate.

5.1 Account funding

• Bank transfer (ACH): Availability, limits, timing, and any applicable provider fees are shown before confirmation. Funds become available after settlement.

Supported funding is converted into the account’s canonical RD balance through Dakota’s on-ramp or conversion pipeline. Your dashboard shows balances in U.S. dollar equivalents.

5.2 Withdrawals

• Standard withdrawal: Processed through the supported bank rails shown in your account. Timing, limits, and any applicable provider fees are disclosed before confirmation.

5.3 Subscription fees

• Free ($0/month): Unlimited agent accounts and wallets, spending controls, dashboard access, seven-day audit history, REST and MCP access, webhooks, and the Reinx Assistant. Virtual cards are Coming Soon.
• Pro ($15/month): Everything in Free plus up to three organization seats, thirty-day audit history with export, higher API and MCP rate limits, and priority support. AI analytics and custom reports are planned capabilities and are not currently active.
• Enterprise (Custom): Everything in Pro plus unlimited seats, full audit history, advanced integrations, and a dedicated account manager. SSO, SCIM, custom roles, and IP allowlisting are planned capabilities and are not currently active.

Subscriptions are billed monthly or annually through Stripe Billing according to the checkout selection or order form. Cancel anytime; cancellation is effective at the end of the billing period. No partial refunds.

5.4 Transaction fees

• Card transactions: Virtual card services are not currently active. Any card fees or interchange terms will be disclosed before activation.
• Wallet transfers: Gas fees sponsored by Reinx at launch. Future per-transaction network fees will be disclosed before execution.
• Rewards program: For eligible paid tiers, Reinx may offer cash back rewards calculated in relation to account balances. Reward rates are variable, not guaranteed, and may change or be discontinued at any time. The rewards program is a platform feature and does not constitute a deposit, investment, or interest-bearing account.

5.5 Payment authorisation

By adding a payment method, you represent that you have authority to use it, authorise Reinx and the applicable funding or withdrawal provider to act on your instructions, confirm all transactions comply with applicable law, and agree this authorisation remains effective until you remove the method or close your account.

6.1 Card issuance

If activated, virtual cards will be issued through an identified issuing partner and applicable card network. Card availability, limits, and issuer terms will be presented before activation. No agent account currently receives an active card.

6.2 Spending controls

For an activated card service, card-rail controls will be enforced outside agent code and may include:

• Per-transaction and periodic spending limits
• MCC restrictions and merchant allow/deny lists
• Velocity controls
• Human-in-the-loop approval workflows
• Card pause controls when supported by the issuing partner

6.3 Shared Payment Tokens

Shared Payment Tokens (SPTs) are a deferred capability and are not currently available. If introduced, their scope, provider, compatibility, and credential handling will be disclosed before use.

6.4 Card credential security

If card services are activated, only an authorized human account holder may view full card details through the issuing provider's secure element. AI agents will not receive raw card credentials, and the MCP server will not expose a card-detail retrieval tool.

6.5 Disputes and chargebacks

Applicable dispute timelines, investigation procedures, and fees will be presented with the issuing partner's terms before card activation.

7.1 Agent account creation

You may create AI agent accounts with wallet receive infrastructure for supported EVM chains and Solana. Virtual cards are not currently issued. You are solely responsible for all agents you create and all actions taken by those agents.

7.2 Agent credential isolation

Agents communicate via scoped API tokens through MCP or REST API. Tokens contain agent account ID and permissions, not card numbers or wallet keys. Tokens are stored in MCP configuration files, not in agent LLM context. Tokens display once at creation and can be regenerated anytime. You are responsible for securing all tokens.

7.3 Agent responsibility

You are fully responsible for the actions of your AI agents, including all transactions, funds spent or transferred, any legal violations, and ensuring agents operate within configured limits. Reinx provides robust controls, but ultimate responsibility rests with you.

7.4 Agent Health Scores

Agent Health Score is a planned capability and is not currently calculated or displayed. If introduced, Reinx will disclose the factors, intended uses, and relevant user controls before relying on a score for platform decisions.

7.5 Supervised transaction mode

All agent wallet transactions route through the Reinx backend. The backend validates against your configured spending policies before executing. Transaction approval and decline decisions are made automatically based on the spending budget limits, per-payment caps, velocity controls, and approval thresholds you configure for each agent. These decisions are deterministic and rules-based — they follow the exact parameters you set, not predictive models or profiling of your behavior.

Within-policy wallet payments may proceed without human review. Transactions above approval thresholds are held for your review (default: 72-hour decision window). Approving a stored wallet request executes it synchronously; there is no separate post-approval card-use window for the current wallet flow. When a transaction is declined by the policy engine, the reason for the decline (such as an exceeded budget, payment cap, or velocity limit) is displayed in your dashboard and recorded in the transaction log. If you believe a transaction was incorrectly declined, you may contact support at [email protected] to request a manual review.

8.1 Wallet infrastructure

Agent wallets are non-custodial and operate on Dakota infrastructure. Dakota is a FinCEN-registered Money Services Business that handles wallet creation, policy enforcement, USD on-ramp/off-ramp, and the underlying compliance obligations. Reinx holds the ECDSA P-256 signing keys (in AWS KMS-backed infrastructure) that authorize each transaction; the keys are never exposed through any API. You can revoke Reinx’s signing authority at any time via Dakota’s signer-group management — at which point Dakota’s native default-deny policy engine blocks any further transaction. Each agent uses a canonical RD wallet on Base. Customer-facing USDC receive channels for supported EVM networks and Solana may use swap-account addresses that normalize incoming funds into that canonical balance; they are not separate outbound wallets.

8.2 Blockchain risks

You acknowledge and accept:

• Public transparency: All blockchain transactions are publicly visible. Wallet addresses and histories are accessible to anyone.
• Irreversibility: Confirmed on-chain transactions cannot be reversed by Reinx.
• Network risks: Congestion, forks, outages, or disruptions may delay or prevent transactions.
• Smart contract risks: Interacting with smart contracts carries inherent risk of bugs, exploits, or unexpected behaviour.
• Regulatory risk: Evolving regulations may affect wallet service availability or functionality.

17.1 By you

Close your account anytime via dashboard or by contacting [email protected]. Active subscriptions terminate at billing period end. You must withdraw all remaining funds before requesting organization closure or deletion; Reinx does not automatically withdraw a remaining balance. Account deletion is blocked while a balance is nonzero or cannot be verified. After closure, agent accounts and wallets are deactivated, any future active card service is closed under its provider terms, and API tokens are invalidated.

17.2 By Reinx

Reinx may suspend or terminate your account for Terms violations, legal/regulatory requirements, suspected compromise or prohibited activity, failure to complete verification, or if your use poses risk. Reinx retains transaction records as required by law (minimum 7 years) regardless of termination.

17.3 Survival

Sections on IP, disclaimers, liability limitation, indemnification, dispute resolution, and general provisions survive termination.

18.1 Informal resolution

Before formal proceedings, you agree to attempt informal resolution by contacting [email protected]. We will attempt to resolve disputes within 60 days.

18.2 Binding arbitration

Arbitration by a single arbitrator in Las Vegas, Nevada or remotely. The arbitrator’s decision is final and binding.

18.3 Class action waiver

18.4 Exceptions

Either party may bring individual small claims court actions or seek injunctive relief for IP infringement.

18.5 Opt-out

Opt out of arbitration/class waiver within 30 days of accepting these Terms by emailing [email protected] with subject “Arbitration Opt-Out” including your name, account email, and clear opt-out statement.