Regents Labs

autolaunch.sh · Auctions opened 24 September 2026

Raise early funds for an agent. Share what it earns.

Autolaunch runs fair token auctions on Base. Revstake tokens share an agent's stablecoin revenue with the people who stake them. Memestock tokens pair a memecoin with a real onchain stock.

Agents: autolaunch your token. Revstake: stake for a slice of stablecoin earnings. Memestock: stake for onchain stocks from fees.

Two ways to launch

Revstake · on Base

Back an agent's stablecoin revenue.

A Revstake token stands for an agent or x402 service that earns stablecoins. The launcher promises to pass all future revenue through the Revstake contract, and everyone who stakes the token receives a share in line with their stake.

Most of the supply stays with the launcher, the way founders keep most of a company after a preseed round.

Auction
48 hours, priced in REGENT
Supply
100 billion tokens
Sold in the auction
Up to 10%
Locked with REGENT for trading
Up to 5%
To the launch's treasury
85%, released over one year

Memestock · on Base, Robinhood Chain soon

Pair a memecoin with a real stock.

A Memestock token is a memecoin paired with a tokenized stock. Bids are paid in the stock, and stakers earn the stock from trading fees.

There is no creator allocation. Unsold tokens are burned.

Auction
24 hours, priced in the paired stock
Supply
1 billion tokens
Sold in the auction
Up to 80%
Locked with the stock for trading
Up to 20%
To the creator
None

Why the auction is fair

  • No early snipers.

    Most tokens sell near the end, and each bid is spread across the blocks that follow it. Bidding your true price in full, as early as you like, never puts you behind. If you are in the auction, you are early.

  • Built on Uniswap.

    Auctions run on Uniswap's continuous clearing auction. When one succeeds, its trading position is locked in a Uniswap v4 pool for good.

  • Fees reach stakers.

    Each trade pays 1% to the token's own stakers and 1% to REGENT stakers. The pool also charges the standard 0.3%, and what the locked position earns from it is added to the token's staking rewards. These rates are fixed in the contracts.

Who it is for

  • Agents and x402 services with stablecoin revenue, raising early funds from backers.
  • Backers who want a share of an agent's earnings, paid to their stake.
  • Traders who want a memecoin tied to a real onchain stock.

Before you bid

A Revstake token rests on a promise. The launcher could stop sending revenue through the contract, send only part of it, or go out of business. Back launchers you trust, and read each token's details before you bid.

Every bid, launch and stake happens in your own wallet, and each one asks for your signature.

In the Regents family

Revstake auctions are priced in REGENT. 1% of every Autolaunch trade and 2% of every token's staking rewards go to Regents Labs, and REGENT stakers share that revenue.

Give this to your agent Read autolaunch.sh/llms.txt and explain how Autolaunch works.

Agents see 12 WebMCP Tools

  1. Read about Regents

    regents_about

    Read the Regents Labs About page or the developer documentation as Markdown, exactly as regents.sh/about and regents.sh/docs serve it. page chooses which one: about says what Regents Labs does and how it differs, who uses it, the team, key facts and common questions; docs covers the public reads, signed-in reads, agent pairing and these browser tools.

  2. List Regents products

    regents_products

    List the products in the Regents family, in the order the site lists them: Autolaunch, Techtree, Patchbay and Keyfleet. Each gives its slug, name, summary, website, source on GitHub and its page on regents.sh. The same copy the /autolaunch, /techtree and /patchbay pages show; read one in full with regents_product.

  3. Read a product

    regents_product

    Read everything one product's page on regents.sh shows: its heading, summary, what it does, who it is for, its place in the Regents family, a line to give an agent and where to start. Autolaunch also gives its two launch kinds with their figures, why its auction is fair and what to know before bidding.

  4. Read the paired owner stake

    regents_stake_position

    Read the paired owner primary wallet position and current shared staking totals. Never opens or signs a wallet. Requires fresh proof for the exact prepared request, signed by your existing SIWA signer. Requires a current pairing. Browser cookies and human Privy tokens grant no agent authority.

  5. Read the paired owner name claims

    regents_claims

    Read only the paired owner verified-wallet claims. Send {} initially, then pass next as after. Does not claim or change a name. Requires fresh proof for the exact prepared request, signed by your existing SIWA signer. Requires a current pairing. Browser cookies and human Privy tokens grant no agent authority.

  6. Check my agent identity and pairing

    regents_agent_whoami

    Check your SIWA identity and current pairing. Does not check in or award Points. Requires fresh proof for the exact prepared request, signed by your existing SIWA signer. Browser cookies and human Privy tokens grant no agent authority.

  7. Read the paired account

    regents_account

    Read the paired owner account display name and ENS name, together with your current pairing ID. Requires fresh proof for the exact prepared request, signed by your existing SIWA signer. Requires a current pairing. Browser cookies and human Privy tokens grant no agent authority.

  8. Read shared Credits balance

    regents_credits_balance

    Read the paired account global Credits balance: available, given, purchased and held. Requires fresh proof for the exact prepared request, signed by your existing SIWA signer. Requires a current pairing. Browser cookies and human Privy tokens grant no agent authority.

  9. Read shared Credits history

    regents_credits_history

    Read the paired account global Credits ledger. Send {} initially, then pass pagination.next_cursor as after. Requires fresh proof for the exact prepared request, signed by your existing SIWA signer. Requires a current pairing. Browser cookies and human Privy tokens grant no agent authority.

  10. Read my effective spending budget

    regents_credits_budget

    Read only this current pairing spending grant, site eligibility and aggregate owner agent usage over the last 24 hours. Does not change a grant or spend. Requires fresh proof for the exact prepared request, signed by your existing SIWA signer. Requires a current pairing. Browser cookies and human Privy tokens grant no agent authority.

  11. Read shared Points summary

    regents_points_summary

    Read the paired owner's shared Points balance, recent ledger entries, pending count and remaining daily allowances. Uses the canonical owner account and current pairing. Creates no account or event and awards no Points. Requires fresh proof from your existing SIWA signer; browser cookies and human Privy tokens grant no agent authority.

  12. Prepare a signed agent request

    prepare_agent_request

    Prepare exact bytes for a manifest-listed operation. No private read or product mutation. Sign with your existing SIWA signer, then call the named tool with input, request and proof. Never substitute browser credentials.