Aere Cloud · developer service

Your users never need to hold gas.

Live Keyed & metered ERC-4337 Passkey smart accounts

Endpoint cloud.aere.network/v1/sponsorAuth your Aere Cloud API keyChain 2800

The first transaction is where most crypto products lose the user: they arrive with no token, and nothing works until they buy one. Gas sponsorship removes that wall. Your backend makes one keyed call; the Foundation relayer deploys the user’s smart account and pays the gas. The user signs with a passkey and is on-chain, with zero AERE in hand.

How it works

Your user creates a passkey in their browser (Face ID, Touch ID, a security key) — no seed phrase.
Your backend calls /v1/sponsor/createAccount with your API key; the relayer deploys their ERC-4337 smart account and pays the gas.
The user signs their transactions with the passkey; your backend relays them through /v1/sponsor/execute.
Usage is metered per API key and shows up in your console under sponsored operations.

Why it is safe by construction

The smart account validates every signature itself. The relayer only pays gas — it never sees a user’s key and cannot move a user’s funds. So even a fully compromised relayer could waste its own gas budget and nothing more; user assets stay out of its reach by the design of the account, not by our promise.

Onboard a gasless user

POST https://cloud.aere.network/v1/sponsor/createAccount
x-api-key: ak2800.<your-address>.<secret>
{ "initialOwners": ["0x…passkey-derived…"], "salt": "0x…" }

# the relayer deploys the account and pays the gas;
# your user never held a single wei of AERE

Honest phase-1 limits

Stated up front, the same as the public relayer: today it runs a single relayer account with no high-availability failover. If it is down, users who already hold AERE can still transact directly; new gasless onboarding pauses until it is back. The keyed route adds authentication and per-key metering on top of that engine, and a redundant relayer is on the roadmap.

Get an API key

Part of Aere Cloud. Full API reference and the wallet-infrastructure engagement that builds the complete passkey flow are in the docs.