Val Town Code SearchReturn to Val Town

1# Usage Dashboard
2
3A dashboard for monitoring API usage and inference calls.
4
5## Features
20  index.ts                 # Main entry point and routing
21  auth.ts                  # Authentication logic
22  /api/
23    index.ts              # API request handler
24    requests.ts           # API endpoints for requests data
25    inference-calls.ts    # API endpoints for inference calls
26    user-summary.ts       # API endpoints for user summary data
27  /views/
28    layout.ts             # Common layout template
54   - Links back to the associated request
55
56### API Endpoints
57
58- `/api/requests` - Get paginated requests
59- `/api/requests?usage_id=123` - Get a specific request
60- `/api/inference-calls` - Get paginated inference calls
61- `/api/inference-calls?usage_id=123` - Get inference calls for a specific request
62- `/api/user-summary` - Get user summary data
63
64## Debugging

24       user_id = ? 
25       AND timestamp > ?
26       AND our_api_token = 1
27    `,
28    [userId, new Date().getTime() - 24 * 60 * 60 * 1000],
113  branch_id,
114  model,
115  our_api_token,
116  num_images,
117}: {
120  branch_id: string;
121  model: string;
122  our_api_token: boolean;
123  num_images: number;
124}) {
132      branch_id,
133      model,
134      our_api_token,
135      num_images
136      ) VALUES (?, ?, ?, ?, ?, ?, ?, ?)
143      branch_id,
144      model,
145      our_api_token ? 1 : 0,
146      num_images,
147    ],

41);
42
43// token middleware for API requests
44app.all("/api/*", async (c, next) => {
45  const sessionCookie = getCookie(c, "_session");
46  if (!sessionCookie) {
52});
53
54app.route("/api", backend);
55
56app.get("/frontend/*", (c) => {

1import { basicAuthMiddleware } from "./auth.ts";
2import { handleApiRequest } from "./api/index.ts";
3import { getRequests } from "./api/requests.ts";
4import { getUserSummary } from "./api/user-summary.ts";
5import { getInferenceCalls } from "./api/inference-calls.ts";
6import { renderDashboard } from "./views/dashboard.ts";
7import { renderRequests } from "./views/requests.ts";
22  const path = url.pathname;
23
24  // Handle API requests
25  if (path.startsWith("/api/")) {
26    return handleApiRequest(req);
27  }
28

4
5/**
6 * Handle API requests
7 */
8export async function handleApiRequest(req: Request): Promise<Response> {
9  const url = new URL(req.url);
10  const path = url.pathname.replace("/api/", "");
11  
12  try {
13    // Route to the appropriate API handler
14    if (path === "requests") {
15      const usageId = url.searchParams.get("usage_id");
59    }
60  } catch (error) {
61    console.error("API error:", error);
62    return new Response(JSON.stringify({ error: error.message }), {
63      status: 500,

32        <ol>
33          <li>
34            Login with your Val Town API token (with projects:read, projects:write, user:read permissions)
35          </li>
36          <li>Select a project to work on</li>
70          </div>
71          <h3>Cost Tracking</h3>
72          <p>See estimated API usage costs for each interaction</p>
73        </div>
74      </section>
79        <ul>
80          <li>React frontend with TypeScript</li>
81          <li>Hono API server backend</li>
82          <li>Web Audio API for sound notifications</li>
83          <li>AI SDK for Claude integration</li>
84        </ul>
85        <p>
86          The application proxies requests to the Anthropic API and Val Town API, allowing Claude to view and edit your
87          project files directly.
88        </p>

13- Generate code in TypeScript or TSX
14- Add appropriate TypeScript types and interfaces for all data structures
15- Prefer official SDKs or libraries than writing API calls directly
16- Ask the user to supply API or library documentation if you are at all unsure about it
17- **Never bake in secrets into the code** - always use environment variables
18- Include comments explaining complex logic (avoid commenting obvious operations)
23### 1. HTTP Trigger
24
25- Create web APIs and endpoints
26- Handle HTTP requests and responses
27- Example structure:
173However, it's *extremely importing* to note that `parseProject` and other Standard Library utilities ONLY RUN ON THE SERVER.
174If you need access to this data on the client, run it in the server and pass it to the client by splicing it into the HTML page
175or by making an API request for it.
176
177## Val Town Platform Specifics
181- **AI Image:** To inline generate an AI image use: `<img src="https://maxm-imggenurl.web.val.run/the-description-of-your-image" />`
182- **Storage:** DO NOT use the Deno KV module for storage
183- **Browser APIs:** DO NOT use the `alert()`, `prompt()`, or `confirm()` methods
184- **Weather Data:** Use open-meteo for weather data (doesn't require API keys) unless otherwise specified
185- **View Source:** Add a view source link by importing & using `import.meta.url.replace("ems.sh", "val.town)"` (or passing this data to the client) and include `target="_top"` attribute
186- **Error Debugging:** Add `<script src="https://esm.town/v/std/catch"></script>` to HTML to capture client-side errors
187- **Error Handling:** Only use try...catch when there's a clear local resolution; Avoid catches that merely log or return 500s. Let errors bubble up with full context
188- **Environment Variables:** Use `Deno.env.get('keyname')` when you need to, but generally prefer APIs that don't require keys
189- **Imports:** Use `https://esm.sh` for npm and Deno dependencies to ensure compatibility on server and browser
190- **Storage Strategy:** Only use backend storage if explicitly required; prefer simple static client-side sites
224### Backend (Hono) Best Practices
225
226- Hono is the recommended API framework
227- Main entry point should be `backend/index.ts`
228- **Static asset serving:** Use the utility functions to read and serve project files:
248  });
249  ```
250- Create RESTful API routes for CRUD operations
251- Always include this snippet at the top-level Hono app to re-throwing errors to see full stack traces:
252  ```ts
285   - For files in the project, use `readFile` helpers
286
2875. **API Design:**
288   - `fetch` handler is the entry point for HTTP vals
289   - Run the Hono app with `export default app.fetch // This is the entry point for HTTP vals`

