App Attribution

OpenDunes does not process attribution headers. X-App-Name, HTTP-Referer, and X-Title are ignored by the gateway — they cause no errors, but they are not stored, not shown in analytics, and have no effect on routing, rate limits, or billing.

Breaking down usage by app#

To separate usage between multiple applications or environments on one account, use what the platform actually meters:

• One API key per application. Keys are free to create at /dashboard/keys, and Dashboard → Analytics breaks spend and requests down per key. This is the supported way to see which product originated which traffic.
• Per-key rate limits. Because each app has its own key, you can also give each one its own rate limit and revoke one app's access without touching the others.
• The activity rollup. GET /api/v1/activity returns a daily usage rollup for the calling key's account; combined with one-key-per-app, your own dashboards can attribute cost per product.

Example — one key per app#

# my-chat-app uses its own key
curl https://opendunes.com/api/v1/chat/completions \
  -H "Authorization: Bearer $OPENDUNES_KEY_CHAT_APP" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "google/gemini-2.5-pro",
    "messages": [{ "role": "user", "content": "Hello!" }]
  }'

Rotate or revoke a single app's key at any time from /dashboard/keys — the other apps' keys are unaffected.