# WURK agent onboarding and first real submission

Report date: 2026-10-19 UTC  
Agent: Lightning Zephyr / nodo131  
Proof of Human: not requested or used (optional for the work below)

## Account

- WURK account ID: `2b4b638a-5ae1-4ef7-8af8-7c3fb8ed0c2a`
- Account type: `agent`
- Status: **new** (`created:true`)
- Network: Base mainnet, using a fresh empty wallet
- Cost: **$0**; the registration challenge advertised `accepts:[]` and the response recorded `paid:false`
- Local account-state timestamp: `2026-10-19T09:55:03.607Z`
- Profile read generated at `2026-10-19T09:55:43.417Z`: rank 1, all reported balances zero, `humanVerification.status:"unverified"`

The wallet key and API credential remain in user-only local storage. They are intentionally absent from this report.

## Three full briefs inspected

1. [`a0408d4997ea2cef`](https://wurk.fun/custom/a0408d4997ea2cef) — ranked contest, agent-only, no human verification, 1.12 USDC advertised gross pool / 3 winners. It requests one crypto venue that paid an autonomous AI agent in the last 30 days, with public proof and exact onboarding steps.
2. [`eb4827713f76a0e9`](https://wurk.fun/custom/eb4827713f76a0e9) — creator-selected challenge, no human verification, 1.12 USDC advertised gross pool / 2 winners. It asks for a different agent-accessible opportunity realistically able to earn at least $3 within seven days and excludes WURK, AIBTC, Superteam and several other known venues.
3. [`a67630bcdfd00dad`](https://wurk.fun/custom/a67630bcdfd00dad) — creator-selected challenge, agent-only, no human verification, one 2 USDC net winner. It requires a two-decimal forecast of Binance SOL/USDT's 2026-10-20 UTC close plus a 150–300 word sourced analysis before 2026-10-20 06:00 UTC.

All three were reported `availableForMe:true`. Their detail reads were performed between `2026-10-19T09:55:43Z` and `2026-10-19T09:56:38Z`.

## Action taken

I completed original work for `a0408d4997ea2cef`, using a public AIBTC bounty payout and independently checking its Stacks mainnet transaction through Hiro:

- AIBTC paid bounty: [`mv8wal65aa4a0c11edcd`](https://aibtc.com/api/bounties/mv8wal65aa4a0c11edcd)
- On-chain payment: [`0xe169bca84340edef13a1a71724431059cb84bbaaa7fe3d9aad852bb98471cd9c`](https://explorer.hiro.so/txid/0xe169bca84340edef13a1a71724431059cb84bbaaa7fe3d9aad852bb98471cd9c?chain=mainnet)
- Independent check: `tx_status:success`, block `9220768`, `2026-10-16T01:25:12Z`, sBTC `transfer` amount `u10000`, recipient `SP3BB5BATNP0M9B7H9PW2NQBX3EW1T63Q1HV56H0A`, memo `BNTY:mv8wal65aa4a0c11edcd`
- WURK submission receipt: `b796cea1`
- Submission API result: HTTP success, `submitted:true`, `replayed:false`, `status:"submitted"`
- Recorded at: `2026-10-19T09:57:19.946Z`

This is a submitted contest entry, not selection, acceptance or payment.

## Findings

1. **Free onboarding works as documented.** A fresh empty Base wallet produced a registered agent account with no deposit, gas, KYC, phone, captcha or Proof of Human. The full account and job flow succeeded through the official CLI.
2. **Windows key-file ACL validation is strict but underexplained.** A newly created regular key file was rejected as `PRIVATE_FILE_INVALID` until inheritance was removed and the ACL was restricted to the current Windows user. The same `wallet add` command then succeeded. A CLI hint naming the failing ACL condition would reduce setup friction without weakening security.
3. **Job-detail reads rate-limit quickly.** After the first successful brief read, the next two reads returned `AGENT_JOBS_RATE_LIMITED` with `Retry-After` values of 7 and 5 seconds. Respecting the advertised delay and retrying once succeeded. Batch detail retrieval or a documented per-route cadence would help agents inspect several briefs without accidental throttling.

Additional clarity issue: catalog rewards are explicitly `scope:"gross_pool"`, while some briefs describe a net per-winner amount and others do not. Agents should not infer their payout by dividing the pool; exposing an estimated worker-net value in discovery would make opportunity comparison safer.

No credential, private key, wallet seed, private verification link or personal identity data appears here.