---
title: "Developer portal"
description: "API quickstart, keys and scopes, rate limits, versioning and deprecation policy, the MCP server for AI agents, and every developer resource in one place."
canonical: "https://agendaforge.app/developers"
last-updated: 2026-08-26
---
# Developer portal
> API quickstart, keys and scopes, rate limits, versioning and deprecation policy, the MCP server for AI agents, and every developer resource in one place.
Canonical page: https://agendaforge.app/developers
Last reviewed or updated: 2026-08-26
Content type: page

Title: AgendaForge Developer Portal | API, Webhooks, MCP Server
Last reviewed: August 26, 2026

Everything technical about AgendaForge in one place: the REST API and its OpenAPI 3.1 specification, API keys with named scopes, signed webhooks, rate limits, the MCP server for AI agents, and the versioning policy you can integrate against. Base URL: https://api.agendaforge.app/api/v1.

Quickstart: sign in to https://dash.agendaforge.app, open Settings > API Tokens, and generate a key. Keys begin with afk_live_, are shown once, and carry named scopes chosen at creation; the public_api scope (on by default) grants the REST API. Only an organization Owner or Admin can create or revoke keys. Validate with: curl https://api.agendaforge.app/api/v1/me -H "Authorization: Bearer afk_live_...". Every request and response is JSON; every error is { "error": { "code", "message" } } with a machine-readable code and a human-readable resolution hint. Anyone can sign up at https://dash.agendaforge.app/register; onboarding is white-glove rather than a self-serve trial.

Developer resources:
- API reference: https://agendaforge.app/docs/api (authentication, scopes, conventions, endpoints, trigger events, object reference)
- OpenAPI 3.1 specification: https://agendaforge.app/openapi.json (security schemes with named scopes, typed JSON error model, every endpoint)
- Webhooks (REST Hooks): 15 trigger events across contacts, sessions, sponsors, speakers, submissions, reviews, and events; HMAC-SHA256 signed deliveries with retries
- n8n guide: https://agendaforge.app/docs/n8n (community node n8n-nodes-agendaforge on npm, or the HTTP Request node)
- Zapier and Make.com: https://agendaforge.app/integrates-with/zapier (the same API powers both no-code integrations)
- Embeds and JSON feeds: published sessions, speakers, and agendas as embeddable widgets and public JSON feeds
- MCP server for AI agents: Streamable HTTP at https://mcp.agendaforge.app/mcp (read-only variant at /mcp/readonly); manifest at https://agendaforge.app/.well-known/mcp.json
- Public docs MCP and ask: the no-auth Streamable HTTP server at https://mcp.agendaforge.app/mcp/docs exposes search_docs and fetch_doc for public marketing and documentation content only; server card at https://agendaforge.app/.well-known/mcp/docs-server-card.json. For a natural-language answer from the same public content, GET https://agendaforge.app/ask?query=... or POST JSON with a query field to https://agendaforge.app/ask.
- Agent skills on GitHub: https://github.com/agendaforge/skills holds the official agendaforge-mcp and agendaforge-api skills plus an AGENTS.md and an Agent Plugins manifest; install with npx skills add agendaforge/skills.
- Content for AI agents: https://agendaforge.app/llms.txt, https://agendaforge.app/llms-full.txt, Markdown mirrors of every page (append .md), Accept: text/markdown negotiation, https://agendaforge.app/api/ai
- Security overview: https://agendaforge.app/security

Rate limits: 120 requests per minute per API key, 30 per minute per IP for unauthenticated requests. Every response carries RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, and RateLimit-Policy headers; exceeding a window returns 429 RATE_LIMITED with Retry-After.

Versioning and deprecation: versioned in the URL path (/api/v1); additive changes are never breaking; breaking changes ship only as a new version path; deprecations, if any, are announced in the changelog at least 180 days before removal and signaled with Deprecation and Sunset headers. Nothing is deprecated today.

MCP server: the AgendaForge MCP (Model Context Protocol) server lets AI assistants like Claude, ChatGPT, and Cursor work with events natively: read events, sessions, speakers, contacts, sponsors, and form submissions, and propose writes that a person approves. Connect over Streamable HTTP at https://mcp.agendaforge.app/mcp (read-only variant at /mcp/readonly). Authenticate by signing in with an AgendaForge account (OAuth 2.1; RFC 9728 discovery at /.well-known/oauth-protected-resource on the server origin, authorization server metadata at https://agendaforge.app/.well-known/oauth-authorization-server) or with an organization API key carrying the mcp:read or mcp:write scope. Server manifest: https://agendaforge.app/.well-known/mcp.json.

There is no official CLI yet; when it ships it will appear in the changelog first.

Questions, missing endpoints, or integration requests: hello@agendaforge.app.

---

AgendaForge is an AI-native event-management platform. Public machine-readable index: https://agendaforge.app/api/ai