Skip to main content
Momentra finds and organizes local public events — concerts, markets, talks, classes, meetings and more — and makes them available to AI agents and assistants. You point it at the organizations and venues you care about, and it reads their published calendars, normalizes every event into one schema, and lets an agent search, match, and plan against them. From there, an agent can turn the results into finished work: draft this weekend’s newsletter, generate an event feed, build a destination guide, assemble a month-long calendar, or pull recommendations for a specific area — all from fresh event data across calendars, venues, and publishers, with no scraping to build or maintain yourself. The same underlying momentra-events service is exposed through two surfaces. Pick the one that fits how your agent is built.

MCP server

A hosted Model Context Protocol server for ChatGPT, Claude, and any MCP-compatible client. OAuth 2.1 / CIMD, billed with prepaid credits.

ZeroClick API

A conventional HTTP REST API under /api/v1/*, fronted by the ZeroClick storefront. Pay-per-request, signed-request auth.

​
Which one should I use?

The two surfaces are shaped for different workflows. Technically a human or an agent can use either — the real dividing line is how payment is handled.

MCP — human-in-the-loop

Built for human-in-the-loop agentic workflows: a person drives an AI assistant (ChatGPT, Claude) that calls the tools. Connect over OAuth with no key to paste, and pay with prepaid Stripe credits. The Stripe step is a one-time setup a human handles.

ZeroClick — AI-native

Built for fully AI-native agentic workflows: an autonomous agent pays per request at the ZeroClick pay URL, with no human-managed billing account in the loop. Supports the x402 agent-payment flow, so an agent can settle programmatically.
The split is about payment handling, not capability. MCP requires Stripe payment handling, which may or may not be a barrier for a given integration; ZeroClick’s per-request model (x402) removes the need for a managed billing account. Pick the one whose payment model fits your workflow.
Both surfaces read the same global index and return the same normalized event and organization shapes. They differ in transport, auth, and how they bill — see Surfaces for the side-by-side.

​
What Momentra does

1

Index an organization

Give Momentra an organization’s website. It crawls the published calendar and extracts every event into the v1 schema.
2

Search and read

Search across the organizations in your scope and open the full event or organization document.
3

Match against a brief (MCP)

Describe what you’re looking for as an editorial brief and let Momentra surface the events and organizations that fit it.
Coverage of any organization depends on what it publishes on its own website. Momentra reads the published calendar and records external ticketing or aggregator links without following them further.

​
Who makes Momentra

Momentra is built by Peter Newton. If you’re working on local events, agentic data access, or just want to compare notes, he’s happy to talk — reach out any time via DM Peter in the nav. Conversations welcome, whether you’re building on Momentra or just curious.