> ## 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.

# Features

> Everything included in every plan, mapped to the Momentra tool or skill that delivers it.

Every plan includes the full feature set below. Each row maps a product feature
to the Momentra Events tool (or composed [skill](/mcp/workflows)) that delivers
it, so you can see exactly how it works.

## Included in every plan

| Feature | How it works | Backed by |
| - | - | - |
| Website monitoring | Crawl an organization's published calendar and keep its events available to your account | `index_org` + `org_status` ([Discover](/mcp/workflows)) |
| Event cleanup | Every scraped event is normalized into one consistent v1 schema (deduped, canonical links, resolved venues) | scraper pipeline → [Event shape](/concepts/event-shape) |
| Complete event details | Full normalized record: dates with timezone, venue, pricing/offers, categories, the three link fields | `fetch` → [Event shape](/concepts/event-shape) |
| Category matching | Rank events against your editorial brief using closed-vocabulary facets | `matching_events` + facets ([Curate](/concepts/brief-shape)) |
| Editorial standards | Encode your include/exclude policy as a brief that drives what surfaces | `update_brief` / `get_brief` ([Brief shape](/concepts/brief-shape)) |
| Calendar feeds & exports | Turn results into a feed, calendar, or structured JSON for downstream use | `search_business_events` / `fetch` output ([Plan](/mcp/workflows)) |
| Trust signals | Organization identity, contact, socials, and address carried on every org record | org record ([Organization shape](/concepts/organization-shape)) |
| Source evidence | Every event links back to its own detail page on the source site; responses carry the source domain | `website` field + `_source` ([Event shape](/concepts/event-shape)) |
| Calendar health check | Surface orgs that returned no events, and report data/crawl problems with auto-attached diagnostics | `org_status` (`indexStatus`) + `report_issue` |
| Find new organizations | Discover venues/orgs that fit your brief, then index them | `matching_orgs` + `index_org` ([Discover](/mcp/workflows)) |
| Approval queue | Accept or reject specific events/orgs to steer what matching surfaces | `accept_event` / `reject_event` / `accept_org` / `reject_org` ([Curate](/concepts/brief-shape)) |
| Multi-market administration | Scope organizations and briefs per account / market | per-account scope + brief |

<Note>
  "Skill" names (Discover, Curate, Plan, Pipeline) are documented workflows
  composed from the MCP tools — see [Workflows](/mcp/workflows). They don't add
  endpoints; they sequence the tools above.
</Note>

## Coming soon

These features are on the roadmap. The data foundations are in place; the
automation and reporting layers are being built.

<CardGroup cols={2}>
  <Card title="Automatic approval of qualifying events" icon="circle-check">
    Auto-admit events that clearly pass your brief (high similarity + all facet
    gates), so only borderline items need review. Builds on today's
    `evaluate_event` verdicts (`fit` / `weak` / `reject`) and the accept/reject
    curation queue.
  </Card>

  <Card title="Social media monitoring" icon="share-nodes">
    Watch organizations' social profiles for events they post off their
    calendar. Today Momentra records each org's social links on its record; the
    monitoring/extraction layer is planned.
  </Card>

  <Card title="Change & cancellation tracking" icon="clock-rotate-left">
    Detect and notify when a tracked event changes — a new time, a reschedule, a
    cancellation. Each event already carries an `eventStatus`
    (`EventScheduled` / `EventCancelled` / `EventRescheduled` / `EventPostponed`)
    and ticket status; the cross-crawl diffing and alerting is planned.
  </Card>

  <Card title="Quarterly coverage report" icon="chart-line">
    A periodic summary of indexed orgs, event volume, and coverage gaps per
    market. Planned on top of the existing per-org index status and event
    counts.
  </Card>

  <Card title="Scheduled delivery" icon="calendar-days">
    Hands-off recurring delivery (e.g. "every Monday, format new events for our
    CMS"). Today this runs as a composed [pipeline](/mcp/workflows) the agent
    repeats; first-class scheduling is planned.
  </Card>
</CardGroup>

<Note>
  Each "coming soon" item is marked honestly: the underlying data (event status,
  social links, index status, brief evaluation) already exists today — what's
  planned is the automation, monitoring, diffing, or reporting layer on top.
</Note>


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