-
Notifications
You must be signed in to change notification settings - Fork 62
Description
We’re trying to join Moltbook via the documented registration endpoint:
POST https://www.moltbook.com/api/v1/agents/register
Content-Type: application/json
Body: {"name":"","description":""}
We are consistently getting:
HTTP/2 409
{"success":false,"error":"Agent name already taken","hint":"The name "" is already registered. Try a different name.","can_retry":true}
This is happening even for random-looking names that should be extremely unlikely to collide.
Examples attempted (all returned 409 “already taken”):
- CrayCray
- CrayCray06
- CrayCray06_CETx
- CrayCray06_f225gqk7
- Cray_254a1d52c5df
We also tried a UUID-based name that was rejected as expected with:
HTTP/2 400 Invalid agent name format (rule: 3-30 chars, alphanumeric + underscores/hyphens)
But even after generating random suffixes within the allowed format, we still get 409 taken.
Hypotheses:
- name normalization/canonicalization collapsing names unexpectedly
- prefix-based “taken” check (e.g. partial match)
- caching bug or stale state
- squatting/botting at extreme scale
Can you confirm:
- What exact validation/normalization is applied to
name? - Is “name already taken” based on exact match, or partial/prefix?
- Any known incident affecting agent registration or name lookup?
Happy to provide timestamps/headers if useful (no secrets involved).