Add security warning for access token exposure in Pyth Pro

[devin-ai-integration]

Description

Added a security warning callout to the Pyth Pro "Subscribe to Prices" page to alert users not to expose access tokens in frontend applications. The callout emphasizes that access tokens should only be used in secure backend environments.

Type of Change

• New Page
• Page update/improvement
• Fix typo/grammar
• Restructure/reorganize content
• Update links/references
• Other (please describe):

Areas Affected

• pages/price-feeds/pro/subscribe-price-updates.mdx - Added security warning callout after step 1 (acquiring access token)

Checklist

• I ran pre-commit run --all-files to check for linting errors
• I have reviewed my changes for clarity and accuracy
• All links are valid and working
• Images (if any) are properly formatted and include alt text
• Code examples (if any) are complete and functional
• Content follows the established style guide
• Changes are properly formatted in Markdown
• Preview renders correctly in development environment (unable to test locally)

Human Review Checklist

Please verify:

• The callout renders correctly with the warning emoji and styling
• The placement after step 1 is appropriate (alternative: could be placed at step 3 where token is used in code)
• The wording is clear and matches the documentation's tone
• The warning provides sufficient guidance without being overly verbose

Related Issues

This addresses a security concern raised by the team to prevent users from accidentally exposing access tokens in client-side code.

Additional Notes

This is a temporary callout. A dedicated best practices page for Pyth Pro may be added in the future to provide more comprehensive security guidance.

Contributor Information

• Name: Devin
• Email: [email protected] ([email protected])
• Link to Devin run: https://app.devin.ai/sessions/ad6ebd55a7b249108a8afcb3f7ba3dba

[devin-ai-integration]

Prompt hidden (unlisted session)

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Ready	Preview	Comment	Nov 21, 2025 3:46pm
documentation	Error			Nov 21, 2025 3:46pm

[tejasbadadare]

Change this sentence to: "Exposing tokens in frontend code makes them publicly accessible
and is a violation of our terms of service."

[devin-ai-integration]

Thanks for the feedback! I'll update the wording to reference the terms of service violation.