Skip to content
中文Sign inRaise GPU yieldStart mining
Menu

Terms of service

Last updated: 22 October 2026. Version 1.6.

1. About these terms

These terms are an agreement between you and Extra Watts B.V., which runs Peryn.

  • Legal name and legal form: Extra Watts B.V. (besloten vennootschap)
  • Registered in the Netherlands. Chamber of Commerce (KvK) number: 75938650
  • Address: Herengracht 420, 1017 BZ Amsterdam, Netherlands
  • VAT number: NL860448769B01
  • Email: hello@peryn.ai
  • Legal notices: legal@peryn.ai
  • Privacy: privacy@peryn.ai
  • Security contact: security@peryn.ai

These terms include our acceptable use policy and the licences of the models you use (section 9). Our privacy policy explains how we handle personal data.

By creating an account, using an API key or enrolling a GPU node, you accept these terms. If you accept them for a company or other organisation, you confirm you may bind it, and "you" means that organisation.

Some parts apply differently to consumers (people acting outside their trade or profession): see section 5 (right of withdrawal), section 15 (liability) and section 17 (disputes). Nothing in these terms takes away rights that consumer law gives you.

2. The service

Peryn has three parts:

  • The API. An OpenAI-compatible API for text generation with open-weight models, at https://api.peryn.ai/v1 (it also answers at its earlier address, https://api.ai.pearlsafe.xyz/v1). The list of models and their current prices is at https://api.peryn.ai/v1/models.
  • The web chat at chat.peryn.ai, for signed-in users.
  • The miner program. GPU operators run our node software and either the open-source Pearl miner or, on consumer GPUs in switching mode, their own mining software beside a model server we name. Their nodes serve requests and mine PRL, the Pearl network's coin, through our mining pool (in switching mode, at the pool the operator chooses). Section 12 has the rules. The miner portal is not open yet (see section 12).

The developer console on the website lets you manage API keys, buy credits and see your usage.

Features marked "coming soon" on the site are not part of the service until we launch them.

3. Your account

  • You must be at least 18 years old to use the service.
  • The service is meant for business and developer use. If you are 18 or older, you may also use the web chat for personal use. Consumers may buy credits to use the web chat beyond the free allowance. The API is for business and developer use.
  • You sign in with a link we email to you. Keep access to that inbox secure: anyone who can read it can sign in as you.
  • Give us an email address you control, and keep it up to date.
  • You are responsible for everything done with your account and your API keys. Keep keys secret. If you think a key is exposed, revoke it in the console straight away.
  • One account per person for any free allowance (section 5).

4. Privacy tiers

Each API key has a privacy tier. Requests made with that key use that tier.

  • Standard. We do not log or store your content. The same GPU work also mines PRL.
  • Private. We do not log or store your content. Requests are never used for mining and run only on vetted nodes. Priced on the cost of the GPU, because it earns no mining income (section 6). We offer it for a model only once we have measured that model's throughput.

The privacy policy explains each tier, including what our mining pool can see on Standard requests.

Where requests run. GPU nodes may be in any country. By default a request runs on any healthy node. You can set region rules for your account or for an API key (for example "EU only" or "exclude these countries"), and we then route your requests only to matching nodes. If no matching node is available, the request fails rather than running elsewhere. The country where a request ran is shown in your usage logs and in an API response header. A node's country comes from its operator's declaration and a check of its IP address. A dishonest operator could fake both, for example with a VPN. We remove nodes we catch doing this. For the strongest assurance, combine region rules with the Private tier, which runs only on vetted nodes. "EU only" is not the default. If you need your data to stay in a region, for example for your own legal obligations, it is your responsibility to set region rules.

