01 The agreement
These Terms of Service (the “Terms”) are a binding agreement between you (“you,” “Customer,” or the autonomous agent you operate) and CR3 Labs, operator of Vectorway (the “Service”).
By accessing the Service, connecting a wallet via Sign-In With Ethereum (SIWE) or Privy, minting an API key, paying for credits, or calling any API endpoint, you agree to these Terms and our Privacy Policy. If you do not agree, do not use the Service.
If you accept these Terms on behalf of a legal entity, you represent that you are authorized to bind that entity, and references to “you” include that entity. Autonomous agents operated by a principal bind that principal.
02 Accounts & API keys
A Vectorway account is created on first successful SIWE sign-in or first successful /v1/auth/agent-onboard call. The account is keyed to the wallet address that authenticated.
- You are responsible for safeguarding the private key controlling your wallet and any API keys minted from your account. We cannot recover them.
- You are responsible for all activity under your account, including all calls made by automated agents acting on your behalf.
- API keys are revocable at any time from the dashboard. Revocation is immediate.
- We may suspend or terminate an account that violates these Terms, that we reasonably believe is fraudulent or compromised, or that is the subject of a credible legal request.
03 Credits & payments
Vectorway offers two billing paths on a single endpoint, and you choose per request which one to use:
- Pay-per-call (x402). Each request is billed individually in USDC, signed and settled directly by your wallet over the Coinbase x402 protocol. No account, no top-up, no balance kept with us.
- Prepaid credits (API key). You may optionally pre-fund a wallet-scoped credit balance and authenticate per request with an
x-api-key. Credits are debited from that balance as you call the Service.
Credits are denominated as a single integer unit where one credit equals one atomic unit of USDC (i.e., 0.000001 USDC, ~$0.000001). Credits are sold in USD via Stripe Checkout or in USDC via x402, at the linear list rate posted on the pricing page and in the dashboard (currently $1 = 1,000,000 credits). Credits are a service voucher, not a fixed currency exchange — see the “No custody” bullet below.
A small initial credit grant may be issued, at our discretion, to a new wallet that signs in through the dashboard’s bot-resistance gate. The grant amount, current rate, and any promotional credits are posted in the dashboard and may change at any time.
How payments are processed
- USDC via x402. The Coinbase x402 facilitator verifies and settles your USDC payment directly between your wallet and our receiving address on the underlying blockchain. Vectorway never takes custody of your wallet, your private keys, or the in-flight USDC. Settlement is governed by the blockchain network and by Coinbase’s facilitator service, not by us.
- USD via Stripe. Card and bank payments are processed by Stripe, Inc. (and its local subsidiaries) under Stripe’s own terms. Stripe handles card data, fraud screening, KYC/AML where required, chargeback resolution, and any merchant-of-record obligations applicable to your transaction. Vectorway does not see, store, or transmit your full card number.
- No custody. Credit balances are an internal accounting record of prepaid API usage. They are not a deposit, an account balance with a financial institution, e-money, a stored-value instrument, or a claim on Vectorway for cash or crypto. Credits have no cash value, are not redeemable for currency, and cannot be transferred between accounts.
Refunds, chargebacks, and disputes
- Crypto payments are final. USDC transfers on a blockchain are irreversible. Because we do not custody funds, we cannot reverse, claw back, or re-route an on-chain payment. If you sent USDC in error, contact support@vectorway.io and we will help where reasonable, but we make no guarantee of recovery.
- Card disputes. Refund and chargeback rights for Stripe payments are determined by Stripe and the card networks. Initiate refund requests with us; chargebacks go through your card issuer. Filing a chargeback for a charge you actually authorized may result in suspension of your account and forfeiture of the disputed credits.
- Service-side refunds of credits. We make best-effort refunds of credits (not cash or crypto) when a billable failure was caused by our infrastructure. We are not obligated to refund for upstream model-provider failures or for content you simply did not like.
Other payment terms
- Pricing. Per-token rates by model and the credit-to-USD rate are listed in the dashboard, on the pricing page, and (where applicable) in
/openapi.json. Most chat completions are billed per token of input and output, not per call. We may change pricing prospectively; existing balances stay denominated in credits. - Reservation, settlement, and refund. On the API-key path, an upper-bound number of credits is reserved from your balance at request time and the actual token cost is computed once the upstream model returns; any overcharge is automatically refunded to your balance the same request. On the x402 path, your wallet authorizes an upper-bound USDC amount on the 402 challenge, and the facilitator settles the actually-used amount per call (subject to a small minimum settlement floor — currently $0.001 — to satisfy the facilitator’s lower bound). On a 5xx server-side failure the entire reservation is refunded; on a 4xx caller error no settlement occurs because no work was done. Memory writes are billed as part of the same per-token settlement, not as a separate fee.
- Expiry. Credits do not expire while your account remains active. Inactive accounts (no successful auth and no API call for 24 months) may have their unused credit balance expired on 30 days’ notice to the contact email on file, if any.
- Taxes. Prices exclude taxes. You are responsible for any sales, VAT, GST, or similar taxes applicable to your purchase, except for taxes on our net income. Stripe may collect applicable taxes on our behalf where required.
- Sanctions & KYC. Stripe and the x402 facilitator each apply their own sanctions screening and, where applicable, KYC/AML controls. If a payment is rejected, frozen, or reversed by Stripe, the x402 facilitator, your bank, or your wallet provider, the corresponding credits will not be issued and we are not liable for that third party’s decision.
04 Acceptable use
You will not, and will not allow any agent acting on your behalf to:
- Use the Service to generate or distribute content that is illegal in your jurisdiction or ours, including CSAM, content that infringes third-party rights, or content that materially impersonates a real person to defraud.
- Attempt to extract model weights, system prompts, internal tooling instructions, or otherwise reverse-engineer the Service except as expressly permitted by law.
- Use the Service to generate weapons of mass destruction, malware, or to facilitate attacks on third-party systems.
- Submit other people’s personal data into long-term memory without a lawful basis.
- Bypass rate limits, abuse Turnstile, or share API keys publicly.
- Use the Service in connection with any sanctioned jurisdiction or sanctioned person under U.S., UK, or EU sanctions law.
We may suspend access immediately and without notice if we reasonably believe continued use would expose us or other customers to legal, financial, or operational risk.
05 Your content
You retain all rights in the prompts, files, and memory entries you submit (“Customer Content”) and the responses generated for you (“Output”). You grant us a narrow, worldwide, non-exclusive license to process Customer Content only as needed to operate the Service for you and to perform under these Terms.
We do not use Customer Content or Output to train, fine-tune, or evaluate any machine-learning model.
Model providers may have their own usage policies that flow through to you (e.g. content policies for Gemini). You are responsible for complying with the policy of the underlying provider for the model you choose to call.
06 Memory & data
The memory endpoints persist what you write for a configured retention window — currently seven (7) days from the last write — after which entries are removed automatically. The retention window is set by the operator (see REDIS_MEMORY_TTL_SECONDS) and may change as the Service evolves. You can list, search, and delete memory entries at any time via the API or the dashboard, and you may explicitly remove an entry before its TTL expires. We do not read your memory contents except to operate the Service or as required by law.
The Service is not designed or certified for regulated data (HIPAA PHI, PCI primary account numbers, classified information, etc.) and is not a system of record. Treat the memory endpoints as a recall cache, not a backup; if you need long-term durable storage of a memory entry, persist it on your own infrastructure as well.
07 Service changes
We iterate quickly. We may add, change, deprecate, or remove API endpoints, models, and dashboard features. We will give reasonable prior notice (typically posted at /docs or in /openapi.json) before breaking changes to documented public endpoints.
We do not commit to backwards compatibility for endpoints or behaviors marked “preview,” “experimental,” or undocumented.
08 Third parties
The Service depends on third parties listed in our Privacy Policy (model providers, Vercel, Redis, Privy, Coinbase x402 facilitator, Stripe, Cloudflare Turnstile). Their outages, errors, or policy changes can affect your use of the Service. We are not responsible for failures attributable to a third party, but we will use reasonable efforts to route around them when feasible.
09 Disclaimers
The Service is provided “as is” and “as available.” To the maximum extent permitted by law, we disclaim all warranties, express or implied, including merchantability, fitness for a particular purpose, non-infringement, and any warranty arising from course of dealing or usage of trade.
Large language model output is probabilistic and can be wrong, biased, or unsafe. Do not rely on the Output for medical, legal, financial, or other decisions without independent verification by a qualified human. You are responsible for any action you or your agent takes based on Output.
Cryptocurrency and on-chain settlement involve risk. Network conditions, smart-contract bugs, stablecoin de-pegs, and bridge failures can cause loss. You accept that risk when paying in USDC. Because CR3 Labs does not custody funds and does not control Stripe or the x402 facilitator, we are not liable for the acts, omissions, fees, downtime, or insolvency of those third-party payment providers, the underlying blockchain, or any wallet you use to pay us.
Nothing in the Service constitutes financial, investment, banking, money-transmission, exchange, custodial, or tax advice. We are not a bank, a broker-dealer, a money services business, a money transmitter, an exchange, or a custodian, and Vectorway must not be used as one.
10 Limitation of liability
To the maximum extent permitted by law:
- Neither party is liable for any indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, revenue, data, or goodwill, even if advised of the possibility.
- Our total aggregate liability arising out of or relating to the Service is capped at the greater of (a) the amount you paid us for credits that were actually consumed by your calls to the Service in the 12 months immediately preceding the event giving rise to the claim, or (b) USD $100. For the avoidance of doubt, unused credit balance, pending top-ups, refunded amounts, and on-chain transfers that were never converted into consumed API usage do not count toward the cap.
Some jurisdictions do not allow these limits; in those jurisdictions our liability is limited to the maximum extent permitted by law.
11 Indemnity
You will defend, indemnify, and hold harmless CR3 Labs and its officers, directors, employees, and contractors from any third-party claim arising out of: (a) your use of the Service, (b) Customer Content you submit, (c) your violation of these Terms or applicable law, or (d) your infringement of any third-party right. We will give you prompt notice of the claim and reasonable cooperation in the defense.
12 Governing law & disputes
These Terms are governed by the laws of the State of Delaware, USA, excluding its conflict-of-laws rules and excluding the UN Convention on Contracts for the International Sale of Goods.
Any dispute arising out of or relating to these Terms or the Service shall be resolved by binding arbitration administered by JAMS under its Streamlined Arbitration Rules, in the English language, in Wilmington, Delaware, by a single arbitrator. Judgment on the award may be entered in any court of competent jurisdiction. Each party waives any right to a jury trial and to participate in a class action.
Notwithstanding the foregoing, either party may seek injunctive or equitable relief in any court of competent jurisdiction to protect intellectual property rights or to prevent unauthorized access to the Service.
13 General
- Entire agreement. These Terms and any documents incorporated by reference (including the Privacy Policy and any order form you sign with us) are the complete agreement on this subject.
- Severability. If any provision is unenforceable, the remaining provisions stay in effect.
- No waiver. A delay in enforcing a provision is not a waiver of it.
- Assignment. You may not assign these Terms without our written consent. We may assign to an affiliate or in connection with a merger or sale of assets.
- Notices. We may give notice via the dashboard, API response headers, the contact email on your account (if any), or by posting to this page. Notices to us must go to legal@vectorway.io.
- Changes to these Terms. We may update these Terms by changing the effective date above. Material changes will be surfaced in the dashboard. Continued use of the Service after the effective date constitutes acceptance.
14 Contact
Legal notices and contract questions: legal@vectorway.io.
Security reports: security@vectorway.io.
General support: support@vectorway.io.