What you need
- MetaMask (or Coinbase Wallet) browser extension or mobile wallet
- Network: Base mainnet (chain ID 8453)
- A little USDC on Base for the skill price
- A little ETH on Base for gas
Add Base and get USDC
In MetaMask, add Base if it is not already present. Official public RPC endpoints are listed by Base docs; many wallets add Base in one click.
Fund USDC on Base. Common path: buy USDC in Coinbase and withdraw to your wallet on the Base network, or use a bridge if your funds start elsewhere. The skill purchase itself is still an on-chain USDC transfer, not a card charge inside LVL.
Open the canary
Go to the live marketplace and open agent-x402-first-buy, or use the pay deep link that starts checkout for that skill. Read the free sample or outline first. The point of the canary is trust in the rails, not content complexity.
Connect and pay
- Connect wallet when prompted (Base network).
- Confirm the listed USDC amount matches the listing.
- Approve USDC spend if the flow uses an allowance, then confirm the transfer.
- Wait for confirmation; keep the tx hash.
- Complete unlock so the site can verify the tx and return sealed files.
After payment
You should receive sealed pack files for the skill. Save them. If download fails, re-redeem with the same transaction proof rather than paying twice. See the sealed packs guide for idempotent re-redeem details.
Verify honesty
Open /api/proof and BaseScan. Confirmed unlocks show skill id, amount, and explorer links. LVL positions itself as verification-first: small real numbers beat invented GMV.
If something breaks
- Wrong network: switch to Base (8453)
- No ETH: fund gas
- USDC on Ethereum mainnet instead of Base: bridge or withdraw again on Base
- Tx succeeded but UI stuck: keep tx hash, retry unlock / support path with proof
Next steps
Once the canary works, try a higher value skill only after reading its free outline. For agent automation, hand the same skill id to an HTTP buyer using /api/shop and /api/pay.
Why start at five cents
The canary skill is priced to make mistakes cheap. You might pick the wrong network once. You might forget gas once. You might mis-click a wallet account. Five cents plus gas teaches the loop without turning a mistake into a painful story.
After one successful canary, your confidence in LVL rails should come from your own explorer links, not from anyone's landing page claim.
Wallet setup detail
Install MetaMask from the official site. Create or import a wallet you control. Write down the seed phrase offline. Never paste a seed into lvlltd.com. LVL should never ask for a seed phrase.
Add Base mainnet. Confirm chain ID 8453. If a dapp prompts to switch network, read the prompt. Scams often try to switch you to unknown chains.
Funding paths that actually work
Path A: Coinbase account, buy USDC, withdraw to your MetaMask address on Base. Path B: bridge from another chain using a reputable bridge UI. Path C: another user sends you USDC on Base. All paths end the same: USDC balance on Base in the paying account.
Separately acquire Base ETH for gas. The amount is usually small, but zero ETH means zero transfers.
Using the marketplace UI
Open Hub marketplace. Find agent-x402-first-buy or use the deep link with buy and pay query params. Read sample content. Click buy or pay. Connect wallet. Confirm the USDC transaction. Wait for confirmation banners. Download or copy sealed files when the unlock succeeds.
If the UI stalls after a successful BaseScan transfer, do not spam new payments. Keep the hash. Retry unlock. That discipline saves money.
Reading the transaction on BaseScan
Open the transaction. Confirm token transfer of USDC. Confirm destination. Confirm status success. Compare amount to the listing. This is the same habit agents should encode in software.
After the canary
Try a tripwire skill only if the free outline is strong. Climb prices as trust compounds. For teams, document which wallet is the company buyer wallet and who holds the seed under your security policy.
Privacy notes
Base transactions are public. Skill unlock amounts and addresses can be correlated. Use fresh wallets if that matters for your threat model. Do not put personal data into skill inputs you would not want logged by your own agent runtime.
Support posture
When asking for help, provide skill id, txHash, approximate UTC time, and whether unlock returned an error body. Screenshots of wallet activity help. Never send seed phrases.
Field notes from live rails
Everything in this guide is meant to match production behavior on lvlltd.com: free outlines at /skills/{id}/outline.json, challenges at /api/pay, settlement in USDC on Base chain ID 8453, unlock proofs that can be checked on BaseScan, and a public ledger at /api/proof that refuses to invent volume. If a third-party article disagrees with those primary surfaces, trust the primary surfaces.
When you teach teammates, walk them through one canary unlock before any architecture debate. Shared scars on a $0.05 purchase create better systems design conversations than slides alone. Keep notes on what confused people; those notes should become checklist items in your internal runbook and, if you sell skills, clearer outline text for the next buyer.
Finally, remember the integrity line that LVL repeats for a reason: understanding is free; sealed capability is optional and paid. Education pages like this one should make you more demanding, not more impulsive. Read outlines. Allowlist addresses. Prefer small spends first. Verify. Then scale.
Related live checks
After reading, run at least two live checks: open the free outline for a skill you care about, and open /api/proof. Optionally issue a pay challenge with curl and confirm you see HTTP 402 with amount and payTo fields. Those three actions connect this article to production reality in under two minutes.
If you maintain internal wiki mirrors of these guides, include the canonical URLs on lvlltd.com so agents and humans can detect drift. Canonicals and llms.txt exist so education stays discoverable next to commerce, not buried in a slide deck.