Skip to main content
ARouter supports optional HTTP headers that identify your application in API requests. These headers are used for source tracking in the ARouter Dashboard — giving you per-app analytics and usage breakdowns across multiple projects or workflows under a single account.

Headers

HTTP-Referer

Your application’s URL. Used to identify the source of the request.

X-Title

Your application’s display name. Shows up in your Dashboard activity view.

Implementation

Include these headers in any request to the ARouter API:

App Categories

Categorize your application to appear correctly in ARouter’s analytics: Pass the category as part of your X-Title header or as a dedicated header if supported by your integration. The category appears in your Dashboard analytics alongside the app name.

Dashboard Activity

When you include attribution headers, the ARouter Dashboard displays:
  • App Name: Shown in the activity feed and analytics per request
  • Source URL: Used to group requests by application domain
  • Category: Appears in usage breakdowns by app type
  • Per-app usage: Token consumption, cost, and request volume per attributed app
This is especially useful when:
  • Managing multiple applications under one account
  • Running A/B tests across different app versions
  • Understanding which workflows drive the most usage

Benefits of Attribution

  • Usage breakdown by app — See which of your applications consumes the most tokens and cost
  • Traffic analysis — Understand request volume patterns per app
  • Optimization signals — Identify high-cost workflows for optimization
Attribution headers are ARouter-side only and do not affect model behavior, routing, or the upstream provider.