5. Credits and payment

  • Prepaid. The API is prepaid. You buy credits in US dollars. Each request is charged against your credits.
  • Payment. You add credits with USD stablecoins (USDC) sent to your account's own deposit address, or, where the console offers it, by card through our payment provider. A card payment is credited once our payment provider confirms it to us. A stablecoin deposit is credited once the block that holds it is final on its network.
  • Stablecoin deposits.
    • Your account has its own deposit address. The console shows it after you accept these terms. A deposit sent before you accepted them is held until you do.
    • We credit native USDC sent on the networks the console lists (Base, Arbitrum and Ethereum). 1 USDC adds 1 US dollar of credit, at the full amount received. Network fees are yours.
    • Other tokens, other networks, and ETH sent to a deposit address are not credited. We hold them and, after a check, try to send them back to the address they came from. We may deduct the network fee of the return.
    • Deposits under 1 US dollar are held until your held deposits reach 1 US dollar, then credited together.
    • We check the sending address against sanctions lists. We may hold a deposit while we review it. We do not credit a deposit from a sanctioned address, and the law may require us to block it.
    • Blockchain transactions are public and cannot be reversed. Check the address and the network before you send.
  • Other tokens, through Relay. Where the console offers it, you can also add credits by sending USDT or another listed token to a deposit address that Relay (Uneven Labs, Inc.), a third party, provides for your account.
    • Relay converts what you send and delivers it to your account's deposit address as USDC on Base. We credit the USDC that arrives, under the rules above. The rate and fees are Relay's, set when your deposit arrives; the console shows an indicative quote only.
    • Relay's own terms apply to the conversion. We are not a party to it, and we do not hold your tokens while Relay converts them.
    • Send only the token, on the network, that the console shows for that address. Other tokens sent to it are lost.
    • You give a refund address you control on the network you send from. Do not give an exchange deposit address. If Relay cannot complete a deposit, it may refund it there, less network fees. Relay does not refund deposits sent from Tron automatically, and a deposit stopped by Relay's own compliance checks is not refunded automatically; such a deposit is returned, if at all, only after a manual review with Relay.
    • Deposits through Relay under 10 US dollars are held until your held deposits through Relay reach 10 US dollars, then credited together. Deposits over 10,000 US dollars are credited after a manual check.
    • We check the address your deposit was sent from, and your refund address, against sanctions lists, as for any deposit. On Tron we also refuse a refund address that Tether has frozen. We may hold a deposit until Relay tells us where it came from.
  • Accounts billed monthly. By separate written agreement, we may bill a business monthly instead, up to an agreed credit limit. Usage is then invoiced once a month in US dollars, payable in USD stablecoins or by bank transfer within the agreed payment term. The agreement says what happens if an invoice is not paid on time.
  • How a request is charged. When a request starts, we set aside enough credit to cover its highest possible cost (based on its maximum output length). When it ends, we charge the actual cost and release the rest. If you do not have enough credit, we may refuse the request.
  • Token counts. We charge by tokens. Our own count, made with each model's tokenizer, is the one we bill.
  • Refunds. Credits are non-refundable, except where the law requires a refund.
  • Consumers: right of withdrawal. If you are a consumer in the EU, you may cancel a credit purchase within 14 days of buying it, without giving a reason, by emailing legal@peryn.ai. We then refund the unused part of that purchase within 14 days. When you buy credits, you ask us to start the service straight away. If you use credits during those 14 days, you pay for what you used.
  • Expiry. Unused credits expire after 12 months without activity on your account. Activity means signing in, making a request charged to your credits, or buying credits. We will email you at least 30 days before your credits expire.
  • Taxes. Prices exclude VAT. We add VAT where the law requires it, and checkout shows the total, including any VAT, before you pay. Customers in the Netherlands pay Dutch VAT. Business customers in another EU country who give us a valid VAT number pay no Dutch VAT (the reverse-charge rule applies). Consumers in another EU country pay the VAT of their country.
  • Chargebacks. If a payment is reversed, we may remove the matching credits and suspend the account until it is resolved.
  • Free allowance. Signed-in users of the web chat get a free allowance of up to 50,000 tokens a day, reset at 00:00 UTC, for use in the web chat only. We can change or end it at any time. It may not be resold (see the acceptable use policy).

