**TL;DR:** Index names allow only lowercase alphanumeric characters and dashes. No dots, no uppercase, no emoji. Index name rules that reject your create call The rules 1. Length: your index name plus your project ID (normally seven alphanumeric characters) plus one separating dash must not exceed 52 characters.

## The fix

1. **Characters:** UTF-8 lowercase alphanumeric Latin characters and dashes only. No uppercase, no dots, no underscores, no emoji, no non-Latin scripts.

2. **No dots, ever.** Dots separate hosts and subnets in DNS, which Pinecone uses for routing. `my.index` is invalid.

3. **Length:** your index name plus your project ID (normally seven alphanumeric characters) plus one separating dash must not exceed 52 characters. The project ID counts, so a long name that fits alone can still fail.

4. Generate index names programmatically: lowercase, dashes, short prefix plus a suffix (`docs-v2`, `tenant-embeddings`).

5. Validate before calling: `re.fullmatch(r"[a-z0-9-]+", name)` and `len(name) + 8 <= 52`.

6. Never derive an index name from a tenant name, email, or free-text field without sanitizing. That is how dots and uppercase sneak in.

## When to use this

- This covers exactly what the title says: Pinecone index name rules.
- You are setting this up for the first time, or auditing an existing setup.
- You want the key gotchas in one place before you start.

## When not to use this

- You are doing a different workflow with Pinecone; these steps are specific to the title above.
- You need the full reference docs; this is the short path, not the manual.

## Compatibility

- Not pinned to a specific version; follows current Pinecone behavior.

## Edge cases

- The confusing variant is the length cap: the name looks fine, but name plus project ID overflows.