Conference Developer & AI Endpoints — General Pattern
This skill documents the available pattern for developer/AI-facing conference
data. Treat the sections as a surface catalog, not an all-or-nothing acceptance
checklist. For one endpoint, change and validate that endpoint plus its shared
public-data boundary; do not add MCP, CLI, documentation pages, agent skills, or
unrelated endpoints. Stripping private and internal fields is an invariant for
every public surface. Stop when the requested surface is usable and its privacy
contract is verified.
Surface catalog for a full conference endpoint suite
For a conference at route /{conf}, create the following:
1. Public Data Utility
Create src/data/{conf}-public-data.ts that:
- Imports the conference's source data (typically
src/pages/{conf}/source/schedule.json and the speaker extraction logic in src/data/{conf}-speakers.ts)
- Exports functions:
getPublicTalks(), getPublicSpeakers(), getScheduleByDay(), and a CONFERENCE_META object
- Strips all sensitive fields before returning data:
email / contact.email — speaker email addresses
notes — internal organizer notes
acceleventsSpeakerId — internal platform IDs
sessionId, invited — internal session metadata
cfpData — call for papers submission details and review status
- Returns clean types (
PublicSpeaker, PublicTalk) with only public-safe fields
2. API Routes
Create the following API routes in src/pages/api/{conf}/:
| File |
Endpoint |
Format |
Description |
llms-txt.ts |
/{conf}/llms.txt |
Plain text |
Basic conference info + schedule overview. Links to other endpoints. |
llms-full-txt.ts |
/{conf}/llms-full.txt |
Plain text |
Full details: every talk description, speaker bio, social links. |
sessions.ts |
/{conf}/sessions.json |
JSON |
All sessions (talks + workshops) with metadata. CORS enabled. |
speakers.ts |
/{conf}/speakers.json |
JSON |
All speakers with roles, companies, socials. CORS enabled. |
mcp.ts |
/{conf}/mcp |
JSON-RPC 2.0 |
MCP server with tools for querying conference data. |
All endpoints should:
- Set appropriate
Cache-Control headers (s-maxage=3600, stale-while-revalidate=86400)
- JSON endpoints must include CORS headers (
Access-Control-Allow-Origin: *) and handle OPTIONS preflight
- Never expose sensitive/internal fields
3. URL Rewrites
Add rewrites in next.config.ts under the existing rewrites section:
// {Conf} developer/AI endpoints
{
source: '/{conf}/llms.txt',
destination: '/api/{conf}/llms-txt',
},
{
source: '/{conf}/llms-full.txt',
destination: '/api/{conf}/llms-full-txt',
},
{
source: '/{conf}/sessions.json',
destination: '/api/{conf}/sessions',
},
{
source: '/{conf}/speakers.json',
destination: '/api/{conf}/speakers',
},
{
source: '/{conf}/mcp',
destination: '/api/{conf}/mcp',
},
4. MCP Server Implementation
The MCP endpoint should implement JSON-RPC 2.0 with the following tools:
get_conference_info — Returns conference metadata (dates, location, venue, links)
list_speakers — Returns speakers with optional search filter
list_talks — Returns talks with optional day, type, track, search filters
get_schedule — Returns schedule organized by day, with optional day filter
The endpoint should:
- Handle both GET (returns server info) and POST (JSON-RPC requests)
- Support batch requests
- Return proper JSON-RPC 2.0 error responses
- Follow the Streamable HTTP transport spec (2025-03-26)
5. Developer Documentation Page
Create src/pages/{conf}/developers.tsx with:
- Dark terminal theme matching the conference site design
- Sections: Endpoints, Quick Start (curl/JS/Python), CLI Tool, MCP Server, Agent Skills, Data Privacy
- Interactive endpoint cards linking to each endpoint
- Code blocks with copy functionality
- MCP config snippet for Claude Desktop / Cursor / Windsurf
- Use the AIE brand gold color (#FFE9A7) for headings and accent highlights
6. Agent Skill
Create .agents/skills/{conf}-developer-api/SKILL.md with:
- Endpoint inventory with URLs and descriptions
- Quick-start curl examples
- MCP integration instructions and config
- Data model schemas (JSON structure for talks and speakers)
- List of sensitive fields that are stripped
- Key file paths in the repository
7. CLI Tool
The generic CLI at cli/aie/ (published as aieng on npm) supports all conferences. When adding a new conference, add an entry to the CONFERENCES registry array in cli/aie/cli.mjs with:
slug — Conference route slug (e.g. europe)
aliases — Short aliases (e.g. ['eu', 'eur', 'london'])
name, route, dates, location, status
hasEndpoints — Set to true once endpoints are live
Usage: npx aieng {conf} [command] (e.g. npx aieng eu speakers)
Reference Implementation
The Europe conference (/europe) is the reference implementation. Use these files as templates:
- Data utility:
src/data/europe-public-data.ts
- API routes:
src/pages/api/europe/ (llms-txt.ts, llms-full-txt.ts, sessions.ts, speakers.ts, mcp.ts)
- URL rewrites:
next.config.ts (search for "Europe developer/AI endpoints")
- Inline section:
src/components/europe-2026/DeveloperEndpointsSection.jsx
- Agent skill:
.agents/skills/europe-developer-api/SKILL.md
- CLI tool:
cli/aie/ (generic multi-conference, published as aieng)
Conference-Specific Adaptations
Each conference has its own data source format. Key differences to account for:
- Europe: Source data in
src/pages/europe/source/schedule.json, speakers derived via src/data/europe-speakers.ts
- World's Fair: Historical data in
src/utils/speakers-sessions-details.json (hundreds of speakers from 2025), new 2026 data TBD
- Miami: Speaker data hardcoded in
src/components/aie-miami-2026/SpeakersSection.tsx and speakers.js
- Singapore: Data in
src/components/aie-singapore-2026/
When adapting, always check the conference's existing data sources and extraction patterns before building the public data utility.
Verification Checklist
After implementing endpoints for a new conference:
- Run
SKIP_ENV_VALIDATION=1 npx tsc --noEmit — must pass with zero errors
- Start dev server:
SKIP_ENV_VALIDATION=1 pnpm dev
- Verify each endpoint returns data:
curl http://localhost:3000/{conf}/llms.txt
- Verify JSON endpoints don't contain emails, notes, or internal IDs
- Test MCP endpoint with a
tools/list JSON-RPC call
- Test MCP endpoint with a
tools/call JSON-RPC call (e.g. list_speakers with search)
- Verify the developer page renders correctly in the browser
- Run build:
SKIP_ENV_VALIDATION=1 pnpm build
Notes
pnpm lint does not work on Next.js 16; use npx tsc --noEmit for type checking
- All endpoints use
s-maxage=3600, stale-while-revalidate=86400 caching
- The MCP implementation is hand-rolled JSON-RPC 2.0 (not using the official MCP SDK)
- The base domain for production URLs is
https://ai.engineer
1---2name: conference-developer-endpoints3description: Add or review developer- and AI-facing conference data endpoints such as llms.txt, sessions.json, speakers.json, or MCP routes for AI Engineer conference pages. Implement only the requested surface unless the user asks for the full endpoint suite; never expose private speaker, CFP, or organizer data.4metadata:5 source: https://skillmd.com/skills/swyxio/conference-developer-endpoints6---78# Conference Developer & AI Endpoints — General Pattern910This skill documents the available pattern for developer/AI-facing conference11data. Treat the sections as a surface catalog, not an all-or-nothing acceptance12checklist. For one endpoint, change and validate that endpoint plus its shared13public-data boundary; do not add MCP, CLI, documentation pages, agent skills, or14unrelated endpoints. Stripping private and internal fields is an invariant for15every public surface. Stop when the requested surface is usable and its privacy16contract is verified.1718## Surface catalog for a full conference endpoint suite1920For a conference at route `/{conf}`, create the following:2122### 1. Public Data Utility2324Create `src/data/{conf}-public-data.ts` that:25- Imports the conference's source data (typically `src/pages/{conf}/source/schedule.json` and the speaker extraction logic in `src/data/{conf}-speakers.ts`)26- Exports functions: `getPublicTalks()`, `getPublicSpeakers()`, `getScheduleByDay()`, and a `CONFERENCE_META` object27- **Strips all sensitive fields** before returning data:28 - `email` / `contact.email` — speaker email addresses29 - `notes` — internal organizer notes30 - `acceleventsSpeakerId` — internal platform IDs31 - `sessionId`, `invited` — internal session metadata32 - `cfpData` — call for papers submission details and review status33- Returns clean types (`PublicSpeaker`, `PublicTalk`) with only public-safe fields3435### 2. API Routes3637Create the following API routes in `src/pages/api/{conf}/`:3839| File | Endpoint | Format | Description |40|---|---|---|---|41| `llms-txt.ts` | `/{conf}/llms.txt` | Plain text | Basic conference info + schedule overview. Links to other endpoints. |42| `llms-full-txt.ts` | `/{conf}/llms-full.txt` | Plain text | Full details: every talk description, speaker bio, social links. |43| `sessions.ts` | `/{conf}/sessions.json` | JSON | All sessions (talks + workshops) with metadata. CORS enabled. |44| `speakers.ts` | `/{conf}/speakers.json` | JSON | All speakers with roles, companies, socials. CORS enabled. |45| `mcp.ts` | `/{conf}/mcp` | JSON-RPC 2.0 | MCP server with tools for querying conference data. |4647All endpoints should:48- Set appropriate `Cache-Control` headers (`s-maxage=3600, stale-while-revalidate=86400`)49- JSON endpoints must include CORS headers (`Access-Control-Allow-Origin: *`) and handle `OPTIONS` preflight50- Never expose sensitive/internal fields5152### 3. URL Rewrites5354Add rewrites in `next.config.ts` under the existing rewrites section:5556```ts57// {Conf} developer/AI endpoints58{59 source: '/{conf}/llms.txt',60 destination: '/api/{conf}/llms-txt',61},62{63 source: '/{conf}/llms-full.txt',64 destination: '/api/{conf}/llms-full-txt',65},66{67 source: '/{conf}/sessions.json',68 destination: '/api/{conf}/sessions',69},70{71 source: '/{conf}/speakers.json',72 destination: '/api/{conf}/speakers',73},74{75 source: '/{conf}/mcp',76 destination: '/api/{conf}/mcp',77},78```7980### 4. MCP Server Implementation8182The MCP endpoint should implement JSON-RPC 2.0 with the following tools:8384- `get_conference_info` — Returns conference metadata (dates, location, venue, links)85- `list_speakers` — Returns speakers with optional `search` filter86- `list_talks` — Returns talks with optional `day`, `type`, `track`, `search` filters87- `get_schedule` — Returns schedule organized by day, with optional `day` filter8889The endpoint should:90- Handle both GET (returns server info) and POST (JSON-RPC requests)91- Support batch requests92- Return proper JSON-RPC 2.0 error responses93- Follow the Streamable HTTP transport spec (2025-03-26)9495### 5. Developer Documentation Page9697Create `src/pages/{conf}/developers.tsx` with:98- Dark terminal theme matching the conference site design99- Sections: Endpoints, Quick Start (curl/JS/Python), CLI Tool, MCP Server, Agent Skills, Data Privacy100- Interactive endpoint cards linking to each endpoint101- Code blocks with copy functionality102- MCP config snippet for Claude Desktop / Cursor / Windsurf103- Use the AIE brand gold color (#FFE9A7) for headings and accent highlights104105### 6. Agent Skill106107Create `.agents/skills/{conf}-developer-api/SKILL.md` with:108- Endpoint inventory with URLs and descriptions109- Quick-start curl examples110- MCP integration instructions and config111- Data model schemas (JSON structure for talks and speakers)112- List of sensitive fields that are stripped113- Key file paths in the repository114115### 7. CLI Tool116117The generic CLI at `cli/aie/` (published as `aieng` on npm) supports all conferences. When adding a new conference, add an entry to the `CONFERENCES` registry array in `cli/aie/cli.mjs` with:118- `slug` — Conference route slug (e.g. `europe`)119- `aliases` — Short aliases (e.g. `['eu', 'eur', 'london']`)120- `name`, `route`, `dates`, `location`, `status`121- `hasEndpoints` — Set to `true` once endpoints are live122123Usage: `npx aieng {conf} [command]` (e.g. `npx aieng eu speakers`)124125## Reference Implementation126127The Europe conference (`/europe`) is the reference implementation. Use these files as templates:128129- Data utility: `src/data/europe-public-data.ts`130- API routes: `src/pages/api/europe/` (llms-txt.ts, llms-full-txt.ts, sessions.ts, speakers.ts, mcp.ts)131- URL rewrites: `next.config.ts` (search for "Europe developer/AI endpoints")132- Inline section: `src/components/europe-2026/DeveloperEndpointsSection.jsx`133- Agent skill: `.agents/skills/europe-developer-api/SKILL.md`134- CLI tool: `cli/aie/` (generic multi-conference, published as `aieng`)135136## Conference-Specific Adaptations137138Each conference has its own data source format. Key differences to account for:139140- **Europe**: Source data in `src/pages/europe/source/schedule.json`, speakers derived via `src/data/europe-speakers.ts`141- **World's Fair**: Historical data in `src/utils/speakers-sessions-details.json` (hundreds of speakers from 2025), new 2026 data TBD142- **Miami**: Speaker data hardcoded in `src/components/aie-miami-2026/SpeakersSection.tsx` and `speakers.js`143- **Singapore**: Data in `src/components/aie-singapore-2026/`144145When adapting, always check the conference's existing data sources and extraction patterns before building the public data utility.146147## Verification Checklist148149After implementing endpoints for a new conference:1501511. Run `SKIP_ENV_VALIDATION=1 npx tsc --noEmit` — must pass with zero errors1522. Start dev server: `SKIP_ENV_VALIDATION=1 pnpm dev`1533. Verify each endpoint returns data: `curl http://localhost:3000/{conf}/llms.txt`1544. Verify JSON endpoints don't contain emails, notes, or internal IDs1555. Test MCP endpoint with a `tools/list` JSON-RPC call1566. Test MCP endpoint with a `tools/call` JSON-RPC call (e.g. `list_speakers` with search)1577. Verify the developer page renders correctly in the browser1588. Run build: `SKIP_ENV_VALIDATION=1 pnpm build`159160## Notes161162- `pnpm lint` does not work on Next.js 16; use `npx tsc --noEmit` for type checking163- All endpoints use `s-maxage=3600, stale-while-revalidate=86400` caching164- The MCP implementation is hand-rolled JSON-RPC 2.0 (not using the official MCP SDK)165- The base domain for production URLs is `https://ai.engineer`