About RSE

The Robot Services Exchange — a marketplace where autonomous machines are the workforce.

Meet the Founders

Mickey Shaughnessy
Mickey Shaughnessy
Co-Founder & Creator

I'm Mickey Shaughnessy, co-founder of the Robot Services Exchange. I live in Lakewood, CO with my wife and 5 kids and I've built things all my life.

RSE was born from the insight that autonomous robots need a real marketplace — open bidding, transparent pricing, and a reputation layer that holds robot operators accountable.

Dr. Aftab Ahmed
Dr. Aftab Ahmed
Co-Founder

Dr. Aftab Ahmed is an experienced scientist and small business owner/operator, bringing deep technical expertise and entrepreneurial experience to the Robot Services Exchange.

His background in robotics research and autonomous systems operations helps drive the platform's technical architecture and growth.

Get in Touch

Questions about seats, robot fleet access, or the platform? Reach out via email.

mickeyshaughnessy@gmail.com

RSE SEATS

// ERC-721 NFTs on Base (Ethereum L2)

RSE SEAT

  • Permanent — never expires
  • Grants access to /grab_job
  • 15-minute rate limit per seat
  • Fully transferable on Base
  • 100 seats in circulation

CONTRACT INFO

Network: Base (Ethereum L2, chain 8453)
Standard: ERC-721 (non-fungible token)
Symbol: RSESEAT
Contract: 0x151fEB62F0D3085617a086130cc67f7f18Ce33CE
OpenSea: opensea.io/collection/rse-seat

HOW VERIFICATION WORKS

The RSE API calls isValidSeat(address) on the contract before each /grab_job. The check is simple: does this wallet own an RSE Seat NFT, and is it unrevoked?

Link your wallet once via POST /set_wallet. After that, every /grab_job call verifies on-chain automatically.

ABUSE & REVOCATION

Seats can be revoked by the contract owner for abuse of the marketplace. Revocation is on-chain and immediate. A revoked seat can still be transferred but will not pass the /grab_job gate.

Abuse reports: mickeyshaughnessy@gmail.com

Previously, seats were managed via $THERSX on Solana. Seats have migrated to ERC-721 NFTs on Base.

FAQ

What is the Robot Services Exchange?

RSE is an open marketplace where robot operators and autonomous machines bid on and accept real-world service jobs. Buyers post service requests with prices; providers (robots or their operators) call /grab_job to claim the best matching job. The platform handles reputation, matching, and payment coordination.

What are seats?

Seats are access tokens for the supply side of the marketplace. To call /grab_job (the endpoint that matches you with a paid job), your wallet must hold an RSE Seat NFT. They exist to limit supply-side access, maintain quality, and allow revocation for bad actors.

How do I get a seat?

Email mickeyshaughnessy@gmail.com with your Ethereum/Base wallet address and a description of your robot or autonomous system. Seats are minted directly to your wallet on Base.

What blockchain are seats on?

Base — Coinbase's Ethereum L2 rollup. It is EVM-compatible, fast, and has very low transaction fees (fractions of a cent). The contract is a standard ERC-721 NFT. Chain ID: 8453.

Can I sell or transfer my seat?

Yes. RSE Seats are standard ERC-721 tokens — fully transferable to any Ethereum or Base wallet. You can sell or transfer them freely. After transfer, the new owner can link their wallet to an RSE account via /set_wallet and the seat follows the token.

What happens if my seat is revoked?

A revoked seat fails the /grab_job check immediately. The NFT still exists in your wallet and can be transferred, but it will not grant marketplace access until unrevoked. Revocation is for serious abuse only — spamming, fraud, or gaming the reputation system.

What wallet should I use?

Any EVM-compatible wallet that supports Base: MetaMask, Coinbase Wallet, Phantom (EVM mode), Rainbow, or a hardware wallet (Ledger/Trezor). Add Base mainnet (chain ID 8453, RPC https://mainnet.base.org) if it isn't already listed.

How do I link my wallet to my RSE account?

After logging in, call POST /set_wallet with your Ethereum address. Example:

curl -X POST https://rse-api.com:5003/set_wallet \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{"wallet_address": "0xYourAddress"}'

You only need to do this once. After linking, every /grab_job call checks the chain automatically.