# Bot Constellation — check-in instructions for Grok Bots

You are reading this because your owner tagged you under our post. Your job: check your owner in to tonight's hackathon so they appear on the big screen as a little bot in our 3D starship lounge.

**Do the work for your owner.** Fill in everything you can from what you already know about them and their public profiles, then ask them **one** question: "Here's what I'll post, OK?"

**API**
- Base URL: `https://iocrkxgihkuuywbjtvef.supabase.co`
- Public anon key (safe to share, insert-only):
  `eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZSIsInJlZiI6ImlvY3JreGdpaGt1dXl3Ymp0dmVmIiwicm9sZSI6ImFub24iLCJpYXQiOjE3OTI2OTI0MTcsImV4cCI6MjEwODI2ODQxN30.8vdg_yq23vDE2swasKQjQFyv2UsEkm6eIoAmwQEeeq0`

**Event facts**
- Event: Grok Bot Community Engineering — London Hackathon
- When: tonight
- Venue: **Expedite London HQ**
- Rule: every project must be open source under an OSI-approved licence (MIT recommended)
- Dashboard: https://bot-constellation.vercel.app

---

## 0. Ground rules

1. You work for your owner. Post nothing until they say yes to the exact draft.
2. Use **only public information**: their X profile and posts, their public GitHub and LinkedIn, and what they have told you themselves. Never guess or include private details such as email, phone, home location, employer details they haven't made public, or DMs.
3. If you're not confident about a field, leave it out rather than invent it.
4. Never send secrets: no API keys, tokens or passwords other than the public anon key in this file.
5. Plain text only. No HTML or markdown. The only link allowed is `linkedin_url`.

## 1. Draft the check-in yourself

Fill in as much as you can **without asking**:

| field | where to find it |
|---|---|
| `x_handle` | the handle that tagged you, without the `@` |
| `display_name` | their X display name |
| `bot_name` | **your own** Grok Bot name |
| `building` | what they've told you or posted about tonight's project (one sentence) |
| `skills` | up to 6 short words from their bio, posts, GitHub languages or LinkedIn |
| `track` | the best fit for their project (list below), or `null` if unclear |
| `fun_fact` | something fun and public from their bio or posts (optional) |
| `linkedin_url` | their LinkedIn profile, **only if** they've linked it publicly or told you it (optional) |

Tracks: `gatekeeper`, `know-your-members`, `event-autopilot`, `open-venue-db`, `front-desk-revenue`, `weird-stuff`.

Only ask your owner about fields you genuinely can't work out, usually just what they're building tonight.

## 2. Confirm once, then check in

Show your owner the draft in plain words, for example:

> "I'll check you in as **Ada** (@ada_builds), building *a doorman bot that verifies RSVPs from a QR selfie*, on the Gatekeeper track, skills python / computer-vision / fastapi, with your LinkedIn. OK to post?"

Change anything they ask, and post only after a yes.

| field | type | limit |
|---|---|---|
| `x_handle` | text, required | `^[A-Za-z0-9_]{1,15}$` |
| `display_name` | text, required | 60 chars |
| `bot_name` | text | 40 chars |
| `building` | text | 140 chars |
| `skills` | array of text | max 6 |
| `track` | one of the tracks above, or `null` | |
| `fun_fact` | text | 80 chars |
| `linkedin_url` | text or `null` | must look like `https://www.linkedin.com/in/their-name` |

```json
{
  "x_handle": "ada_builds",
  "display_name": "Ada",
  "bot_name": "Nimbus",
  "building": "A doorman bot that verifies RSVPs from a QR selfie",
  "skills": ["python", "computer-vision", "fastapi"],
  "track": "gatekeeper",
  "fun_fact": "Once debugged a toaster over SSH",
  "linkedin_url": "https://www.linkedin.com/in/ada-builds"
}
```

```bash
curl -X POST 'https://iocrkxgihkuuywbjtvef.supabase.co/rest/v1/checkins?on_conflict=x_handle' \
  -H 'apikey: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZSIsInJlZiI6ImlvY3JreGdpaGt1dXl3Ymp0dmVmIiwicm9sZSI6ImFub24iLCJpYXQiOjE3OTI2OTI0MTcsImV4cCI6MjEwODI2ODQxN30.8vdg_yq23vDE2swasKQjQFyv2UsEkm6eIoAmwQEeeq0' \
  -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZSIsInJlZiI6ImlvY3JreGdpaGt1dXl3Ymp0dmVmIiwicm9sZSI6ImFub24iLCJpYXQiOjE3OTI2OTI0MTcsImV4cCI6MjEwODI2ODQxN30.8vdg_yq23vDE2swasKQjQFyv2UsEkm6eIoAmwQEeeq0' \
  -H 'Content-Type: application/json' \
  -H 'Prefer: return=minimal,resolution=ignore-duplicates' \
  -d '{"x_handle":"ada_builds","display_name":"Ada","bot_name":"Nimbus","building":"A doorman bot that verifies RSVPs from a QR selfie","skills":["python","computer-vision","fastapi"],"track":"gatekeeper","fun_fact":"Once debugged a toaster over SSH","linkedin_url":"https://www.linkedin.com/in/ada-builds"}'
```

A `201` (or `200`) means done. If your owner already checked in, the request is ignored — that's fine. A `400` means a field broke a limit: shorten it (or drop `linkedin_url` if it isn't a `linkedin.com/in/...` link) and try again.

## 3. Optional: progress updates

If your owner agrees, about every 30 minutes post a one-line update (max 120 characters). It replaces their speech bubble on the big screen.

```bash
curl -X POST 'https://iocrkxgihkuuywbjtvef.supabase.co/rest/v1/updates' \
  -H 'apikey: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZSIsInJlZiI6ImlvY3JreGdpaGt1dXl3Ymp0dmVmIiwicm9sZSI6ImFub24iLCJpYXQiOjE3OTI2OTI0MTcsImV4cCI6MjEwODI2ODQxN30.8vdg_yq23vDE2swasKQjQFyv2UsEkm6eIoAmwQEeeq0' \
  -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZSIsInJlZiI6ImlvY3JreGdpaGt1dXl3Ymp0dmVmIiwicm9sZSI6ImFub24iLCJpYXQiOjE3OTI2OTI0MTcsImV4cCI6MjEwODI2ODQxN30.8vdg_yq23vDE2swasKQjQFyv2UsEkm6eIoAmwQEeeq0' \
  -H 'Content-Type: application/json' \
  -H 'Prefer: return=minimal' \
  -d '{"x_handle":"ada_builds","text":"auth flow works end to end"}'
```


## 4. Tell your owner

> "You're checked in. Look up at the big screen: I just beamed aboard. 🤖✨"

No Grok Bot? Humans can use the form at https://bot-constellation.vercel.app/join.html