6. Prices

  • Prices change. Our prices are dynamic. We may recalculate them as often as every hour.
  • Standard prices are set with reference to what other providers charge for the same model. We never price below a floor that covers what we pay the GPU operator.
  • Private prices are based on the cost of running the GPU plus a margin, because Private requests earn no mining income.
  • Where to see them. Current prices are shown at https://api.peryn.ai/v1/models and on the website.
  • Which price applies. A request is charged at the price in effect when it starts. A price change never applies to credits you have already used.

7. Availability

  • We provide the service on a best-effort basis. We do not offer a service level agreement (SLA) yet.
  • Requests run on a network of GPU nodes, and capacity varies. When we are full, we reject requests (HTTP 429) rather than queue them.
  • We may add, change or remove models. Models depend on the Pearl network, and upgrades to that network can change which models we can serve.
  • We may change or stop parts of the service. If we stop the API for good, we will tell account holders at least 30 days in advance, so you can use your credits. We refund unused paid credits where the law requires it.

8. Acceptable use

You must follow our acceptable use policy. It also applies to your end users if you build the API into your own product.

9. Model licences

Each model is licensed by its maker. Your use of a model, and of its output, is also subject to that licence and its use policy. The current list is on our model licences page.

  • Llama 3.1 8B Instruct. Built with Llama. Llama 3.1 is licensed under the Llama 3.1 Community License, Copyright © Meta Platforms, Inc. All Rights Reserved. You must follow the Llama 3.1 Community License and the Llama 3.1 Acceptable Use Policy. If you use Llama output to create, train or improve an AI model that you distribute or make available, the licence requires that model's name to start with "Llama".
  • Gemma 4 31B IT. Google publishes Gemma 4 under the Apache License 2.0. The version we serve is Pearl Research Labs' quantized copy of Gemma 4. When you use it through our service, you must also follow Google's Gemma Prohibited Use Policy.
  • Qwen3 30B A3B Instruct (not offered yet). The Qwen team at Alibaba Cloud publishes it under the Apache License 2.0. You must follow its licence terms when we offer it.

When we add models, we will list their licences on the model licences page before we offer them.

10. Your content and the output

  • Your input. You keep all rights in what you send us. You give us only the right to process it to answer your request. We do not store it and do not train on it.
  • Output. As between you and us, you own the output, to the extent anyone can. We claim no rights in it. Other users may receive similar or identical output.
  • Your responsibility. You must have the rights to the input you send, and you are responsible for how you use the output.
  • Output can be wrong. Models make mistakes. Output can be inaccurate, incomplete, offensive or out of date. Check it before you rely on it. Do not use it as a substitute for professional advice, for example medical, legal or financial advice.

11. Our rights

We own the service, our software, our website and our brand. These terms do not give you any rights in them, except the right to use the service as these terms allow. The open-source Pearl miner, the model server, the models and any mining software an operator runs are licensed by their own makers.

If you send us feedback, we may use it without obligation to you.

12. Miner program

This section applies if you enrol a GPU node or mine with our pool. The miner portal is not open yet. Until it opens, only nodes we operate serve customer requests.

12.1 What you do

  • You run a GPU node with our node software (the node agent) and the miner image we provide, which contains Pearl's open-source miner and model server. In switching mode (consumer GPUs), you run our node software and the model server release we name, started through the check and with the settings we ship, beside your own mining software, which never handles requests.
  • Your node connects to us, serves the inference requests we send it, and mines PRL through our pool (in switching mode, your miner mines at the pool you choose and is paused while a request runs).
  • You enrol a node in the miner portal with a one-time enrolment token. A new node starts as "pending".
  • Nodes and miners may be in any country, subject to section 12.6.
  • You declare your node's country when you enrol it. We check it against the node's IP address and may stop routing to a node whose country does not match.

