> ## Documentation Index
> Fetch the complete documentation index at: https://docs.momentra.org/llms.txt
> Use this file to discover all available pages before exploring further.

# The two surfaces

> MCP server vs. ZeroClick REST API — same data, different transport, auth, and billing.

Momentra exposes one `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.

| | MCP server | ZeroClick API |
| - | - | - |
| **Workflow fit** | Human-in-the-loop agentic | Fully AI-native agentic |
| **Endpoint** | `POST https://mcp.momentra.org/mcp` | `/api/v1/*` via the ZeroClick storefront `https://agents.momentra.org` |
| **Protocol** | JSON-RPC 2.0 over Streamable HTTP / SSE | Conventional HTTP REST |
| **Shape of a call** | `tools/call` with a `name` + `arguments` | A path + method (e.g. `GET /api/v1/businesses/{id}/events`) |
| **Auth** | OAuth 2.1 + PKCE (CIMD), or static `Authorization: Bearer mck_…` | ZeroClick-signed request (`zc-signature`) with a registered agent |
| **Payment** | Prepaid **Stripe credits** (human-managed) | **Per-request** at the pay URL (x402) |
| **Billing unit** | Momentra **credits** | ZeroClick **units** |

<Note>
  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](/concepts/credits-and-billing).
</Note>

## Same data on both

Whichever surface you call, you get the same normalized records:

<CardGroup cols={2}>
  <Card title="Event shape" icon="calendar" href="/concepts/event-shape">
    Title, dates with timezone, venue, pricing, and three distinct link fields.
  </Card>

  <Card title="Organization shape" icon="building" href="/concepts/organization-shape">
    Stable identity, contact details, socials, and an upcoming event count.
  </Card>
</CardGroup>

## What's only on MCP

Brief-driven matching, curation, evaluation, and aggregator seeding are MCP-only
workflows. The ZeroClick API covers discovery, on-demand indexing, and event
pulls. If you need an editorial brief that surfaces events *for* you, use the
[MCP server](/mcp/overview).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.