Bot Rentals / How It Works

How renting works

A licence with a clock on it. No hosting, no custody, no subscription.

The model is deliberately boring. You rent software for a period. It runs on your hardware with your credentials. We issue a signed licence that expires. That is the whole arrangement.

The four steps

1. Pay for a period. Rentals are priced in USD and settled in USDC, USDT or SOL on Solana, or USDC on Base, Polygon or Arbitrum. There is no card processing, no account to create, and no stored payment method.
2. Get a licence and a download link. A successful payment returns a licence string and a link to the package. Save the licence. It is a signed token, not a database record — nothing is kept on our side, so if you lose it we cannot look it up. Losing it means paying again.
3. Add your credentials. Every bot ships with an .env.sample. Fill in your own keys. They are read from your environment and never transmitted anywhere except the exchange or RPC endpoint the bot is trading through.
4. Run it. On startup the bot calls /api/license/verify. If the licence is valid it runs; if not it prints why and exits.

What the licence is

A short string containing the bot name, the plan, the issue date and the expiry, signed with a key only we hold. Anyone can check whether one is valid, and nobody can forge or extend one. It is stateless by design — there is no account, no login, and no record of who rented what tied to your identity.

You can check yours at any time:

curl "https://saylorinnovations.com/api/license/verify?key=YOUR_LICENCE"

{ "valid": true, "bot": "bitunix-perps-bot", "plan": "bitunix-7",
  "expiresAt": "…", "daysRemaining": 6.2 }

Expiry and renewal

• The bot re-checks periodically while running, not just at startup.
• If the licence server is unreachable it keeps running on the last good check for up to 72 hours, so a dropped connection or an outage on our side does not abandon an open position.
• When the period genuinely ends, the bot stops starting. Nothing on your machine is touched or deleted.
• Renewing issues a new licence for the same package. Swap the string in your .env and carry on — no reinstall, and your logs and local state survive.
• There is no auto-renewal. Nothing recurring is set up, so there is nothing to cancel.

Why it is built this way

The alternative is hosting the bots and running them for you, which means holding your exchange keys or your wallet. That is a custody arrangement, and it makes us a single point of failure for other people's money. One compromise on our side would drain every renter at once.

Renting the software instead means the worst case for you is that a rental was not worth the money. We cannot lose your funds because we never have them.

Renting programmatically

The whole flow is available to automated clients over x402, with no human step. All routes live on the main domain:

# what can be rented, and for how much
curl https://saylorinnovations.com/api/license/plans

# start a rental — returns 402 with payment terms
curl -i "https://saylorinnovations.com/api/license/buy?plan=pump-trader-1"

# retry with the PAYMENT-SIGNATURE header your x402 client produces
curl -H "PAYMENT-SIGNATURE: <payload>" \
  "https://saylorinnovations.com/api/license/buy?plan=pump-trader-1"

Payment terms are quoted in the 402 response — network, asset, amount and recipient. Prices are re-derived server-side on every request, so the terms in the response are the only ones that will settle. The full manifest is at /.well-known/x402.json.

All rentals → Pump Trader (Rust) →Bitunix Perps Bot →SOLPUMP Dip Monitor →SOLPUMP Trader →LiqMap →Trench →Polymarket Signal Suite → Rental terms →