Conference Developer Endpoints

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}/:

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