Getting started

1. Mint a deploy token (once, ~2 minutes)

Open /token and sign in with your @illinois.edu account.
Create a token, label it (e.g. claude-code laptop), and copy it immediately — it is shown once. It looks like qk_….
Treat it like a password; revoke it from the same page any time.

2. Tell your AI agent about UniQuick

Set the token in your agent's environment as UNIQUICK_TOKEN, then point the agent at the API reference — it's written for agents:

https://uniquick.azurewebsites.net/llms.txt

That page documents the REST API (create site, deploy files, data, uploads) — everything an agent needs, no repo access required. Paste the URL into your agent's context or just include it in your prompt.

Using Claude Code? There's also an MCP server and a CLI in the project repository — access is granted on request (vishal@illinois.edu); the REST path above works for everyone without it.

3. Ask for an app

"Build a single-page RSVP sheet for my seminar. Read https://uniquick.azurewebsites.net/llms.txt for the UniQuick API and SDK, then create a site called seminar-rsvp and deploy it. My deploy token is in UNIQUICK_TOKEN."

Your app lands at /s/<your-netid>-seminar-rsvp/ — site names carry your netid automatically. Share the link with anyone at Illinois; they'll be signed in silently. Manage or delete your sites at /my.

What your app's JavaScript gets

Include <script src="/sdk.js"></script> and the page has:

quick.user — who's visiting (name, netid), signed in silently
quick.data — shared JSON storage (get/set/list/delete)
quick.files — file uploads that return a hosted URL
quick.ws — realtime events and presence ("who's here")
quick.ai — chat completions with a daily per-user allowance

Never put an API key in your site's code — your app is static files and anyone at Illinois can view source. Use quick.ai, which needs no key.

Ground rules

Apps are visible to anyone at Illinois with the link — not listed publicly, not private either.
Only you can change or delete your sites; data writes are attributed to real accounts.
Static pages only — no user code runs on the server. Uploads capped at 5MB/file, 40MB/deploy.
Not an approved store for FERPA-protected records or sensitive data.

Questions, repo access, or a site behaving oddly → vishal@illinois.edu.