12.2 Vetting and routing

  • We decide which requests go to which node, and whether a node receives any requests at all.
  • A new node receives customer requests only after we approve it. After that, an active, healthy node may receive Standard requests.
  • Private-tier requests go only to vetted nodes: nodes we run, or nodes of operators we have approved for that tier. Before we approve an operator, we check who they are, where and how the node is hosted, and that they have signed our data processing terms. We decide which operators to approve.
  • We send nodes hidden test requests ("canary checks") that look like customer requests, to check that they serve the model they claim and follow these terms. By joining the program you accept these checks. A node that fails stops receiving requests.

12.3 Your obligations

You must:

  • run our node software and our miner image, or in switching mode the model server release we name, unmodified, at the versions we tell you to use, with the settings we ship, including the logging settings and the start-up check that enforces them;
  • never log, store, inspect, copy or share customer content, and never run anything on the node that reads the content of requests, for example by reading the model server's memory or capturing its traffic;
  • keep the node and its private key secure, and tell us within 24 hours if you think the node, its key or any customer content has been exposed;
  • declare your node's true country, and tell us before you move it;
  • make sure your hosting provider allows mining and this kind of use;
  • comply with the laws that apply to you, your node and your payouts, including the local law where you and your node are, and make sure that running the node and receiving payouts is legal there;
  • follow the acceptable use policy, including its rules for miners.

You pay your own costs: hardware, GPU rental, power and connectivity.

Personal data. Customer requests can contain personal data. When your node processes them, you process that data on our behalf, as our processor under the GDPR (or our sub-processor, where we act for a business customer). Our data processing terms for operators are part of these terms, and you must follow them. If your node is outside the EU/EEA, they include the EU Standard Contractual Clauses where applicable.

12.4 $PEARL mining rewards

  • The pool. Our pool runs on the Pearl network. The Pearl network and PRL are not ours. We do not control them.

  • Pool fees. Until the first block at Pearl's FP8 upgrade height (the "upgrade block"), 0% on PPLNS. From the upgrade block's time: 1% on PPLNS and 2% on FPPS. We show the fees in force on our pool page and in the miner portal.

  • PPLNS ("pay per last N shares"), the default. When the pool finds a block, the whole reward is split among workers in proportion to the work in their recent accepted shares. "Recent" means the latest shares whose total difficulty adds up to twice the network difficulty. Any pool fee is then taken from each miner's part separately.

  • FPPS ("full pay per share"). We may offer FPPS instead of the split above. Until we offer them, every share counts under the split above, and mode=fpps in a rig's password has no effect. Once we offer them, you choose for each rig, by adding mode=fpps to the rig's password, or for your account in the miner portal. A choice applies to shares accepted after it takes effect.

    • Each accepted share is then credited its average value: the share's difficulty divided by the network difficulty at that time, times the block subsidy at the share's height, plus a share of transaction fees as shown on our pool page. We take the FPPS fee shown in the miner portal and on our pool page from that value.
    • You are credited for every accepted share, whether or not the pool finds a block. Blocks found with FPPS shares belong to us.
    • Credits are added every few minutes and paid with your other $PEARL in the daily payouts, under the same minimum and rules.

  • Holds and reviews of FPPS credits. We may hold FPPS credits before we pay them:

    • for a few days, when a new account or address credits a large amount;
    • during a review, when the blocks found with an account's shares fall far short of what those shares should have found.

    We pay held credits once the hold ends or the review is cleared. If a review shows that blocks were withheld, or another breach of these terms, we may withhold the held credits (section 12.6).

  • Limits and switching back to PPLNS. We may limit how much FPPS work we accept. When the limit is reached, new choices of FPPS count under the split above until there is room. We may pause FPPS at any time, for example to protect the pool's reserve. From a pause on, every share counts under the split above until we resume. Credits already made stay yours.

  • Founding Miners. Founding Miners of Season 1 pay 0% on PPLNS and 1% on FPPS on their verified addresses, from verification until six calendar months after the upgrade block's time, then the fees above. See the Founding Miner terms.

  • Maturity. A block reward can be paid only after it has 100 confirmations. If a block is orphaned (dropped from the chain), it pays nothing, and any credit for it is reversed.

  • Shares. Every share must pass Pearl's own verification. We may reject shares that do not. Shares from times when your node is serving Private requests are discarded and earn nothing.

  • Payouts. The minimum payout is 1 $PEARL; less stays owed until a later batch. We prepare payout batches daily at 02:00 UTC. A batch is sent only after we approve it. Payouts go to the $PEARL address you set in the miner portal, or, when you mine with a $PEARL address as your username and no account, to that address.

  • We may change these parameters. We will announce changes in the miner portal at least 30 days in advance, unless a change is needed sooner for security or because of a Pearl network upgrade. In that case we give as much notice as we can.

