半自动的就行，准备手动拿验证码撸，自己写了一半不想写了 
这个有啥用，弄很多key的号池吗
那难道也不会触发那个分钟限制嘛，感觉他说1分钟60次是虚假的
完全没必要，一个key一分钟四十次，注册俩就够用了，卡跟key限流没关系，一万key轮询照样卡死，老黄的这个好像是一批显卡共享资源的，用的人多就卡
平台是靠ip限速的，再多key也没用，热门模型首字几分钟以上，只能离线跑。
感觉没必要，热门模型可用性太差了
确实没见过英伟达注册机,老黄的验证好麻烦
那还不如用公益站，里面很多国模，直接爽吃
差个庄，希望可以搞一批次，然后体验下无限蹬
老黄的key 我放cpa 使用codex去调用 很多codex工具使用不啊 正常的搜索都做不到
老黄的平台太卡了，负载低，你两三个号也够用，负载高，你整几百个号也没用
大家只是给你建议，告诉你做这件事的性价比。 希望交流的时候用词文明一些
给我整不会了，都来我这水评论了，我不来气么，我前面几个贴都解释过了，有需求而已。
总结一个龙虾用的有头skill，需要的可以参考一下
---
name: nvidia-build-registration
description: Drive NVIDIA Build (https://build.nvidia.com/) registration/login flows in browser with customizable IMAP email verification. Use when the user asks to register, login, create, verify, or onboard an NVIDIA Build/NIM/NVIDIA Cloud Account through the browser. Supports any IMAP-compatible mailbox (Gmail, Outlook, custom domains, etc.) for email verification.
---
# NVIDIA Build Registration Workflow
Use browser automation for the visible website flow and IMAP email fetch for verification.
## Prerequisites — Collect Before Starting
Before running the flow, obtain these from the user (or use provided defaults):
| Parameter | Required | Default | Notes |
|-----------|----------|---------|-------|
| `email` | Yes | — | The email to register with |
| `imap_host` | Yes | — | IMAP server (e.g. `imap.gmail.com`) |
| `imap_port` | No | 993 (SSL) / 143 (plain) | Auto-set based on SSL flag |
| `imap_ssl` | No | true | Use SSL/TLS for IMAP connection |
| `imap_user` | No | same as `email` | IMAP login username if different |
| `imap_password` | Yes | — | IMAP password or app-specific password |
| `org_name` | No | email localpart | NVIDIA Cloud Account organization name |
| `sender_filter` | No | `nvidia` | Substring to match in From/Subject when searching inbox |
**Gmail users:** Must use an [App Password](https://myaccount.google.com/apppasswords), not the account password.
Ask the user for missing required parameters before proceeding. Do not guess or hardcode credentials.
## Browser Flow
1. Open `https://build.nvidia.com/`.
2. Click `Login`.
3. Enter the user's email in the modal, click `Next`.
4. If NVIDIA shows "Verify Your Email" with "click the link in the email", fetch the newest NVIDIA email from the IMAP inbox (see **Email Verification** below).
5. Navigate the browser to the extracted verification link. Success state is `Verification Successful!`.
6. Return to `https://build.nvidia.com/`, click `Login` again, enter the same email, and continue.
7. If shown `Almost done!` recommendation/subscription checkboxes, leave unchecked unless user asked otherwise, then click `Submit`.
8. If shown `Create NVIDIA Cloud Account`, fill organization/account name. Use a simple alphanumeric name derived from email localpart (e.g. `user` from `user@example.com`) unless user specified another, then submit.
9. Verify success by returning to Build home and checking that the top-right button says `Profile` (or similar account/avatar state), not `Login`.
## Email Verification
Use IMAP to fetch the NVIDIA verification email. Adapt this pattern to the user's mailbox:
```python
import imaplib, email, email.header, html, re, time
# --- Fill from prerequisites ---
IMAP_HOST = 'imap.gmail.com' # e.g. imap.gmail.com, imap.outlook.com, imap.example.com
IMAP_PORT = 993 # 993 for SSL, 143 for STARTTLS/plain
USE_SSL = True # True for SSL, False for STARTTLS or plain
IMAP_USER = 'user@example.com'
IMAP_PASS = 'app-specific-password'
SENDER_FILTER = 'nvidia' # substring to match in From/Subject
MAX_ATTEMPTS = 12 # polling attempts
INTERVAL = 5 # seconds between attempts
def decode_header_value(raw):
return str(email.header.make_header(email.header.decode_header(raw or '')))
def connect():
if USE_SSL:
return imaplib.IMAP4_SSL(IMAP_HOST, IMAP_PORT)
conn = imaplib.IMAP4(IMAP_HOST, IMAP_PORT)
conn.starttls()
return conn
for attempt in range(1, MAX_ATTEMPTS + 1):
try:
M = connect()
M.login(IMAP_USER, IMAP_PASS)
M.select('INBOX')
_, data = M.search(None, 'ALL')
if data[0]:
for num in data[0].split()[::-1]:
_, msgdata = M.fetch(num, '(RFC822)')
msg = email.message_from_bytes(msgdata[0][1])
subj = decode_header_value(msg.get('Subject', ''))
frm = decode_header_value(msg.get('From', ''))
if SENDER_FILTER.lower() not in (subj + ' ' + frm).lower():
continue
bodies = []
for part in msg.walk() if msg.is_multipart() else [msg]:
if part.get_content_type() in ('text/html', 'text/plain'):
payload = part.get_payload(decode=True)
if payload:
bodies.append(payload.decode(part.get_content_charset() or 'utf-8', 'ignore'))
text = '\n'.join(bodies)
for m in re.finditer(r'href=["\']([^"\']+)["\']', text, re.I):
url = html.unescape(m.group(1))
if 'profile-management/verify-email' in url:
print(url)
M.logout()
exit(0)
M.logout()
except Exception as e:
print(f'Attempt {attempt} error: {e}', file=__import__('sys').stderr)
if attempt < MAX_ATTEMPTS:
print(f'Attempt {attempt}: no match yet, retrying in {INTERVAL}s...', file=__import__('sys').stderr)
time.sleep(INTERVAL)
print('No NVIDIA verification link found.', file=__import__('sys').stderr)
exit(1)
```
### Manual Fallback
If IMAP is unavailable or the user prefers manual verification:
1. Ask the user to check their inbox for the NVIDIA email.
2. Ask them to copy the verification link (containing `profile-management/verify-email?code=...`).
3. Navigate browser to that link.
## Pitfalls
- **Verification link parsing:** Always extract `href="..."` from HTML and HTML-unescape `&`. Never reconstruct URLs from raw quoted-printable snippets — soft line breaks corrupt `code=` / `locale=` parameters.
- **OTP vs CSS colors:** NVIDIA emails may contain decorative CSS like `color: #666666`. Do not treat every 6-digit number as an OTP. Parse the phrase `Your verification code is:` and accept formats like `300-001`.
- **Token expiry:** If a code or link fails, restart from `https://build.nvidia.com/` instead of retrying stale tokens.
- **CAPTCHA boundary:** Do not solve CAPTCHA/hCaptcha/reCAPTCHA automatically. Stop at CAPTCHA, ask the user to complete it manually, then resume after confirmation.
## Verification Checklist
Before final reply, confirm:
- Build page loaded after onboarding.
- Header shows `Profile` / avatar / account state instead of `Login`.
- No unresolved verification page, expired token page, or pending NVIDIA Cloud Account creation page remains.
- Report the email and organization name used.