[qirh]

Summary

• Perplexity would like to identify Markra requests in API attribution data.
• Send X-Pplx-Integration: markra on requests whose configured destination is exactly api.perplexity.ai.
• Apply the default through the shared provider-header path used by chat, Responses, and model discovery.
• Preserve caller-provided attribution case-insensitively and leave proxy traffic unchanged.

Verification

• Request-builder coverage confirms direct Perplexity requests receive the default, lowercase caller overrides are preserved, and lookalike proxy hosts remain unchanged.

[vercel]

@qirh is attempting to deploy a commit to the murongg's projects Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

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

Project	Deployment	Actions	Updated
markra-web	Ready	Preview	Sep 20, 2026 8:03am UTC

[murongg]

Markra already supports custom request headers through customHeaders, which users can use to set X-Pplx-Integration: markra. Could you clarify why this needs to be added automatically in code instead of using the existing custom headers feature? Is there a requirement for attribution to be enabled by default without user configuration?

[qirh]

Fair question. customHeaders works, but most users won't set it, so a built-in default is the only way we actually see Markra traffic, and a user's own value still takes precedence.