12.5 USDC earnings for tokens served

  • For each customer request your node serves, you earn USDC at the miner rate for that model. Rates are per million tokens, with separate rates for input and output tokens. The current rates are shown in the miner portal.
  • Token counts are our gateway's count. It is the one we use, also for your earnings.
  • We also pay you, at the same rates, for requests from our free chat allowance and for our hidden test requests (section 12.2).
  • USDC is paid on the Base network to the address you set. The minimum USDC payout is 10 USDC. A person approves and sends every USDC payout batch.
  • If a customer's payment is later reversed, your earnings for requests you already served are not affected, unless you took part in the fraud.

12.6 Payout review, delays and screening

  • Payouts may be delayed while we review them, for example after failed test requests, unusual share patterns or suspected breaches of these terms, or for operational reasons such as refilling the payout wallet.
  • Sanctions and export controls. We screen payouts against sanctions lists before we send them, and we may ask you to verify your identity and location. We may withhold or refuse payouts, and stop working with you, where sanctions or export-control laws apply, including those of the EU, the Netherlands and the United States. By joining the program you confirm that you are not a sanctioned person and are not owned or controlled by one.
  • We may withhold earnings that result from a breach of these terms.
  • Blockchain payments cannot be reversed. Check your payout address. We are not responsible for payments sent to an address you gave us.
  • We may need to collect more information from you, or report your earnings to tax or other authorities, where the law requires it.

12.7 No guaranteed earnings

  • Mining rewards depend on luck, network difficulty, your hardware and how much traffic we send you. You may earn nothing.
  • The value of PRL can rise or fall, and may be zero. PRL is not an investment product offered by us.
  • Changes to the Pearl network, such as upgrades ("forks"), can change what your node can mine or serve.
  • You are responsible for your own taxes on what you earn.

12.8 Bans and leaving

  • Our pool automatically blocks a worker for a while if too many of its shares are invalid.
  • We remove nodes and ban operators who cheat, for example by manipulating shares, misreporting their work or handling test requests differently from customer requests (see the acceptable use policy, section 3).
  • We may also suspend or remove a node, or ban an operator, for any other breach of these terms or the acceptable use policy.
  • You can stop mining and remove your node at any time. When you leave, we pay out your remaining balance in the next payout batch, even if it is below the minimum payout, as long as it is larger than the network fee for sending it. If we ban you for a breach, we may withhold earnings linked to the breach (section 12.6) and pay out the rest in the same way.
  • You are an independent contractor. These terms do not create an employment relationship, partnership or joint venture.

12.9 Incentive programs

