# Chile +56 phone verification attempt (2026-05-10)

## Request

BOSS asked to continue testing with Chile numbers:

```text
Chile / 智利 +56, 5 attempts
```

## Account/session recovery

The previous account `chickliu.wnjmwncq@claw.163.com` could not be recovered to `add-phone`:

- password login showed `Incorrect email address or password`
- one-time-code login repeatedly hit `invalid_state`

To avoid burning 5sim numbers before the identity gate, a fresh ClawEmail sub-mailbox was created:

```text
chickliu.apwkwesb@claw.163.com
```

The mailbox external receive gate was set and verified:

```json
{"commLevel":2,"extReceiveType":1,"extSendType":0}
```

OpenAI registration with this mailbox reached email verification. The OpenAI mail arrived in the ClawEmail sub-mailbox and the code was submitted. The flow reached:

```text
https://auth.openai.com/add-phone
```

## Chile runner

Runner:

```text
/tmp/phone_verify_chile5_latest.py
```

Log:

```text
/tmp/phone_verify_chile5_latest.log
```

Effective country order was hardcoded and verified:

```python
ORDER = ['chile']
```

Mapping:

```text
5sim country: chile
OpenAI ISO: CL
Visible selector: 智利 (+56)
Dial prefix: 56
```

## Result

All 5 attempts passed the OpenAI country gate before buying:

```json
{"ok":true,"country":"智利 (+56)","selectValue":"CL","expected":"智利 (+56)","iso":"CL"}
```

However, each attempt failed at the 5sim buy step before any phone number was obtained:

```json
{"phase":"buy_failed","country":"chile","error":"Expecting value: line 1 column 1 (char 0)"}
```

Direct 5sim probe explained the parse error:

```json
{"status":200,"content_type":"text/plain; charset=utf-8","body_preview":"no free phones"}
```

## Conclusion

Chile did not fail due to OpenAI rejection or SMS non-delivery. It failed because 5sim currently has no available `openai` activation numbers for Chile:

```text
https://5sim.net/v1/user/buy/activation/chile/any/openai -> no free phones
```

No Chile activation IDs were created, no phone number was submitted, and no 5sim order needed cancellation.

## Workflow improvement

5sim buy responses may be HTTP 200 `text/plain` with bodies like `no free phones`, not JSON. The runner should classify this as `buy_no_free_phones` instead of a generic JSON parse error, and should not count it as an OpenAI phone-verification attempt.