13- Generate code in TypeScript or TSX
14- Add appropriate TypeScript types and interfaces for all data structures
15- Prefer official SDKs or libraries than writing API calls directly
16- Ask the user to supply API or library documentation if you are at all unsure about it
17- **Never bake in secrets into the code** - always use environment variables
18- Include comments explaining complex logic (avoid commenting obvious operations)
23### 1. HTTP Trigger
24
25- Create web APIs and endpoints
26- Handle HTTP requests and responses
27- Example structure:
173However, it's *extremely importing* to note that `parseProject` and other Standard Library utilities ONLY RUN ON THE SERVER.
174If you need access to this data on the client, run it in the server and pass it to the client by splicing it into the HTML page
175or by making an API request for it.
176
177## Val Town Platform Specifics
181- **AI Image:** To inline generate an AI image use: `<img src="https://maxm-imggenurl.web.val.run/the-description-of-your-image" />`
182- **Storage:** DO NOT use the Deno KV module for storage
183- **Browser APIs:** DO NOT use the `alert()`, `prompt()`, or `confirm()` methods
184- **Weather Data:** Use open-meteo for weather data (doesn't require API keys) unless otherwise specified
185- **View Source:** Add a view source link by importing & using `import.meta.url.replace("ems.sh", "val.town)"` (or passing this data to the client) and include `target="_top"` attribute
186- **Error Debugging:** Add `<script src="https://esm.town/v/std/catch"></script>` to HTML to capture client-side errors
187- **Error Handling:** Only use try...catch when there's a clear local resolution; Avoid catches that merely log or return 500s. Let errors bubble up with full context
188- **Environment Variables:** Use `Deno.env.get('keyname')` when you need to, but generally prefer APIs that don't require keys
189- **Imports:** Use `https://esm.sh` for npm and Deno dependencies to ensure compatibility on server and browser
190- **Storage Strategy:** Only use backend storage if explicitly required; prefer simple static client-side sites
224### Backend (Hono) Best Practices
225
226- Hono is the recommended API framework
227- Main entry point should be `backend/index.ts`
228- **Static asset serving:** Use the utility functions to read and serve project files:
248  });
249  ```
250- Create RESTful API routes for CRUD operations
251- Always include this snippet at the top-level Hono app to re-throwing errors to see full stack traces:
252  ```ts
285   - For files in the project, use `readFile` helpers
286
2875. **API Design:**
288   - `fetch` handler is the entry point for HTTP vals
289   - Run the Hono app with `export default app.fetch // This is the entry point for HTTP vals`

23      // 3. Parse the actual HTML response structure
24      
25      console.log("WAEC API called with:", request);
26      
27      // Mock successful response for demonstration
93
94    } catch (error) {
95      console.error("WAEC scraping error:", error);
96      return {
97        success: false,

1// WAEC Results API routes
2
3import { Hono } from "https://esm.sh/hono@3.11.7";
8const scraperService = new WAECScraperService();
9
10// POST /api/results - Submit student information to get WAEC results
11results.post("/", async (c) => {
12  try {
31
32  } catch (error) {
33    console.error("Results API error:", error);
34    return c.json({
35      success: false,
39});
40
41// GET /api/results/analyze - Analyze WAEC website structure (for development)
42results.get("/analyze", async (c) => {
43  try {
102});
103
104// GET /api/results/test - Test endpoint to verify API is working
105results.get("/test", (c) => {
106  return c.json({
107    success: true,
108    message: "WAEC Results API is running",
109    endpoints: {
110      "POST /api/results": "Submit student information to get results",
111      "GET /api/results/test": "Test endpoint"
112    },
113    requiredFields: {