Maple Proxy
Get started with Maple Proxy
Connect your tools to Maple with the desktop app's local proxy. Set the base URL, choose a model, and send a first request, or run Docker or a binary yourself.
Maple Proxy gives tools that support OpenAI Chat Completions a local endpoint for Maple’s private models. It verifies Maple’s secure enclave and encrypts traffic from the proxy to Maple.
API access requires Pro, Max or Team; API usage is billed separately. See pricing.
Desktop app
The Maple desktop app includes the proxy for macOS, Windows and Linux.
- Download Maple and sign in.
- Open Settings, then API & credits under Developer.
- Open the Local Proxy tab and select Start proxy.
Maple creates and saves a proxy key if you have not set one. Copy the base URL from this screen; the default is http://127.0.0.1:8080/v1. Keep Maple open while using connected tools.
With the default CORS setting off, this request uses the saved key because it omits Authorization:
curl -N http://127.0.0.1:8080/v1/chat/completions \
-H "Content-Type: application/json" \
-d '{
"model": "gpt-oss-120b",
"messages": [{"role": "user", "content": "Write a haiku about privacy"}],
"stream": true
}'The first request can take longer while the proxy verifies the enclave. For problems starting it, see troubleshooting.
Connect an application
Choose an OpenAI-compatible / Chat Completions provider and enter:
| Setting | Value |
|---|---|
| Base URL | http://127.0.0.1:8080/v1 (or the URL shown in Maple) |
| API key | A real Maple API key if the tool requires one; create a key |
| Model | An exact ID from models and capabilities |
Some applications expect the URL without /v1; check their instructions. A placeholder key overrides the saved key and fails authentication.
Follow the OpenCode or Goose guide, or use the API reference for your own application.
Desktop settings
Under Advanced settings, change the port, enable Auto-start when Maple launches, or select Enable CORS for browser clients. With CORS on, every client must send its own key. See authentication.
Keep the proxy local
Traffic between your application and the proxy is plaintext. Keep the host on 127.0.0.1 for tools on your computer. If that traffic leaves your machine, protect it with TLS and a trusted network boundary.
Docker or binary
Run a dedicated proxy beside your service or on a machine without the desktop app. See Docker and binary setup.
Last updated