From time to time we run incentive programs that pay miners USD or USDC for accepted mining work, on top of PRL. Each program publishes its own rate or pot, its dates, who can take part and how rewards are paid. For every program:

  • Budget-limited. A program pays only up to its budget. When the budget is spent, rewards stop, even before the program's end date.
  • It can change or end. We may change a program's rates, caps or dates, or end it early. A change applies from the next accrual and never takes away rewards already paid.
  • Held rewards. Part of a reward may be held until a later date and paid only if you are still mining then, as the program says. What miners give up this way may be shared among those who qualify.
  • A USDC address in your login. Where a program lets you give a USDC address when you connect (for example usdc= in the stratum password), rewards for the shares sent with that login belong to that address, and are paid to it in USDC on the network you chose. Check the address: a payment to an address you gave cannot be reversed. When logins of one worker name different addresses at the same time, or none, the reward is kept for your PRL address; you can send it to a USDC address by signing a message with that PRL address.
  • Mining with an address only. Rewards kept for a PRL address are paid once you send them to a USD stablecoin address, or link the address to your account, by signing a message with that PRL address (only its key can move them). A linked address's mining counts for your account in our incentive programs, within the limits each program sets. Rewards not claimed within 90 days after the program ends (or the period the program sets) are forfeited.
  • Founding Miners. A program may make miners who meet its published conditions Founding Miners, with the 0% pool fee of the Founding Miner terms on the address or account that qualified.
  • Abuse voids rewards. We may hold, refuse or take back rewards not yet paid out if we believe they were earned by gaming the program: for example short bursts of borrowed hashrate, withholding blocks, or many accounts for one operator. Our own machines never earn rewards.
  • Paid like other USD earnings. Rewards are paid with your USD payouts, or in the program's own USDC payouts, after the same screening (section 12.6), and are subject to section 12.7.

13. Suspension and termination

  • You can stop using the service and close your account at any time by emailing hello@peryn.ai from the address on your account (or privacy@peryn.ai to also have your personal data deleted).
  • We may suspend or close your account, revoke keys or stop routing to your node if you breach these terms or the acceptable use policy, if the law requires it, or if your use puts the service or others at risk. Where we can, we will tell you first and explain why.
  • Unused credits when an account closes. When an account closes, whether you or we close it, unused credits are not refunded, except where the law requires a refund (for example under the right of withdrawal in section 5).
  • Sections that by their nature should survive (for example 10, 14, 15 and 17) continue after the account is closed.

14. Disclaimers

The service is provided "as is" and "as available". To the extent the law allows, we give no warranties, express or implied, including about fitness for a particular purpose, accuracy of output, or uninterrupted availability. We give no warranty about model output (section 10). Consumers keep their statutory rights.

15. Liability

  • Nothing in these terms limits liability that cannot be limited by law, including for intent or deliberate recklessness (opzet of bewuste roekeloosheid) of our management, or for death or personal injury caused by negligence.
  • Our total liability for all claims arising from the service or these terms is limited to the fees you paid us in the 12 months before the event that caused the claim, or EUR 100 if you paid us nothing in that period. This limit does not reduce payouts you have earned under section 12.
  • For business customers and miners: we are not liable for indirect or consequential loss, lost profits, lost revenue or lost data.
  • For miners: we are not liable for changes in the value of PRL or USDC, for the behaviour of the Pearl network or the Base network, or for income you expected but did not earn.
  • For consumers: the limits in this section apply only as far as consumer law allows.

Business customers and miners will compensate us for claims by third parties, and the reasonable costs of those claims, that result from their breach of these terms or the acceptable use policy, or from the content they send through the service.

16. Changes to these terms

We may change these terms. We will post the new version on this page and update the date at the top. For material changes, we will email account holders at least 30 days before they take effect. If you do not agree, stop using the service before the change takes effect. If you keep using it, the new terms apply.

17. Governing law and disputes

These terms are governed by the laws of the Netherlands. Disputes go to the competent court in Amsterdam, the Netherlands. If you are a consumer in the EU, you also keep the protection of the mandatory laws of your country, and you may bring a claim in the courts where you live.

18. Contact

Extra Watts B.V., Herengracht 420, 1017 BZ Amsterdam, Netherlands. Email: hello@peryn.ai. Legal notices: legal@peryn.ai. Privacy: privacy@peryn.ai. Security: security@peryn.ai.