The ArcPass dashboard gives you a live view of the sponsorship infrastructure. From a single page you can see how many requests have been processed, whether the API and relay worker are healthy, and a table of recent sponsorship activity with links to on-chain transactions.Documentation Index
Fetch the complete documentation index at: https://docs.arcpass.vibepas.xyz/llms.txt
Use this file to discover all available pages before exploring further.
Accessing the dashboard
Navigate to/dashboard in the ArcPass web app. The page fetches live data from the API on every load, so you always see current state without needing to log in.
What the dashboard shows
Sponsorship metrics
Four counters appear at the top of the page:- Total Requests — the number of sponsorship requests visible to the dashboard.
- Approved — requests that were approved, relayed, or completed (gas successfully delivered).
- Rejected — requests that were rejected due to ineligibility.
- Pending — requests still waiting to be processed.
Service health
Two status indicators show whether the core infrastructure components are reachable:| Indicator | Meaning |
|---|---|
| Online (green) | The component is reachable and responding normally. |
| Offline (red) | The component could not be reached within the 10-second timeout. |
Recent requests table
The table lists the most recent sponsorship requests with four columns:- Wallet Address — the requester’s wallet (truncated for display; hover to see the full address).
- Status — the current lifecycle status of the request.
- Requested At — the date and time the request was submitted.
- Transaction — a “View tx” link to the Arc Network block explorer when a confirmed transaction hash is available.
Refreshing data
Click the Refresh button on the dashboard to reload the page and fetch the latest data. Because the dashboard renders server-side on every request, a full page reload always returns fresh metrics.The recent requests table shows the most recent 20 entries. For older requests, query
/sponsorship/:id directly with the request ID.