momentra-events service through two channels. They share
the same global index and the same normalized data shapes, but they target
different kinds of workflow.
The practical dividing line is payment handling, not capability — a human or
an agent could use either:
- MCP fits human-in-the-loop workflows. A person drives an AI assistant and sets up prepaid Stripe credits once. That Stripe step may or may not be a barrier for a given integration.
- ZeroClick fits fully AI-native workflows. An autonomous agent pays per request at the pay URL — supporting the x402 agent-payment flow — with no human-managed billing account in the loop.
The two surfaces bill the same work through different accounting. Credits and
ZC units are kept aligned at a fixed rate so the free tiers are comparable —
see Credits & billing.
Same data on both
Whichever surface you call, you get the same normalized records:Event shape
Title, dates with timezone, venue, pricing, and three distinct link fields.
Organization shape
Stable identity, contact details, socials, and an upcoming event count.