--- title: "AgendaForge: event management software for conferences" description: "What AgendaForge does, who it is for, the product tour, what it replaces, pricing, onboarding, and the FAQ." canonical: "https://agendaforge.app/" last-updated: 2026-10-11 --- # AgendaForge: event management software for conferences > What AgendaForge does, who it is for, the product tour, what it replaces, pricing, onboarding, and the FAQ. Canonical page: https://agendaforge.app/ Last reviewed or updated: 2026-10-11 Content type: page Title: Event Management Software for Conferences | AgendaForge Description: Run the call for speakers, review, agenda, sponsors, tickets and check-in for conferences of 200 people and up in one workspace. $2,000 per event, published. ## From call for speakers to the front door AgendaForge is event management software for conferences of 200 people and up. It runs the call for speakers, review, agenda, sponsors and tickets in one workspace, on one set of contacts, with AI that drafts and waits for a person to approve. Core is $2,000 per event (https://agendaforge.app/pricing). Every plan starts with a 25-minute walkthrough on Google Meet, prices are published per event, and the workspace works from Claude and ChatGPT over MCP. Announcement: sell tickets by card or USDC, paid straight to you, and scan them at the door. ## One event, five views 1. Call for speakers: branded forms feed one list of responses, counted by stage. 2. Review: review rounds with rubrics, blind when you choose. Accept a talk and its session moves to Accepted. 3. Agenda: drag a session onto the grid. A speaker booked twice is flagged the moment it lands. 4. Tickets: a hosted ticket page with promo codes and a waitlist, paid into your own Stripe account. 5. Check-in: scan at the door from any laptop or phone browser, with an iPad kiosk in the lobby, or with the Check-In app for iPhone and Android (App Store and Google Play). The product views on the page show Forge Summit 2027, which is demo data. ## In use at Stable Summit (https://www.stablesummit.xyz) and Capital Summit (https://www.capitalsummit.io). Stable Summit takes its speaker applications on AgendaForge, and its speaker portal and forms run on their own domains. ## Connects to what your team already uses Stripe, Luma, Ticket Tailor, Google Sheets, Slack, ClickUp, Zapier and Make, plus a REST API and signed webhooks (https://agendaforge.app/developers). ## What kind of event do you run? Conferences and programs of 200 people and up: associations, academic conferences, developer conferences, corporate events, medical conferences and trade shows (https://agendaforge.app/for). ## Seven tools for one conference. One workspace instead. Before AgendaForge a conference typically runs on a form tool, a review spreadsheet, an agenda document, speaker email threads, a sponsor sheet, a ticketing tool and a printed door list: seven copies, kept in step by hand. In AgendaForge one event workspace holds the call for speakers and review, the agenda builder, the speaker portal, sponsors, tickets and check-in, and the AI Event Coordinator. One copy: every job reads the same contacts and sessions. ## What is inside: the whole program, one copy of the event The speaker who applied in March is the same contact on the agenda, in the portal and on the door list in October, and still the same contact when they sponsor next year. Nothing is exported, pasted or retyped in between. ### 01 Call for speakers and review: every proposal in one list, reviewed your way Speakers apply through a form on your theme, one question at a time, that already knows your tracks and formats. Every answer lands in one list, and reviewers score it against your rubric, blind if you choose. Try a real speaker form: https://forms.agendaforge.app/form-demo/call-for-speakers (what you submit is a real response). Stable Summit takes its speaker applications here. ### 02 Agenda builder: drag a talk in, the clash shows up on drop Rooms across the top, times down the side. Accepted talks wait in Unscheduled until you place them, a speaker booked twice is flagged the moment the card lands, and the agenda goes on your website as an embed that updates when you move a session. ### 03 Speaker portal: speakers sign in with a code, no password needed Each speaker sees their own sessions, the tasks you set and the files you asked for. Headshots and bios land on their contact record, and Design Studio turns them into speaker cards they can share. ### 04 Tickets and check-in: sell the ticket, scan it at the door A hosted ticket page with promo codes and a waitlist, scanning at every door from any laptop or phone browser, and an iPad kiosk for self check-in. Staff can also scan with the Check-In app for iPhone and Android, on the App Store and Google Play. How you get paid: - Card: charged on your own Stripe account. Stripe pays you out on your schedule; AgendaForge takes only its published fee. - USDC: sent from the buyer's wallet to yours on Base, through the Commerce Payments contract. - AgendaForge never holds your ticket money or delays your payouts. ### 05 AI Event Coordinator: drafted by AI, approved by your team The AI Event Coordinator answers questions from your event's own data, drafts emails and proposes changes to submissions, sessions and speakers. Proposed changes wait for a person on your team to approve or reject, and approved changes show up in the event's History. Claude, ChatGPT and Cursor can work on the event too, through the MCP server; their changes land in the same list and wait for a person (https://agendaforge.app/ai-agents). ## Also in the workspace Every plan includes all of this, nothing sold separately: sponsors (tiers, a branded intake form, sponsor contacts beside your speakers), a contact CRM (one record per person, across every event), email from the workspace (a template or a written note to any selection of contacts, every send logged), forms for the whole event (sponsor enquiries, applications and feedback on the same builder, with branching), Design Studio speaker cards, Add to Website (approved speakers published to your event site, plus agenda and speaker feeds), a participant hub (one sign in lists every event a person is part of; past ones stay read only), ⌘K search, Google Sheets sync, Slack and ClickUp, Zapier and Make with a REST API and signed webhooks on 16 event types, and activity history (who changed what, with the value before and after). Numbers: a 25-minute walkthrough on Google Meet sets your event up; 2 ways to get paid for tickets (card and USDC, both straight to you); 16 event types on signed webhooks; $2,000 per event on Core. Things you can check: listed in Claude's connector directory (https://claude.ai/directory/agendaforge); CSV export and a REST API; GDPR obligations met for every customer, with EU data residency as a paid add-on (https://agendaforge.app/gdpr); a person answers, the same day (hello@agendaforge.app). ## Pricing: priced per event, published in full - Core: $2,000 per event (founding rate $1,500). 500 registrations, then we talk; 50 speakers; 5 seats. - Pro: $4,000 per event (founding rate $3,000). Unlimited, white-label, your own domains. - 2 of 5 founding partners have been onboarded, so 3 places are still open at the founding rate. - Selling tickets? Card processing is charged by Stripe to your own account. The AgendaForge ticket fee is separate and published at https://agendaforge.app/pricing. Compare it with Eventbrite and Luma in the fee calculator: https://agendaforge.app/tools/ticketing-fee-calculator. ## How onboarding works: sign up, book the call, bring your program in 1. Sign up: create your account and name your organization. Then you tick what your events need, and the calendar comes next. 2. Book a 25-minute walkthrough: pick a time that suits you. The invite comes with a Google Meet link, and the account is approved, usually before the call. 3. Bring your program in: on the call the first event is set up together. Bring last year's speaker list as a CSV and it is imported together. Rather not have a call? Write a note about your event instead, and the account is activated by email. ## Questions before you sign up Something missing? Write to hello@agendaforge.app. A person answers. ### What happens after I sign up? You create your account, name your organization and tick what your events need. Then you pick a 25-minute walkthrough, and the invite arrives with a Google Meet link. We approve your account, usually before the call, and on the call we set up your first event together. Rather not have a call? Write us a note about your event instead, and we activate your account by email. [Getting started, step by step](/getting-started). ### Will I be talking to a salesperson? No. The walkthrough is 25 minutes with the people who build AgendaForge, spent setting up your first event and answering your questions. There is no quote to negotiate, because the prices are [published in full](/pricing). ### Can we try it before we buy? Yes. Start with a real speaker form, the one your speakers would see. Once your account is approved, usually before the walkthrough, the workspace is yours to explore with your own event. [Try a real speaker form now](https://forms.agendaforge.app/form-demo/call-for-speakers?theme=cobalt&mode=light) ### Who holds the ticket money? You do. Card payments are charged on your own Stripe account, and Stripe pays you out on your schedule; we take only our published fee. USDC goes from the buyer's wallet to yours. We never hold your ticket money or delay your payouts. The flip side: because the charge is yours, refunds and disputes come out of your Stripe balance. [How ticket fees work](/pricing#tickets). ### How is this different from Sessionboard or Cvent? Sessionboard is a content-operations platform for submissions, speakers, sessions and sponsors, and Cvent is an enterprise event-management platform covering the wider event lifecycle. AgendaForge runs the program, from the call for speakers to tickets and the door, in one workspace per event on one set of contacts, with its prices published. The comparisons go capability by capability: [vs Sessionboard](/vs/sessionboard) and [vs Cvent](/vs/cvent). See all questions: https://agendaforge.app/faq ## For AI agents: when to use AgendaForge and how to call it When to use: reach for AgendaForge when the job is the content and people side of a conference: a call for papers with review rounds, speaker coordination, a multi-track agenda with clash checks, sponsors, or registration. Best fit is a paid-ticket community, developer, or industry conference of 200 people and up. It also sells tickets (card into your own Stripe account, or USDC) and checks people in at the door, and it connects to Luma or Ticket Tailor if you keep selling there. It is not a meeting-notes app. Machine entry points: - Public content, no auth: MCP server https://mcp.agendaforge.app/mcp/docs (tools: search_docs, fetch_doc), JSON answers at https://agendaforge.app/ask, curated index at https://agendaforge.app/llms.txt, full text at https://agendaforge.app/llms-full.txt. Append .md to any page URL for Markdown, or send Accept: text/markdown. - Authenticated event operations: MCP server https://mcp.agendaforge.app/mcp (Streamable HTTP; reads execute, writes create proposals a human approves) and REST API v1 at https://api.agendaforge.app (OpenAPI 3.1 at https://agendaforge.app/openapi.json; cursor-paginated lists, batch create, async imports with 202 + pollable jobs, typed JSON errors on every 4xx and 5xx). - Authentication: OAuth 2.1 via the 401 Bearer challenge, or an organization API key with mcp:read / mcp:write scopes. Instructions: https://agendaforge.app/auth.md. Discovery: https://agendaforge.app/.well-known/mcp.json, https://agendaforge.app/.well-known/ai-catalog.json, https://agendaforge.app/.well-known/agent-skills/index.json. - Skills and agent configs: install with npx skills add agendaforge/skills; the public repo https://github.com/agendaforge/skills carries all five SKILL.md files, an AGENTS.md, and an Agent Plugins manifest (plugin.json). Webhooks and integration docs at https://agendaforge.app/docs/api. - Registry listings: official MCP registry entries app.agendaforge/agendaforge and app.agendaforge/docs (https://registry.modelcontextprotocol.io/v0/servers?search=app.agendaforge); Claude directory at https://claude.ai/directory/agendaforge; MCP.so at https://mcp.so/servers/agendaforge-50742c; Smithery at https://smithery.ai/servers/agendaforge/agendaforge and https://smithery.ai/servers/agendaforge/docs. REST endpoints at a glance (base https://api.agendaforge.app, full contract in https://agendaforge.app/openapi.json): - GET /api/v1/me verifies a key and names its organization and scopes. - GET /api/v1/contacts, /api/v1/sessions, /api/v1/sponsors: cursor-paginated lists scoped to one event. - POST /api/v1/contacts (single), /api/v1/contacts/batch (up to 100), /api/v1/imports/contacts (async, answers 202 with a job id polled at GET /api/v1/jobs/:id). - POST /api/v1/hooks and DELETE /api/v1/hooks/:id manage REST Hook webhooks across 16 trigger events; GET /api/v1/triggers/:event/sample returns a sample payload. - Authentication on every endpoint: Authorization: Bearer afk_live_... (or the same key as X-API-Key), created in Settings, API Tokens with the public_api scope. - Rate limit 120 requests per minute per key with RateLimit-* headers on every response; safe retries via the Idempotency-Key header; every 4xx and 5xx is the same typed JSON error object. --- AgendaForge is an AI-native event-management platform. Public machine-readable index: https://agendaforge.app/api/ai