Tianji Analytics
Query any read-only data from the Tianji monitoring and analytics platform.
Configuration
Three values are required (provided via skill config):
| Variable |
Description |
TIANJI_BASE_URL |
Tianji instance URL (e.g. https://tianji.example.com) |
TIANJI_API_KEY |
API key for authentication |
TIANJI_WORKSPACE_ID |
Default workspace ID |
Making API Requests
All endpoints are under {TIANJI_BASE_URL}/open and require a Bearer token:
curl -H "Authorization: Bearer {TIANJI_API_KEY}" \
"{TIANJI_BASE_URL}/open/workspace/{TIANJI_WORKSPACE_ID}/website/all"
Only GET requests are allowed. All responses are JSON.
Service Domains
Find the exact endpoint and parameters in api-endpoints.md.
For full parameter schemas, consult openapi-readonly.json.
| Domain |
Endpoints |
Typical Questions |
| Website |
13 |
Traffic stats, pageviews, geo distribution, Lighthouse scores |
| Monitor |
9 |
Uptime status, recent check data, monitor events |
| Survey |
8 |
Survey responses, result stats, AI categories |
| Telemetry |
7 |
Custom event counts, telemetry pageviews, metrics |
| Billing |
7 |
Usage quotas, subscription tier, credit balance |
| Feed |
6 |
Feed channels, event streams, feed states |
| Application |
5 |
App store reviews, app info, event stats |
| AI/AIGateway |
5 |
Gateway logs, model pricing, quota alerts |
| Worker |
3 |
Worker list, worker details, revisions |
| Page |
2 |
Status pages |
| Workspace |
2 |
Members, service counts |
| Global |
1 |
Platform configuration |
| AuditLog |
1 |
Audit trail |
Workflow
- Identify the service domain from the user's question
- Read api-endpoints.md to find the endpoint
- Construct the GET request with required path/query parameters
- Parse the JSON response and summarize for the user
Common Scenarios
Website traffic overview
GET /open/workspace/{workspaceId}/website/all
Pick the target website ID, then:
GET /open/workspace/{workspaceId}/website/{websiteId}/stats?startAt={timestamp}&endAt={timestamp}
Monitor health check
GET /open/workspace/{workspaceId}/monitor/all
Pick the target monitor ID, then:
GET /open/workspace/{workspaceId}/monitor/{monitorId}/get
GET /open/workspace/{workspaceId}/monitor/{monitorId}/status
Survey results analysis
GET /open/workspace/{workspaceId}/survey/all
Pick the target survey ID, then:
GET /open/workspace/{workspaceId}/survey/{surveyId}/result/list?startAt={timestamp}&endAt={timestamp}&limit=50
GET /open/workspace/{workspaceId}/survey/{surveyId}/stats?startAt={timestamp}&endAt={timestamp}
Feed event inspection
GET /open/workspace/{workspaceId}/feed/channels
Pick the channel ID, then:
GET /open/workspace/{workspaceId}/feed/{channelId}/fetchEventsByCursor?limit=20
Sensitive Data Handling
Some GET endpoints may return fields containing platform-stored secrets (e.g. modelApiKey,
customModelBaseUrl in AI Gateway responses). Additionally, endpoints like workspace members,
audit logs, and billing may contain PII or internal details.
Rules:
- NEVER display
modelApiKey, apiKey, secret, token, password, or credential fields to the user
- Redact or omit these fields when summarizing API responses
- When querying workspace members or audit logs, only surface non-sensitive metadata (names, roles, timestamps) unless the user explicitly requests full detail
Notes
- Timestamps use milliseconds since epoch (e.g.
1704067200000 for 2024-01-01)
- Pagination: some endpoints use
cursor parameter; check the response for nextCursor
- The
type parameter in website metrics accepts: url, language, referrer, title, browser, os, device, country, event
1---2name: tianji3description: Query website analytics, monitor uptime, survey results, telemetry data, feed events, application stats, and more from the Tianji platform via its read-only OpenAPI (69 GET endpoints across 14 service domains). Use when the user asks about website traffic, pageviews, monitor status, survey feedback, telemetry events, feed channels, billing usage, or any Tianji platform data.4---5
6# Tianji Analytics
7
8Query any read-only data from the Tianji monitoring and analytics platform.
9
10## Configuration
11
12Three values are required (provided via skill config):
13
14| Variable | Description |
15|----------|-------------|
16| `TIANJI_BASE_URL` | Tianji instance URL (e.g. `https://tianji.example.com`) |
17| `TIANJI_API_KEY` | API key for authentication |
18| `TIANJI_WORKSPACE_ID` | Default workspace ID |
19
20## Making API Requests
21
22All endpoints are under `{TIANJI_BASE_URL}/open` and require a Bearer token:
23
24```bash
25curl -H "Authorization: Bearer {TIANJI_API_KEY}" \
26 "{TIANJI_BASE_URL}/open/workspace/{TIANJI_WORKSPACE_ID}/website/all"
27```
28
29Only GET requests are allowed. All responses are JSON.
30
31## Service Domains
32
33Find the exact endpoint and parameters in [api-endpoints.md](references/api-endpoints.md).
34For full parameter schemas, consult [openapi-readonly.json](references/openapi-readonly.json).
35
36| Domain | Endpoints | Typical Questions |
37|--------|-----------|-------------------|
38| **Website** | 13 | Traffic stats, pageviews, geo distribution, Lighthouse scores |
39| **Monitor** | 9 | Uptime status, recent check data, monitor events |
40| **Survey** | 8 | Survey responses, result stats, AI categories |
41| **Telemetry** | 7 | Custom event counts, telemetry pageviews, metrics |
42| **Billing** | 7 | Usage quotas, subscription tier, credit balance |
43| **Feed** | 6 | Feed channels, event streams, feed states |
44| **Application** | 5 | App store reviews, app info, event stats |
45| **AI/AIGateway** | 5 | Gateway logs, model pricing, quota alerts |
46| **Worker** | 3 | Worker list, worker details, revisions |
47| **Page** | 2 | Status pages |
48| **Workspace** | 2 | Members, service counts |
49| **Global** | 1 | Platform configuration |
50| **AuditLog** | 1 | Audit trail |
51
52## Workflow
53
541. Identify the service domain from the user's question
552. Read [api-endpoints.md](references/api-endpoints.md) to find the endpoint
563. Construct the GET request with required path/query parameters
574. Parse the JSON response and summarize for the user
58
59## Common Scenarios
60
61### Website traffic overview
62
63```
64GET /open/workspace/{workspaceId}/website/all
65```
66Pick the target website ID, then:
67```
68GET /open/workspace/{workspaceId}/website/{websiteId}/stats?startAt={timestamp}&endAt={timestamp}
69```
70
71### Monitor health check
72
73```
74GET /open/workspace/{workspaceId}/monitor/all
75```
76Pick the target monitor ID, then:
77```
78GET /open/workspace/{workspaceId}/monitor/{monitorId}/get
79GET /open/workspace/{workspaceId}/monitor/{monitorId}/status
80```
81
82### Survey results analysis
83
84```
85GET /open/workspace/{workspaceId}/survey/all
86```
87Pick the target survey ID, then:
88```
89GET /open/workspace/{workspaceId}/survey/{surveyId}/result/list?startAt={timestamp}&endAt={timestamp}&limit=50
90GET /open/workspace/{workspaceId}/survey/{surveyId}/stats?startAt={timestamp}&endAt={timestamp}
91```
92
93### Feed event inspection
94
95```
96GET /open/workspace/{workspaceId}/feed/channels
97```
98Pick the channel ID, then:
99```
100GET /open/workspace/{workspaceId}/feed/{channelId}/fetchEventsByCursor?limit=20
101```
102
103## Sensitive Data Handling
104
105Some GET endpoints may return fields containing platform-stored secrets (e.g. `modelApiKey`,
106`customModelBaseUrl` in AI Gateway responses). Additionally, endpoints like workspace members,
107audit logs, and billing may contain PII or internal details.
108
109**Rules:**
110- NEVER display `modelApiKey`, `apiKey`, `secret`, `token`, `password`, or `credential` fields to the user
111- Redact or omit these fields when summarizing API responses
112- When querying workspace members or audit logs, only surface non-sensitive metadata (names, roles, timestamps) unless the user explicitly requests full detail
113
114## Notes
115
116- Timestamps use milliseconds since epoch (e.g. `1704067200000` for 2024-01-01)
117- Pagination: some endpoints use `cursor` parameter; check the response for `nextCursor`
118- The `type` parameter in website metrics accepts: `url`, `language`, `referrer`, `title`, `browser`, `os`, `device`, `country`, `event`
modbender