Fix API key prefix documentation - keys use plln_pk/plln_sk not pk_/sk_

[voodoohop]

Current situation:

• API keys actually start with plln_pk_ (publishable) and plln_sk_ (secret)
• Documentation incorrectly states they start with pk_ and sk_

Issues:

• AGENTS.md shows examples with pk_ and sk_ prefixes
• Actual implementation uses plln_pk_ and plln_sk_ prefixes
• Confusing for developers following the docs

Options to consider:

1. Update docs to reflect actual plln_pk_/plln_sk_ format
2. Consider shortening to pln_pk_/pln_sk_ (simpler, follows Stripe pattern)
3. Move the type indicator (pk_/sk_) before the vendor prefix for clarity

Current code:
src/client/routes/index.tsx:93 - Uses plln_pk and plln_sk as prefixes

@PrimeevolutionZ

[voodoohop]

@claude what do you think? what is best practice? can you implement? simple minimal and sweet

[claude]

Claude finished @voodoohop's task —— View job • claude/issue-5329-20251116-1426 • Create PR ➔

---

Todo List

• Read current documentation to verify incorrect examples
• Read actual implementation to confirm correct prefixes
• Provide best practice recommendation
• Update documentation with correct prefixes
• Search for other references to incorrect format
• Commit and push changes

---

Analysis

Current situation verified:

• Documentation incorrectly stated keys start with pk_ and sk_
• Actual implementation uses plln_pk and plln_sk (lines 93-94 in src/client/routes/index.tsx)
• Found 3 files with incorrect references

Best practice recommendation:

Keep plln_pk_ and plln_sk_ format ✅

Reasoning:

• ✅ Clear vendor identification (Pollinations)
• ✅ Type indicator follows vendor prefix (industry standard pattern)
• ✅ Already implemented in code - just needed docs updated
• ✅ Similar to established patterns: stripe_pk_, sk_test_, etc.

Why not the alternatives:

• pln_pk_/pln_sk_: Less clear abbreviation, harder to recognize
• Moving type before vendor (pk_plln_): Breaks common pattern where vendor prefix comes first

Changes Made

Updated all documentation references from pk_/sk_ to plln_pk_/plln_sk_:

• ✅ enter.pollinations.ai/AGENTS.md - 9 replacements (key type descriptions, examples, troubleshooting)
• ✅ enter.pollinations.ai/RATE_LIMITER_FIX_COMPLETE.md - 1 replacement (test example)
• ✅ AGENTS.md - 1 replacement (API gateway section)

Summary

Simple, minimal, and sweet as requested! The fix keeps the existing plln_pk_ and plln_sk_ format that's already in the code and just updates the docs to match. This is the standard pattern - vendor prefix first, then type indicator.

---

[zubairgitteam]

where do you get the secret key, i am not able to find it.

[PrimeevolutionZ]

where do you get the secret key, i am not able to find it.
https://enter.pollinations.ai/