Skip to main content
Read-only.
When you need everyone from a set of accounts, a list of people, or one collab, at every event, in one call, use the ledger. Each row is one person at one event with their status, who brought them, who knows them and their city. Follows the heyBTW MCP rules.

When to use it

  • “Show me every event anyone from these 30 target accounts has been to.”
  • “Which of these people actually checked in, and where?”
  • “Give me the LA dinner roster as a CSV with partner source and city.”
  • “Who from Wavecrest has registered for anything this quarter?”

Parameters

Give at least one of domains, emails or channel_id.

Response

data[0] holds the page of rows and counts over the whole matching set. How to read status:
  • attended is a checked-in sign-up. registered is an RSVP, never attendance.
  • no_show appears only for a held event whose source recorded check-in. Where check-in was not recorded the sign-up reads registered with a partial_coverage gap.
  • An event not yet held reads registered with a gap.
  • seniority is advisory, from the title, and used by no rule or count.
  • A null partner_source does not mean no partner brought the person.
This sample is trimmed from a real call today on a ScaleUp.ai fixture collab.

Rules the agent must follow

  • Registered is not attended. Only attended (checked in) means the person came.
  • Null is unknown, never zero.
  • Nothing here is a ranking or engagement metric. Do not grade people from it.
  • Page with next_cursor on the same filters; do not fan out per-event get_event_details calls instead.
  • No row reads cancelled today, because no store records a cancelled registration.

Errors and gaps

  • invalid_parameter: none of domains, emails and channel_id was given, or a filter, limit or cursor is malformed.
  • partial_coverage gap: an event not yet held, or check-in not recorded. Not retryable. Disclose it.
  • entitlement_required: the plan lacks MCP read.
  • internal_error: retry once.