One session. One thread.
Stable session IDs map a harness conversation to its Perplexity thread, keeping subsequent turns attached to the same conversation.
Perplexity-2-APIMore context.One continuous thread.
Bring a signed-in Perplexity web session into your local developer workflow. Keep harness sessions connected to their own persistent conversation.
Windows 10 / 11 · x64 · WebView201 / A LITTLE HANDS-ON
Get a feel for it.
An interactive, illustrative preview in your browser. The real application runs on your Windows desktop.
Your clientLOCAL WORKFLOW
Perplexity Bridge127.0.0.1:8082
Your sessionWEB SESSION
Sample session
curl http://127.0.0.1:8082/v1/chat/completions \
-H 'Authorization: Bearer YOUR_LOCAL_KEY' \
-H 'Content-Type: application/json' \
-H 'X-Perplexity-Session-Id: YOUR_UNIQUE_SESSION_ID' \
-d '{"model":"perplexity-auto","messages":[{"role":"user","content":"Hello"}]}'Visual demonstration — no live API call.
ILLUSTRATIVE DEMO · PREPARED SAMPLE CONTENT · NO FILE UPLOADS
Made for local workflows.
Use the local API and integration helpers with supported clients. Your harness remains responsible for any local tool permissions.
Context, with checkpoints.
Large context transfers use bounded fragments and validation. Persistent session mappings help maintain continuity across restarts.
- 01
Install the desktop bridge
Use the x64 installer. The release includes .NET; WebView2 Evergreen Runtime must also be installed.
- 02
Sign in and start the endpoint
Sign into Perplexity in the embedded browser, verify your account, and create a local API key.
- 03
Give every session an identity
Use the documented helper or send X-Perplexity-Session-Id with a unique, stable ID for each conversation.
MAKE IT PART OF YOUR EVERYDAY
Get Perplexity-2-API.
Windows 10 / 11 · x64 · WebView2
MIT licensed
Independent experimental project. Website changes and account limits can affect operation. Session identity is required for generation.
Integration helpers and additional packages on GitHub Releases ↗
Is this the official Perplexity API?+
No. The official API is a separate product. This independent project uses undocumented web interfaces and is not affiliated with or endorsed by Perplexity.
Why is a session ID required?+
It identifies which ongoing conversation should receive a request. Requests without a stable session identity are rejected rather than silently starting a new thread.
Does the bridge grant access to local files?+
No. Your harness controls local tools and permissions. The bridge translates tool requests; verify important work using actual tool results.