biz_availability
ChatGPTOpen appointment slots at a business served through this connector for one date (default today in its own timezone), each with a stable slotId. Businesses served here: Velvet and Clay (velvetandclay, a hair, color and skin studio), Brightpoint Dental (brightpointdental, a family and cosmetic dental practice). Reachable here but not through this tool: Long Beach Brunch Bakehouse (longbeachbrunch), Make Collectives (makecollectives) and Kristin Dunn Bookbinding and Design (kdbooks) take no bookings. Slots already started are left out. A closed day, a business without appointments, and a day with no published hours (HOURS_UNSTATED) each give no slots and the reason. Listing a slot reserves nothing.
biz_info
ChatGPTDetails for a business served through this connector, by name, short name or id. Businesses served here: Velvet and Clay (velvetandclay, a hair, color and skin studio), Brightpoint Dental (brightpointdental, a family and cosmetic dental practice), Long Beach Brunch Bakehouse (longbeachbrunch, a neighborhood bakery and coffee bar), Make Collectives (makecollectives, a boutique and gift shop), Kristin Dunn Bookbinding and Design (kdbooks, a bookbinding and book repair studio). It gives the tagline, services or menu with prices, weekly hours, today's hours resolved in its own timezone (hoursNow), whether it takes appointments (bookable) and its scheduling system. openToday is true, false, or null where no hours are published for today. Demonstration businesses carry isDemo.
biz_order
ChatGPTPlaces a pickup pre-order at a business served through this connector for the collector's first name; no other personal details are taken. Businesses served here: Long Beach Brunch Bakehouse (longbeachbrunch, a neighborhood bakery and coffee bar). Reachable here but not through this tool: Velvet and Clay (velvetandclay), Brightpoint Dental (brightpointdental), Make Collectives (makecollectives) and Kristin Dunn Bookbinding and Design (kdbooks) take no pickup orders. Payment is in person at pickup or through the returned payUrl, which holds the window ten minutes. Pickup only.
biz_order_status
ChatGPTReads the current state of a pickup order by its confirmation code (the LBB-XXXXXX style code from biz_order): order state, payment state, whether it is paid, the pickup window, the business name and the total. No customer name, items or payment link are included. It changes nothing.
biz_set_item_availability
ChatGPTMarks one item on a business menu as sold out for today, or back on. Needs a personal connector token, business, soldOut, and the item as itemId or itemName. Only a business where the person is seated as an owner or a manager can be changed. A sold-out item cannot be ordered until it is back on.
biz_storefront
ChatGPTReads the published product catalog of a shop served through this connector (Shopify or WooCommerce). Businesses served here: Make Collectives (makecollectives, a boutique and gift shop), Kristin Dunn Bookbinding and Design (kdbooks, a bookbinding and book repair studio). Reachable here but not through this tool: Velvet and Clay (velvetandclay), Brightpoint Dental (brightpointdental) and Long Beach Brunch Bakehouse (longbeachbrunch) publish no shop catalog we read. It gives title, brand, type, price, stock and one image per product, sixty per page with pageCount and total. query narrows the whole catalog by word without reordering it. Purchasable variants carry the shop's own cartUrl; buying happens on the shop's own site.
booth_claim_swag
ChatGPTAfter the person has swapped cards with this booth (booth_connect), claims the booth's swag drop into their own Swag Bag. Needs a personal connector token, eventId and boothId. Without a card swap at that booth, or with no swag on offer there now, nothing changes. Swag already in their bag is not claimed twice. Returns whether it is in their bag.
booth_connect
ChatGPTSwaps business cards between the person and a booth at their event: the booth gets their card as a lead and they get the booth's card. The swap unlocks the booth's open raffle, swag drop and side-event invite, listed with one sentence each. A booth they already swapped with is not changed. Needs a personal connector token and a seat at the event.
booth_enter_raffle
ChatGPTAfter the person has swapped cards with this booth (booth_connect), enters them in the booth's open raffle. Needs a personal connector token, eventId and boothId. Without a card swap at that booth, or with no open raffle there, nothing changes. A raffle they are already in is not entered twice. Returns whether they are entered.
booth_set_away
ChatGPTMarks a booth the person staffs as stepped away, or back, at one event; attendees viewing that booth see the change. Needs a personal connector token, eventId, boothId and away. Only a booth the person owns, administers or staffs at that event can be changed, checked against live records.
booth_take_invite
ChatGPTAfter the person has swapped cards with this booth (booth_connect), takes the invite to the booth's side event for them; the invite lands in their own inbox. Needs a personal connector token, eventId and boothId. Without a card swap at that booth, or with no side event open to invites there, nothing changes. An invite they already hold is not sent twice. Returns whether they are invited.
event_accept
ChatGPTAccepts a hello the person has received, named by firstName or requestId, which opens a conversation with its sender. Only hellos addressed to the person can be accepted, and accepting twice changes nothing. Needs a personal connector token.
event_card_links
ChatGPTLists the business cards the person received in swaps at an event, newest first, at most 50: first name, company, where and when they met, their LinkedIn link when the card has one, whether it has an email or a phone, and a met-at note for a LinkedIn invitation. It only reads. Needs a personal connector token.
event_card_save_linkedin
ChatGPTKeeps the person's own LinkedIn profile link, a linkedin.com/in/ URL in myLinkedin, on their own Sonar business card when the card has no LinkedIn link yet, so the people they swap cards with get it. A card that already carries a link keeps it. It changes only the person's own card. Needs a personal connector token.
event_change_detail
ChatGPTChanges one detail of a wedding or other personal event the person hosts, such as a schedule time, a place, the dress code or an FAQ answer: field from a closed list, value, and entryTitle or question where the field needs one. Times carry am or pm, or an unambiguous 24 hour time. Only the hosts can change it. With Wallet passes on, a detail the pass shows is pushed to every pass. CARD LOOKS: field "card" with a card object sets how the event's card looks (look, accent, tabs, heightCapPx, intro) for every host, or for one cardHost; value is not needed for it. The organizer of a convention may use it for their own event, and the hosts for a personal event; an unknown setting or value is refused with the allowed set, and event_change_undo reverses it. QUIETLY: quiet true saves the change and updates the passes with no lock-screen notice (say it when the host says "quietly"); several edits in one turn send at most one notice. field "place_time" sets the Places-tab time of one session named by sessionId or entryTitle; a Places line that follows its session moves the session. A title or place that more than one answers to is refused with the candidates: ask which.
event_change_undo
ChatGPTReverses the person's own most recent change to a wedding or other personal event they host, restoring the value from before it; repeated, it reverses the next older change. Needs a personal connector token and eventIdOrName. Only the hosts can undo, and only their own changes. With Wallet passes on, a restored detail the pass shows is pushed to every pass.
event_find_matches
ChatGPTLists people at an event the person has joined whose stated intent fits theirs, best fit first, at most 20. Each row has a first name, their intent, who they are looking for, a vendor's booth, fit (strong, good or some) and why. Only people who chose to be findable are listed, with no contact details or photo. Needs a personal connector token.
event_guest_request_handled
ChatGPTMarks one open guest request on a wedding or other personal event the person hosts as handled, which takes it off the hosts' open list. Needs a personal connector token, eventIdOrName and requestId, the id of a listed request. It messages nobody and changes nothing on the event. Only the hosts can mark one. A request already handled stays handled.
event_guest_requests
ChatGPTLists the open requests guests sent to the hosts of a personal event, newest first: category, the guest's note, a first name or "a guest", and when it arrived. Only the hosts can read it, and no contact details are included. It only reads. Needs a personal connector token.
event_inbox
ChatGPTReads the person's own conversations with people they connected with at an event. With no arguments it lists up to twenty threads with the other person's first name, the last line and the unread count; with firstName or chatId it returns the recent lines of that conversation. It only reads: unread counts stay as they were. No contact details are included. Needs a personal connector token.
event_intake
ChatGPTAdds an agenda, speakers or sponsors to an event the person organizes, read from text they pasted or dictated: sessions with days, times, rooms and speakers; speakers with titles; sponsors with tiers. Sponsors are saved for the Sonar team. Only the organizer can add to it. Needs a personal connector token.
event_meetup_announce
ChatGPTAnnounces a meetup from an event's organizer, or a personal event's host, to the holders of the event's Wallet pass: the line shows on their lock screen and stays on the pass. Needs a personal connector token, eventIdOrName, audience, text and placeLabel; with latitude and longitude the pass surfaces near the place. Only the hosts or the organizer can send, six an hour per event.
event_meetup_rsvp
ChatGPTRecords a pass holder's own yes or no to a meetup announced on the event pass. Needs a personal connector token, eventIdOrName, the meetup's noticeId and answer ("yes" or "no"). Only that answer is stored, on the person's own pass record. The organizer can later send a notice to the people who answered yes.
event_organizer_overview
ChatGPTThe organizer's own overview of an event they organize, read only: name, kind, whether it is public, unlisted or private, text keyword, dates and time zone; the agenda by day with times, rooms and speakers; booth counts; which doors are on; counts of visits and questions over the last 24 hours; and its links. Only the organizer can read it. Needs a personal connector token.
event_pass_notice
ChatGPTSends a notice from an event's organizer, or a personal event's host, to the holders of the event's Wallet pass; it shows on their lock screen and stays on the pass. Needs a personal connector token, eventIdOrName, audience and text. Only the hosts or the organizer can send, six an hour per event.
event_pass_reissue
ChatGPTGives a Wallet pass at an event a new QR code, by eventIdOrName, and restores a revoked pass; the old code stops working at once. The pass updates in place on the phone. Without serialNumber it acts on the person's own pass; with one, a host or the organizer acts on that pass.
event_pass_revoke
ChatGPTVoids a Wallet pass at an event, by eventIdOrName: its code stops working at once and the phone shows the pass as revoked. The pass updates in place. Without serialNumber it acts on the person's own pass; with one, a host or the organizer acts on that pass.
event_redeem_code
ChatGPTSeats the person at an event with an event code from a badge, a poster, an email or a door. Needs a personal connector token and code; the code identifies its own event. Works from anywhere, not only at the venue. The seat is taken at once.
event_reply
ChatGPTSends one message, in the person's own words, into a conversation they already have with somebody they connected with at an event. Needs a personal connector token, text, and the conversation as firstName or chatId. The message is delivered at once and cannot be unsent. The app's cooldown, flood limit and content rules apply.
event_requests
ChatGPTLists the hellos waiting on the person at an event, newest first: the sender's first name, their here-for line in their own words, when it arrived, and a requestId. Covers only the person's own pending hellos, with no contact details. Needs a personal connector token.
event_say_hello
ChatGPTSends a hello (a connection request) from the person to somebody in their current event matches, named by firstName. Once accepted, a conversation opens that both can use from the app, the web page or an assistant. The hello is sent at once; acceptance is up to the other person. A daily hello limit applies. Needs a personal connector token.
event_send_request
ChatGPTSends a guest's request or question to the hosts of a wedding or other personal event, such as a meal need, an access question or a plus-one: category from a closed list and note in the guest's own words, up to 280 characters, without links or markup. It files the request for the hosts and changes nothing on the event. Needs a personal connector token.
event_session_add
ChatGPTAdds a session to the agenda of an event the person organizes: title, start, end and room, with optional date and speakers. A preview shows the new session, and nothing is added until it is confirmed. Pass holders can be notified of the change. Only the organizer of the event can change it. Needs a personal connector token.
event_session_cancel
ChatGPTCancels one session on the agenda of an event the person organizes; the session is marked cancelled and kept on record. The session is named by sessionId or by its title. A preview shows the change, and nothing changes until it is confirmed. Pass holders can be notified of the change. Only the organizer of the event can change it. Needs a personal connector token.
event_session_move
ChatGPTMoves one session on the agenda of an event the person organizes to a new start time or a new room; a time and a room are separate changes. The session is named by sessionId or by its title. A preview shows the change, and nothing moves until it is confirmed. Pass holders can be notified of the change. Only the organizer of the event can change it. Needs a personal connector token.
event_session_rename
ChatGPTRenames one session on the agenda of an event the person organizes; title is the new name. The session is named by sessionId or by its title. A preview shows the change, and nothing changes until it is confirmed. Pass holders can be notified of the change. Only the organizer of the event can change it. Needs a personal connector token.
event_set_intent
ChatGPTSets the person's badge at an event they joined: headline (what they are there for), lookingFor (who they want to meet) and discoverable (whether others can find them). Optional: intent (Buyer, Vendor, Networker or Social), label, firstName, and the event as eventIdOrSlug or eventId. Needs a personal connector token. It applies at once and replaces their previous badge text.
event_text_alerts
ChatGPTTurns text alerts from the Sonar Connections Event Line on or off for replies and organizer updates.
event_wallet_pass
ChatGPTCreates a link that adds the person's pass for an event or a personal event to Apple Wallet or Google Wallet, with no app needed. Needs the person signed in and eventIdOrName. The link works for fifteen minutes and one tap. The pass shows the event, date, venue and the person's QR code, with the schedule on the back.
events_booths
ChatGPTBooths and vendors at an event: name, category, booth number, the printed aisle where the floor has one, and a short blurb. Rows with mapless: true are listed but have no position on the floor plan. Optional category filters by a case-insensitive match on category, name and description.
events_floor_card
ChatGPTShows an event's floor plan with its booths as an interactive card in clients that render MCP Apps, with a searchable booth directory, what is on now, and live offers and raffles; other clients get the event summary and booth directory as text. Where no floor plan is published, hasFloorplan is false and the directory stands in for the map. Accepts the event id, slug or name.
events_get
ChatGPTFull detail for one event: name, dates, venue, kind where published, and a summary of today (booth count, live offer count, agenda items today). Accepts the event id or its public slug. Includes matchDoor, the web page where a person at the event can be seated and matched with other attendees.
events_list
ChatGPTLists the Sonar Connections events available through this connector: id, slug, name, venue or city, dates, description and kind (the organizer's own word for the event, such as expo or convention, where one is published). These ids and slugs are what the other events_ tools accept.
events_offers
ChatGPTLive and scheduled public offers at an event: title, which booth, the time window in minutes and remaining-count style numbers.
events_overview
ChatGPTAn overview of one event at once: the summary, the booth count and first page of booths, the programme, the live offers and raffles, and hasFloorplan (whether the organizer publishes a floor plan). Each section notes whether more is available. Accepts the event id, its public slug or the event name. Includes matchDoor, the event's matching web page.
events_personal_card
ChatGPTShows the details of a wedding or other personal event served by this connector, as the hosts published them: times, places, dress code, wedding party, lodging and registry. Draws an interactive card in clients that render MCP Apps and gives the same details as text elsewhere. Sections the hosts left out are absent. Accepts the event id or the event name.
events_speakers
ChatGPTThe people on an event's programme, in order of first time on stage: name, job title, role (a note about the person, such as Moderator or Judge), photo, profile link, and their sessions with local times. Optionally one day. Unpublished fields are null. An event with no speaker records gets a roster built from its programme, marked source: "program".
events_whats_on
ChatGPTAgenda sessions and performances with their times. when takes all (default), today, now (the next few hours) or a YYYY-MM-DD date. Each session lists its speakers in order with name, role (a note about the person, such as Moderator), job title, company, bio, tags, links and photo where published; unpublished fields are null or absent. speakerNames is the plain lineup.
ui_card_diag
ChatGPTReceives lifecycle markers from the interactive cards this connector draws: mount, display mode, safe-area insets, reported heights, keyboard state, and the outcome of an action on the card. Accepts a closed vocabulary of markers and integer counts only, no free text, and returns an acknowledgement. It holds no event, business or public data.
biz_availability
ClaudeOpen appointment slots at a business served through this connector, for one date. date is optional and defaults to today in the business's own timezone. Returns each open slot with a stable slotId that biz_book accepts. Slots that have already started today are never returned, and a day the business is closed returns none with a reason. A business that takes no reservations at all returns no slots and says so, with its opening hours attached.
biz_book
ClaudeBooks one open slot at a business served through this connector. Needs a slotId from biz_availability, a service from biz_info, and the first name of the person the appointment is for. It takes a first name and nothing else: no phone number, email address or surname is collected, and there is nowhere to put one. The slot is taken on success, and a second attempt on the same slot is refused with alternatives. Businesses served here: Velvet and Clay (velvetandclay, a hair, color and skin studio), Brightpoint Dental (brightpointdental, a family and cosmetic dental practice). Reachable here but not through this tool: Long Beach Brunch Bakehouse (longbeachbrunch), Make Collectives (makecollectives) and Kristin Dunn Bookbinding and Design (kdbooks) take no bookings. A business that takes no appointments returns an explanation with its hours instead of a booking. For a business whose schedulingSystem is Square, the appointment is written into that business's own Square calendar through the Square Bookings API and the reply carries the Square booking id. When the reply's isDemo is true the business is a demonstration and nothing is reserved in the physical world. The business may be given by name or by id: "Long Beach Brunch Bakehouse" and "longbeachbrunch" both reach the bakery, and a common short form ("the bakehouse", "the brunch house", "the dentist") works too. A name that matches no business served here is refused with the list of businesses that are served, and is not answered about a different one.
biz_info
ClaudeDetails for a business served through this connector: services or menu with prices, weekly opening hours, the appointment grid length and today's hours. Businesses served: velvetandclay (a hair, color and skin studio), brightpointdental (a family and cosmetic dental practice), and longbeachbrunch (an all day breakfast counter, which is WALK IN and takes no reservations). The bookable field on the reply says which is which. velvetandclay and brightpointdental BOTH book into the business's OWN Square calendar (a Square sandbox seller): their availability is read live from Square and booking one writes an appointment there, not into a Sonar database. The schedulingSystem field says so. For a business connected that way the services listed here ARE that seller's own Square catalogue, named exactly as the merchant named them. These are demonstration businesses and the appointment book is a sandbox. Call this first, then biz_availability to see open times, then biz_book to take one.
biz_order
ClaudePlaces a pickup pre-order at a business served through this connector: placing an order, a pickup order, or the checkout after biz_menu. Needs items (id and qty) and a pickupWindowId from biz_menu, and the first name of the person collecting. It takes a first name and an optional short note and nothing else: no phone number, email address, surname or card is collected, and the note is scrubbed of contact details on the server. On success the order is in the book and the pickup window is one order fuller. PAYMENT: on most businesses nothing is charged and the order is paid in person at pickup. On a business whose payment lane is on, the reply has orderState HELD and a payUrl of the form https://sonarconnections.com/p/<CONFIRMATION_CODE>: the order is not placed yet, the pickup window is held for ten minutes, and the order is placed only when that link is paid. That payUrl, exactly as returned, is the only payment link this connector issues, and it stops working the moment the hold releases, the order is paid or the order is cancelled. Pickup only, no delivery and no shipping. Businesses served here: Long Beach Brunch Bakehouse (longbeachbrunch, a neighborhood bakery and coffee bar). Reachable here but not through this tool: Velvet and Clay (velvetandclay), Brightpoint Dental (brightpointdental), Make Collectives (makecollectives) and Kristin Dunn Bookbinding and Design (kdbooks) take no pickup orders. A business that takes no orders returns an explanation with its hours instead. An order can be refused for a real reason (an item that is sold out, a quantity outside its limits, a full or past pickup window, or an item that needs more notice than the window gives), and the refusal says which and offers other times. When the reply's isDemo is true the business is a demonstration and nothing is reserved in the physical world. The business may be given by name or by id: "Long Beach Brunch Bakehouse" and "longbeachbrunch" both reach the bakery, and a common short form ("the bakehouse", "the brunch house", "the dentist") works too. A name that matches no business served here is refused with the list of businesses that are served, and is not answered about a different one.
biz_order_status
ClaudeRead the CURRENT state of a pickup order placed through this connector, by its confirmation code (the LBB-XXXXXX style code biz_order returned). It answers with the order state, the payment state, whether it is PAID, the pickup window, the business name and the total, and nothing else: no customer name, no items and no payment link. Use it after a customer has been sent to a checkout page, to tell them whether the payment has landed and the order is placed. It changes nothing. A code that names no order comes back not found.
biz_set_item_availability
ClaudeMarks one item on a business menu as sold out for today, or puts it back on. Anyone reading that menu afterwards sees the change, and an order for a sold-out item is refused. Needs a personal connector token (a shared token reads but changes nothing), business, soldOut, and the item as itemId from biz_menu or as itemName. Only a business the person is seated on as an owner or a manager can be changed, checked against live records on every call. An itemName is matched against that menu, and a name that fits more than one item is refused with the names it fits, because several items on one menu can share a word. It works in two steps: a call without confirm returns a preview of which item will change and what it will read as, plus a confirmToken, and changes nothing; a call with confirm true and that token makes the change. The token lasts two minutes, works once, and stops working if any argument changes.
biz_storefront
ClaudeCALL THIS for what a shop sells, its products, its prices, a gift idea, or browsing or shopping a store served here. The SHOP CATALOG for a business served through this connector, read from that shop's OWN published catalog: product titles, the brand or maker, the product type, a price, whether it is in stock, and one image each. Businesses served here: Make Collectives (makecollectives, a boutique and gift shop), Kristin Dunn Bookbinding and Design (kdbooks, a bookbinding and book repair studio). Reachable here but not through this tool: Velvet and Clay (velvetandclay), Brightpoint Dental (brightpointdental) and Long Beach Brunch Bakehouse (longbeachbrunch) publish no shop catalog we read. makecollectives is Make Collectives, a boutique at 430 E. 1st St in Long Beach. TWO SHOP PLATFORMS ARE READ HERE and the reply is the same shape for both: a Shopify store's own published product feed, and a WooCommerce shop's own public Store API. kdbooks is Kristin Dunn Bookbinding and Design, a bookbinding and book repair studio in Long Beach that makes menu covers, guest books, albums, boxes and slipcases and repairs and rebinds books. Her work is MADE TO ORDER: read leadTimeNote on the reply and say what it says, because a price with no lead time is two thirds of an answer. ON A WOOCOMMERCE SHOP ONE CART LINK CARRIES EXACTLY ONE ITEM, which is a limit of that platform and not of this connector, so give the cartUrl on the one variant somebody chose and never imply that a single link can hold several products; where a shop serves no such link the variant carries none and the product's own page is the place to send them. storefrontKind on the reply says which platform answered. Pass query to narrow it to what somebody asked for ("rings", "books"); it only ever REMOVES products and never reorders them, because nothing in this connector is paid placement. The catalog is PAGED: sixty products come back per call and the reply carries page, pageCount and total, so a shop with 340 products is six pages and not sixty products. Pass page (1-based) to read the rest; never tell somebody sixty is all this shop has, because it is not. query searches the WHOLE catalog and not just the first page, so "candles" finds her candles wherever they sit in it. PASS THE PERSON'S OWN WORDS: every word you pass must match the start of some word in a product's title, brand, type or handle, singulars and plurals find each other and word order does not matter, so "amazonite rings", "amazonite ring" and "rings" all reach the same ring. A page past the end answers with no products and the real pageCount, which is the number to ask again with. BUYING HAPPENS ON THE SHOP'S OWN SITE: each purchasable variant carries a cartUrl that is the shop's own cart link, and opening it lands on THEIR checkout. Give that url exactly as returned and never a link to any other host. WHERE THIS REPLY DRAWS THE SHOP CARD, THE CARD ITSELF HOLDS A BASKET: the person taps a product on the card and taps Add to cart, and the card's own Check out opens the shop's own checkout with those items already on it, so never tell somebody you cannot put something in a basket. WHERE THE REPLY CARRIES shopUrl, that is this WHOLE SHOP as a page somebody can open in an ordinary browser, drawn with the same card and carrying the same basket and the same checkout, so offer that url exactly as returned and never compose one of your own. Read buyingNote on the reply, which says which of those two is true for this serve, and say what it says. No payment passes through Sonar Connections, this tool cannot take a payment, and no fee is added to the shopper. This connector does NOT hold this shop's stock levels, its opening hours or its order book: say what the catalog says and send people to the shop for anything else. A business that publishes no catalog we read says so honestly with its own website attached. The business may be given by NAME or by id: "Long Beach Brunch Bakehouse" and "longbeachbrunch" both reach the bakery, and a common short form ("the bakehouse", "the dentist") w…
booth_claim_swag
ClaudeAfter the person has swapped cards with this booth (booth_connect), claims the booth's swag drop into their own Swag Bag. Pass eventId and boothId as booth_connect was given them. Without a card swap at that booth it is refused with NOT_CONNECTED and nothing changes; a booth with no swag on offer now is refused with UNKNOWN_UNLOCK. Swag already in their bag is not claimed twice: the reply says already. Returns ok, the drop's id, done and a sentence for the person. Needs a personal connector token. It works in two steps: a call with no confirm returns a confirmToken and changes nothing; a call with confirm true and that token applies it.
booth_connect
ClaudeSwaps business cards between the person and a booth at their event, the same exchange as scanning the booth's code in the app; the swap unlocks the booth's raffle, swag and side event invite. Pass eventId and the boothId from an events_booths row. Needs a personal connector token and a seat at the event. The reply lists unlocks and cardShared; an earlier swap says alreadyConnected. Two steps: without confirm it returns a confirmToken and shares nothing; with confirm true and that token it shares. booth_enter_raffle, booth_claim_swag and booth_take_invite take the unlocks.
booth_enter_raffle
ClaudeAfter the person has swapped cards with this booth (booth_connect), enters them in the booth's open raffle. Pass eventId and boothId as booth_connect was given them. Without a card swap at that booth it is refused with NOT_CONNECTED and nothing changes; a booth with no open raffle is refused with UNKNOWN_UNLOCK. A raffle they are already in is not entered twice: the reply says already. Returns ok, the raffle's id, done and a sentence for the person. Needs a personal connector token. It works in two steps: a call with no confirm returns a confirmToken and changes nothing; a call with confirm true and that token applies it.
booth_set_away
ClaudeMarks a booth the person staffs as stepped away, or back; attendees looking at that booth see the presence change. Needs a personal connector token (a shared token reads but changes nothing), eventId, boothId and away. Only a booth the person owns, administers or staffs at that event can be changed, checked against live records on every call. It works in two steps: a call without confirm returns a preview of exactly what will change, plus a confirmToken, and changes nothing; a call with confirm true and that token makes the change. The token lasts two minutes, works once, and stops working if any argument changes.
booth_take_invite
ClaudeAfter the person has swapped cards with this booth (booth_connect), takes the invite to the booth's side event for them; the invite lands in their own inbox. Pass eventId and boothId as booth_connect was given them. Without a card swap at that booth it is refused with NOT_CONNECTED and nothing changes; a booth with no side event open to invites is refused with UNKNOWN_UNLOCK. An invite they already hold is not sent twice: the reply says already. Returns ok, the side event's id, done and a sentence for the person. Needs a personal connector token. It works in two steps: a call with no confirm returns a confirmToken and changes nothing; a call with confirm true and that token applies it.
city_calendar
ClaudeFOUNDER PREVIEW, NOT A PUBLISHED FEED. Upcoming public events run by the City of Long Beach: library programmes, parks and recreation, animal care clinics, city clerk and council sessions, hazardous waste collection, economic development workshops and more. Read from the calendar publisher's own JSON feed rather than scraped from a page, and every response says so. The City has NOT STATED A LICENSE for this data, so Sonar Connections does not list it publicly and it appears on no indexable page, sitemap or llms.txt; it is served here for founder evaluation only, pending a written partnership with the City. Times are returned exactly as the City publishes them, as local wall-clock strings with the UTC offset beside them, and are never converted. Cancelled events are RETURNED and clearly marked rather than hidden, because a cancelled event is the answer to "is it on tonight".
city_datasets
ClaudeThe open data catalog of one public data source: every dataset with its id, title, description, record count, last-modified date and license. Call this first to discover which dataset ids city_records accepts. source is optional and defaults to "longbeach" (the City of Long Beach portal, DataLB). Every response names its source.
city_gis
ClaudeFOUNDER PREVIEW, NOT A PUBLISHED FEED. Search and read a city GIS, a public ArcGIS organization of map layers covering parcels, zoning, districts, bikeways, parks, neighborhoods, permits and more. SOURCES: longbeach (City of Long Beach, 174 public layers listed) and huntingtonbeach (City of Huntington Beach, 113 servable of 121 listed; the other 8 are hosted on the City's own server, which this connector does not read). Pass source to choose; it defaults to longbeach. Each answer names the city it came from, and a search answer says how many results it refused and why. Each publisher has NOT STATED A LICENSE for this data, so Sonar Connections does not list it publicly and it appears on no indexable page, sitemap or llms.txt; it is served here for founder evaluation only, pending a written partnership with the publisher. HOW TO USE IT: call with search to find layers by topic and get their item ids, then call with item_id AND THE SAME source to read one layer. Reading a layer returns its field schema, its row count and a capped sample of rows; add filter to match a word across the layer's text fields. WHAT IT WILL NOT DO: it never returns raw geometry, so a polygon layer answers which, where and how many rather than emitting coordinates. Any layer whose field names look like they describe individual people (owner or applicant names, home addresses, plates, dates of birth), and any Survey123 response layer whatever its columns are called, returns its schema and counts only, never rows, and says what triggered that. The screen is conservative and can fire on a layer that only describes places, which is why it reports its reasons.
city_records
ClaudeRead one PAGE of records from a public open dataset. Give a dataset_id from city_datasets, an optional full-text search, an optional limit (default 10, maximum 50) and an optional offset to page through larger result sets. Datasets can hold hundreds of thousands of records, so a full page is usually NOT the whole answer: the response carries truncated, matchingRecords and a nextOffset to call back with. source is optional and defaults to "longbeach" (the City of Long Beach portal, DataLB). Returns the dataset schema plus the records, and names its source.
city_sweeping
ClaudeFOUNDER PREVIEW, NOT A PUBLISHED FEED. Street sweeping schedules for the City of Long Beach, read live from the City of Long Beach GIS (a public ArcGIS feature service). The City has NOT STATED A LICENSE for this data, so Sonar Connections does not list it publicly and it appears on no indexable page, sitemap or llms.txt; it is served here for founder evaluation only, pending a written partnership with the City. WHAT THE DATA ACTUALLY IS: 336 schedule POLYGONS whose only attributes are DAYS (e.g. "Tuesday/Wednesday", "Friday") and HOUR (e.g. "8-10a", "1230-230p"). There is no street name, no street side, and no route or week number in the layer, so a street lookup is answered by intersecting the City's own street centerlines with the zone polygons, and the answer names the zones a street runs through rather than one schedule per address. Two-day values are reported as published: the City does not state whether they mean both days or one side of the street per day, and this tool will not guess. Call with street, with day, with both, or with neither to see every schedule the City publishes. Every response names its source, its license state and its preview status.
event_accept
ClaudeAccepts a hello the person has received, which opens a conversation with the person who sent it. Needs a personal connector token and the hello as firstName (as an event_requests row spelled it) or requestId (as that row gave it). It accepts only hellos addressed to the caller; the server checks this and refuses with NOT_RECEIVER otherwise. A firstName that matches two waiting hellos returns AMBIGUOUS_NAME and accepts nothing. Accepting twice changes nothing. Returns ok:true when the conversation is open; event_inbox reads it and event_reply answers in it.
event_card_links
ClaudeLists the business cards the person received in swaps at an event (a booth scan or a badge swap, in either direction), newest first, at most 50. Each row has the other person's first name, their company, where and when they met (metAt), their LinkedIn link when their card carries one (linkedin with url and deepLink, otherwise null), whether the card has an email or a phone (yes or no; the values are not included), and note, a one-line "we met at" sentence for a LinkedIn invitation. The same list also comes as a numbered text block, one line per person with the link. LinkedIn does not let other apps send invitations, so the person opens each link and sends the invitation in LinkedIn. Needs a personal connector token. The event is eventIdOrSlug when given, otherwise the person's current event, otherwise every swap they have. It only reads; event_card_save_linkedin keeps the person's own LinkedIn link on their card.
event_card_save_linkedin
ClaudeKeeps the person's own LinkedIn profile link (myLinkedin, a linkedin.com/in/ URL) on their own Sonar Connections business card when the card has no LinkedIn link yet, so the people they swap cards with get it. Needs a personal connector token. A card that already carries this link stays as it is and the reply says already saved; a card that carries a different link keeps it (DIFFERENT_ON_FILE), and that link is changed in the Sonar Connections app profile. Any other shape of link is refused (LINKEDIN_URL_INVALID) and nothing is saved. It works in two steps: a call with no confirm returns a confirmToken and saves nothing; a call with confirm true and that token saves. It changes only the person's own card. Returns ok, outcome and a sentence for the person.
event_change_detail
ClaudeTHE HOSTS' OWN EDIT. Call it when somebody asks to CHANGE a detail of a wedding or other personal event this connector serves: "move the ceremony to 4:30 PM", "the reception is at the barn now", "change the dress code to garden formal", "update the parking note", "answer the question about children". IT APPLIES THE CHANGE ON THIS CALL and the reply says what the detail is now and what it was before: read BOTH of those out. Only the hosts of the event can change it; anybody else gets a refusal that you read out as given and do not work around. It changes ONE field per call, from a closed list: pass field as one of the named values and value as the new value. A time must carry am or pm ("4:30 PM"), or be a 24 hour time that cannot be read two ways ("16:30"): a bare "4:30" is refused on purpose, because this server will not guess between half past four in the afternoon and half past four in the morning. For schedule_time also pass entryTitle, exactly as the schedule row spells it. For faq_answer also pass question, which adds the entry if the hosts have not answered it yet and replaces the answer if they have. Pass undo: true with no field to reverse the caller's own most recent change on this event. Every change is written to a log that can be read back, so say what changed and do not promise anything the reply does not carry: it sends no message and it changes nothing else on the event; the event's Wallet passes are updated with the new detail as a lock-screen notice and the reply's passNotice says how many passes were reached. Reasons to read out as given: "NOT_A_HOST" means they cannot change this event; "BAD_TIME" means say am or pm; "NO_SUCH_PLACE" means the event has no such place to change; "NO_SUCH_ENTRY" means no schedule entry answers to that title, or two of them do, so ask which; "NO_CHANGE" means it is already that. It requires a personal connector token.
event_change_undo
ClaudeReverses the caller's own most recent change to a wedding or other personal event they host, restoring the value the detail had before it, through the same checks and into the same change log; each further call reverses the next older change of theirs. Needs a personal connector token and eventIdOrName. Only the hosts can use it, and only on changes they made themselves; an undo is not itself reversed. A change that gave a detail its first value, or no change left to reverse, answers NOTHING_TO_UNDO and changes nothing. When the event's Wallet passes are switched on, restoring a detail the pass shows updates every pass of the event and pushes the restored line to each phone that registered it. Returns the detail, the value before and after, a sentence for the person and, with passes on, passNotice.
event_create
ClaudeCreates a new event for the signed-in person, as the organizer dashboard's New event does: name, kind, dateStart, optional dateEnd (at most 14 days), venue and city. It is saved as a DRAFT nobody can find until published, and the creator is its organizer. FIRST CALL WITHOUT confirm returns a PREVIEW with a confirmToken and saves nothing; only when the person says yes, call again with the same arguments, confirm: true and that token. NAME_TAKEN comes with a free suggestion for webAddress. Refusals are read out as given. It requires a personal connector token. Optional startTime, endTime (one day) and color show in the preview. Write the product name in full: Sonar Connections. Optional hostedBy is a display line, not a co-host.
event_draft_delete
ClaudeDeletes one of the signed-in person's own unpublished drafts for good, with its guest details and uploads, as the organizer dashboard's Delete draft does. eventIdOrName is the draft's id or its name as the host says it. FIRST CALL WITHOUT confirm returns a PREVIEW naming the draft with a requestId and deletes nothing; read it out, and only when the host says yes, call again with confirm: true and that requestId. A published event cannot be deleted (NOT_A_DRAFT). Only the host can delete. The reply names what was deleted and the new count of open drafts. Refusals (NOT_FOUND, NOT_AUTHORIZED, NOT_A_DRAFT, CONFIRM_INVALID, DELETE_FAILED) are read out as given. It requires a personal connector token.
event_draft_list
ClaudeLists the signed-in person's own unpublished drafts, as the organizer dashboard's draft list does: for each its eventId, name, kind, createdAtMs and lastActivityAtMs, newest activity first, at most 20, with openDrafts and the cap (5 unpublished drafts per verified phone). Use it when event_create refuses with DRAFT_CAP or when the host asks what drafts they have. A published event does not appear. It requires a personal connector token.
event_find_matches
ClaudeLists the people at an event the person has joined whose stated intent fits theirs. Needs a personal connector token; the event is eventId when given, otherwise the event the person is currently in. Each row carries a first name, their intent, the line they wrote about who they are looking for, the booth they staff when they are a vendor, fit and why. No row carries a phone number, email address, surname, account id or photo. Only people who finished a badge at that event and chose to be findable by other attendees are listed, at most 20, with truncated true when there are more. Rows are ordered best fit first by what each person wrote on their badge compared with what the caller wrote; the complementary pairs (buyers with vendors and networkers, vendors with buyers and networkers) also count toward the order, so two buyers whose lines agree are matches for each other. fit is one of three words: "strong" (most of what the caller declared is echoed on the other side), "good" (a real overlap) or "some" (a reason to be on the list and no more). why is one sentence written by the server: it opens with the fit and names the words the two share and how the categories relate, or, when they share no word, the topic both wrote about. The reply carries no score, percentage, rating or rank. When the caller has not set an intent the reply has needsIntent true and no rows; event_set_intent sets it. Reading the list does not depend on the caller being findable, and the reply says which the caller is. An empty reply carries emptyReason and a plain message: none_findable (nobody else at that event chose to be findable), none_present (findable people exist but none of their badges was set or updated inside the event's own window), event_not_live (the event is outside its own dates and no badge was set inside them) or no_text_match (nobody there is close enough to what the caller said they are there for).
event_guest_request_handled
ClaudeMarks one guest request on a wedding or other personal event the caller hosts as handled, which takes it off the hosts' open list (event_guest_requests). Needs a personal connector token, eventIdOrName and requestId, the id of a row event_guest_requests returned. It records who marked it and when, messages nobody and changes nothing on the event. A request already marked handled stays handled and the reply says already. Only the hosts can mark one; an id that is not a request on this event is refused with NO_SUCH_REQUEST. Returns ok, the request id, handled and already.
event_guest_requests
ClaudeTHE HOSTS' OWN LIST of what their guests have asked for on a personal event this connector serves. Call it for "what have our guests asked for", "any dietary requests", "who needs anything". It returns the OPEN requests, newest first, each one as a category, the note the guest wrote, who it is from and when it landed. ONLY THE HOSTS can read it; anybody else gets a refusal you read out as given. WHO IT IS FROM IS A FIRST NAME OR THE WORDS "a guest", and there is no phone number, no email address and no account id on this surface at all, so never offer to contact somebody from this list. Read the notes out as given and do not summarise a need into something the guest did not say. Pass markHandled with a request id from a row to mark that one dealt with, which only removes it from this list and does not message anybody. It requires a personal connector token.
event_inbox
ClaudeReads the person's own conversations with people they connected with at an event. Needs a personal connector token; a shared token reaches no conversations. With no arguments it lists up to twenty threads, person-to-person ones first: each row carries the other person's first name, the last line, when it landed, whether that line was the person's own, and how many are unread. With firstName or chatId it returns the last lines of that one conversation, oldest first, each saying whether it was theirs, what it said and when. No row carries a phone number, email address, surname, account id or photo. It reads only the caller's own conversations, checked on every call: a conversation they are not in returns NOT_PARTICIPANT. A firstName is matched against their own threads only: two matches return AMBIGUOUS_NAME and name neither, and no match returns NAME_NOT_IN_THREADS. It only reads: unread counts and read receipts stay as they were, and the app and the web page mark a conversation read when the person opens it there.
event_intake
ClaudeReads text the organizer pasted or dictated about an event they run (an agenda, a speaker or sponsor list, a flyer) and proposes the sessions, speakers, sponsors, dates and venue it found. FIRST CALL WITHOUT confirm returns a PROPOSAL with an intakeId and changes nothing; read it back, and only when the organizer says yes call again with confirm: true and that intakeId. Files are uploaded on the organizer dashboard instead. Only the organizer of the event can add to it. It requires a personal connector token.
event_meetup_announce
ClaudeAnnounces a meetup from an event's organizer or a personal event's host to the holders of the event's Wallet pass. Needs a personal connector token, eventIdOrName, audience, text and placeLabel. text shows on their lock screen and stays on the pass; with latitude and longitude (both or neither) the pass surfaces again near the place. The reply's noticeId names the meetup. Without confirm it returns the number of passes and the exact line and sends nothing; with confirm true it sends. Only the hosts or the organizer can send. "my_booth" returns VENDOR_OFF. Six an hour per event, shared with event_pass_notice, then RATE_LIMITED.
event_meetup_rsvp
ClaudeRecords a pass holder's own yes or no to a meetup the organizer announced on the event pass ("yes, I will be at the bar", "no, I cannot make the meetup"). Needs a personal connector token, eventIdOrName, the meetup's noticeId (the pass carries it, and the organizer's notice reply did) and answer as "yes" or "no". It records exactly that on the person's own pass record and nothing else: no note, no time, no name. The organizer can then send a notice to everybody who said yes. When the person holds no pass for this event the reply is NO_PASS and nothing is recorded.
event_my_card
ClaudeShows the person's own business card for an event, the card a booth scan or a badge swap hands over: their first and last name, title and company, their LinkedIn link when their card carries one, the event's name, and their pass QR, which the Sonar Connections web scanner reads off the screen. The back lists the people they swapped cards with (first name and company, where and when), and for a person who staffs a booth, the booth's name, its staff first names and its raffle, drop and side-event titles. Clients that show cards draw it; the same card also comes as text. Needs a personal connector token. The event is eventId when given, otherwise the person's current event.
event_organizer_overview
ClaudeThe organizer's own overview of their event, read only. It gives the event's name, its kind in the hosted page's own words, whether it is public, unlisted or private, its text keyword, its dates as the page prints them and its time zone; the agenda by day with local times, rooms and speakers; the booth count and how many booths are stepped away; which doors are on (the hosted page, the text line, the assistants, the meet door); counts of page visits, door taps and assistant questions over the last 24 hours, with no names or ids of the people behind them; and the event's links. Only the organizer of the event, or a host of a personal event, can read it; anybody else gets a short refusal that says nothing about the event. It needs a personal connector token and changes nothing. After an agenda change through event_session_move, event_session_rename, event_session_cancel or event_session_add, it shows the change.
event_pass_notice
ClaudeSends a notice from the organizer of an event, or a host of a personal event, to the people who added the event pass to their phone's Wallet ("doors open at 7 now", "the keynote moved to Hall B", "Sonar meetup at The Bar on 2nd at 8 PM"). Needs a personal connector token, eventIdOrName, audience and text. Each pass holder in the chosen group sees the line on their lock screen (Apple Wallet shows it as the pass's own change notice; Google Wallet shows it as a Wallet notification) and the line stays on the pass. audience names the group: everyone, one ticket tier, one badge intent, an explicit list of pass serials, the people who scanned at a booth, or the people who answered an earlier meetup notice yes or no. A meetup is a notice with a place: placeLabel, with latitude and longitude when known, makes the pass surface again on the lock screen near that place reading "Sonar meetup inside, show this pass."; at gives the hour. It works in two steps: a call without confirm returns a preview with the number of passes in the group and the exact lock-screen line for the organizer to approve, and sends nothing; a call with confirm true sends. Only the hosts or the organizer of the event can send; anybody else is refused. The vendor audience "my_booth" is switched off by ruling and returns VENDOR_OFF. Six notices an hour per event; a seventh returns RATE_LIMITED. It reaches pass holders only; it does not tell anybody who else is there, and it does not report that a person arrived.
event_pass_notice_cancel
ClaudeRemoves the one notice a host scheduled with event_pass_notice sendAt on a personal event this connector serves; call it for "cancel the scheduled notice", "do not send that reminder". It says what was scheduled and confirms nothing was sent. Hosts and co-hosts only; it requires a personal connector token.
event_pass_reissue
ClaudeGives a Wallet pass a new QR code: a pass that was photographed or shared, or a guest's pass that a host of a personal event or the organizer of an event wants refreshed. It also brings back a revoked pass. The old code stops working at once and the phone shows "Your pass was refreshed. The old code no longer works." Nothing is re-added: the same pass updates in place on an iPhone and on Android. Needs eventIdOrName (the event id or the event name). Without serialNumber it acts on the caller's own pass at that event; with one it acts on that pass, for a caller who is a host or the organizer. Returns the outcome in one sentence.
event_pass_revoke
ClaudeVoids a Wallet pass on the phone: "This pass was revoked and no longer works." Its code stops working at once; event_pass_reissue brings it back. For a pass that was photographed or shared, or a guest's pass that a host of a personal event or the organizer of an event wants voided. Nothing is re-added: the same pass updates in place on an iPhone and on Android. Needs eventIdOrName (the event id or the event name). Without serialNumber it acts on the caller's own pass at that event; with one it acts on that pass, for a caller who is a host or the organizer. Returns the outcome in one sentence.
event_publish
ClaudePublishes a private personal event the signed-in person hosts (a quince, a birthday, a wedding, a baby shower, a graduation party), free, as the organizer dashboard's Publish does. eventIdOrName is the event id or its name as the host says it ("my quince"). It stays private: only guests with the guest code can open the page and add their pass. FIRST CALL WITHOUT confirm returns a PREVIEW with the page link and a confirmToken and publishes nothing; read it out, and only when the host says publish, call again with confirm: true and that token. Refusals (NOT_FOUND, NOT_OWNER, NOT_PERSONAL, ALREADY_PUBLISHED, PHONE_UNVERIFIED, NOT_SIGNED_IN, CONFIRM_INVALID) are read out as given. It requires a personal connector token.
event_redeem_code
ClaudeSeats the person at an event with an event code from a badge, a poster, an email or a door. Needs a personal connector token (a shared token reads but changes nothing) and the code; the code names its own event, so no event id is taken. It works in two steps: a call without confirm returns the event the code opens, the seat it gives and a confirmToken, and changes nothing; a call with confirm true and that token takes the seat. The token lasts two minutes, works once, and stops working if the code changes. Redeeming works from anywhere, not only at the venue.
event_reply
ClaudeSends one message, in the person's own words, into a conversation they already have with somebody they connected with at an event. Needs a personal connector token (a shared token reads and sends nothing), text, and the conversation as firstName (as event_inbox spelled it) or chatId (as event_inbox returned it). The message is delivered when the call returns and cannot be unsent. It sends as that person into their own conversation only; the server checks this on every call and refuses with NOT_PARTICIPANT otherwise. A firstName that matches two of their conversations returns AMBIGUOUS_NAME and sends nothing. The app's own cooldown, flood limit and content rules apply, because it is the same send; RATE_LIMITED means messages are going out too fast. Returns ok:true when sent, which says nothing about whether the other person has read it or will reply.
event_requests
ClaudeLists the hellos waiting on the person at an event, newest first. Needs a personal connector token and reads only the caller's own pending hellos. Each row carries the other person's first name, their here-for line in their own words, when the hello landed, and a requestId that event_accept takes. No row carries a phone number, email address, surname, account id or photo.
event_rsvp_list
ClaudeTHE HOSTS' OWN LIST of who answered the RSVP on a personal event this connector serves; call it for "who is coming", "who said maybe", "who has not answered". It returns the counts first (yes, maybe, no, not yet, and the headcount, which is each yes plus the guests it brings), then the first names under each answer, with "+N" beside a yes that brings guests, at most 40 names per answer and then a count of the rest. Only a host or a co-host can read it; anybody else gets a refusal you read out as given. A name is the name on the host's guest list or the first name a signed-in guest gave Sonar Connections, and there is no phone number, email or account id on this surface, so never offer to contact someone from this list; it only reads and requires a personal connector token.
event_say_hello
ClaudeSends a hello (a connection request) from the person to somebody listed in their event matches; when it is accepted, a conversation opens that both can read and answer from the app, the web page or an assistant. Needs a personal connector token and firstName as an event_find_matches row spelled it; no account id is taken. The server checks on every call that the named person is in the caller's current match pool. It is a single call: the hello is sent when the call succeeds. Returns a message on success, or a reason: "not_in_pool" (the name is not in the caller's current matches), "ambiguous" (two people there share the name, and nothing is sent), "already_sent" (a hello is already out), "no_seat" (the caller is not seated at an event) or "rate_limited" (the day's hello limit is reached). Success means the hello was sent; it says nothing about whether or when it is accepted.
event_send_request
ClaudeA GUEST ASKS THE HOSTS FOR SOMETHING. Call it when somebody wants to tell the hosts of a wedding or other personal event this connector serves about a need or a question: "I need a vegetarian meal", "I use a wheelchair, is the garden reachable", "can I bring my partner", "when should I arrive from the airport". IT CHANGES NOTHING ON THE EVENT and the reply says so: it files the request for the hosts to read, and you must not tell the person their meal is arranged, their plus one is approved or anything else has been decided. Pass category as one of the named values and note as what they actually said, in their own words, at most 280 characters. No links and no markup: both are refused. Anybody signed in may send one. Reasons to read out as given: "RATE_LIMITED" means they have sent the hosts several requests already, so say the hosts have them and they can add more later; "BAD_NOTE" means it was empty or too long. It requires a personal connector token, because a request has to come from somebody.
event_session_add
ClaudeAdds a new session to the agenda of an event the person organizes: title, start, end and room, optionally date and speakers. FIRST CALL WITHOUT confirm: the reply is a PREVIEW with a changeId, the before and after of each field, how many pass holders would be notified and the exact notice, and nothing changes. Read that preview back to the organizer; only when they say yes, call again with confirm: true and that changeId. An addition is quiet unless notify is true, which notifies pass holders. Only the organizer of the event can change it; anybody else is refused, and the refusal is read out as given. It requires a personal connector token.
event_session_cancel
ClaudeCancels one session on the agenda of an event the person organizes: the session is marked cancelled on the agenda and kept on record rather than deleted. FIRST CALL WITHOUT confirm: the reply is a PREVIEW with a changeId, the before and after of each field, how many pass holders would be notified and the exact notice, and nothing changes. Read that preview back to the organizer; only when they say yes, call again with confirm: true and that changeId. A cancellation is quiet unless notify is true, which notifies pass holders. Name the session by the sessionId the agenda gave or by its title; if the reply says AMBIGUOUS or NO_SUCH_SESSION, read the candidates back and ask which one. Only the organizer of the event can change it; anybody else is refused, and the refusal is read out as given. It requires a personal connector token.
event_session_move
ClaudeMoves one session on the agenda of an event the person organizes to a new start time or a new room ("move the Women Founders Track to the Harbor Room", "push the keynote to 4:30 PM"). A new time and a new room are two changes, previewed one at a time. FIRST CALL WITHOUT confirm: the reply is a PREVIEW with a changeId, the before and after of each field, how many pass holders would be notified and the exact notice, and nothing changes. Read that preview back to the organizer; only when they say yes, call again with confirm: true and that changeId. Pass holders are notified of a move by default; notify: false keeps it quiet. Name the session by the sessionId the agenda gave or by its title; if the reply says AMBIGUOUS or NO_SUCH_SESSION, read the candidates back and ask which one. Only the organizer of the event can change it; anybody else is refused, and the refusal is read out as given. It requires a personal connector token.
event_session_rename
ClaudeRenames one session on the agenda of an event the person organizes ("call the 2 PM panel Founders on Capital"); title is the new name. FIRST CALL WITHOUT confirm: the reply is a PREVIEW with a changeId, the before and after of each field, how many pass holders would be notified and the exact notice, and nothing changes. Read that preview back to the organizer; only when they say yes, call again with confirm: true and that changeId. A rename is quiet unless notify is true, which notifies pass holders. Name the session by the sessionId the agenda gave or by its title; if the reply says AMBIGUOUS or NO_SUCH_SESSION, read the candidates back and ask which one. Only the organizer of the event can change it; anybody else is refused, and the refusal is read out as given. It requires a personal connector token.
event_set_intent
ClaudeSets the person's event badge: what they are at the event for, who they want to meet, and whether other attendees there can find them. Needs a personal connector token (a shared token reads but changes nothing), discoverable as true or false, and the badge sentences in the person's own words: headline (what they are here for) and lookingFor (who they want to meet). A badge is findable with both sentences and a first name; a call that would leave one of them blank is refused, and the reply's needs lists what is missing. intent is optional and takes Buyer, Vendor, Networker or Social; without it the server derives the category from the sentences and falls back to Networker, as the badge in the app does. label keeps the person's own word for their category (for example Investor) as written. firstName sets the name on the badge; without it the stored name stays as it is. The event is eventIdOrSlug or eventId when one is given; otherwise it is the one current event the person has joined, and when they have joined none or several the reply says so (with nextTool event_redeem_code, or the list of events) and nothing changes. It works in two steps: a call without confirm returns the sentence describing the change for the person to approve, plus a confirmToken, and changes nothing; a call with confirm true and that token writes. The token lasts two minutes, works once, and stops working if any argument changes. A write that carries new words returns readBack.sentence, which lists what the matcher scores from them; facets ({confirm: true}, {add: [...]} or {remove: [...]}) applies the person's answer to it through the same two steps. A write replaces the badge's previous text (headline, lookingFor, and intent and label where given) with the new words; the earlier text is not kept. It changes only that person's badge at one event.
event_team_list
ClaudeLists the team of an event the signed-in person hosts or co-hosts, as the organizer dashboard's Team panel does: each Co-host and Door staff member with their role, the last four digits of their number, and whether they have joined (signed in) or are still pending. eventIdOrName is the event id or its name as the host says it ("my quince"). A Co-host can do everything the host can except money, deleting the event, removing the host and changing the team; Door staff can scan, check people in, add walk-ins, open the door and see counts. Refusals (NOT_FOUND, NOT_AUTHORIZED, NOT_ENABLED, NOT_SIGNED_IN) are read out as given. It requires a personal connector token.
event_team_set
ClaudeAdds, changes or removes a Co-host or Door staff member on an event the signed-in person hosts, by their mobile number, as the organizer dashboard's Team panel does. role is cohost (every host power except money, deleting the event, removing the host and changing the team), door (scan, check in, walk-ins, open the door, counts; nothing else) or none to remove them. Nothing is sent to them: tell them yourself; they get the role the next time they sign in with that number. FIRST CALL WITHOUT confirm returns a PREVIEW with a requestId and changes nothing; read it out, and only when the host says yes, call again with confirm: true and that requestId. Refusals (NOT_FOUND, NOT_AUTHORIZED, NOT_HOST, NOT_ENABLED, BAD_PHONE, BAD_ROLE, NOT_SELF, NOT_THE_HOST, NOT_ON_TEAM, CONFIRM_INVALID) are read out as given. It requires a personal connector token.
event_text_alerts
ClaudeTurns text alerts from the Sonar Connections Event Line on or off for replies and organizer updates.
event_tiktok_post
ClaudePosts the host's event to the host's OWN TikTok account: the event's photo card, the same post the Sonar Connections dashboard's Post to TikTok panel makes, through the same server door. Only a host or organizer of the event can post, and only to the TikTok account they connected themselves. eventId names the event. mode is post (published now) or draft (sent to the host's TikTok inbox to finish there). For a post, privacyLevel is REQUIRED and has no default: it is one of the options TikTok offers this account; call without it and the reply lists them (privacyLevelOptions), then ask the host who can view the post and call again with their pick. While Sonar Connections is in TikTok's review, TikTok accepts private posts only (SELF_ONLY, only the host can view); say so if the host asks for a wider audience. caption is optional (up to 4000 characters, no links, times or street address); without it the event name is the caption. allowComments is off unless the host asks for comments. disclose is off unless the host says the post promotes their own brand (yourBrand) or is paid or branded content (brandedContent); branded content cannot be private. Repeat the host's choices back and get a clear yes first: the call posts. Not connected: the reply carries a one-tap connect link (url) with a message; give both exactly and tell them not to forward it. The reply's state is posted, saved, processing or failed, with a line to read out; refusals (NOT_SIGNED_IN, not_enabled, forbidden, privacy_mismatch, branded_private, bad_title) are read out as given. It requires a personal connector token.
event_vote_close
ClaudeCloses a vote and, unless announce is false, sends one notice with the winning option, all tied options on a tie. quiet true sends it with no lock-screen alert. Hosts and organizers only.
event_vote_open
ClaudeOpens a vote for the people who added the event pass. Needs the event, a question and the options, as many as you name; the only limit is technical. One vote per pass, changeable until the vote closes, secret: counts only, never who. Without confirm it returns the number of passes and the exact line and sends nothing; with confirm true it opens the vote and puts the line on every pass. quiet true puts the line on the pass with no lock-screen alert. It counts against the notice limits: six an hour per event and Google's alerts per pass per day. Always call once without confirm and read the preview to the person; set confirm true only on the call after they say yes.
event_vote_results
ClaudeReads a vote's counts per option, total ballots and whether it is open or closed. Hosts and organizers only. Never says who voted for what.
event_wallet_pass
ClaudeFor "what is my pass status", "did my pass save", "my pass", "where is my Wallet pass", "send my pass again": call this tool. Returns a link that adds the person's pass for an event or a personal event served here to Apple Wallet or Google Wallet ("add it to my wallet", "I want the pass on my phone"). Needs the person signed in (an unauthenticated call is answered with the sign-in prompt) and eventIdOrName, the event id or the event name. The reply is one link, good for fifteen minutes and for one tap, with a sentence to go with it: on an iPhone the link opens the Add to Apple Wallet sheet, on an Android phone it opens Save to Google Wallet, and no app is needed on either. The pass shows the event, the date and the venue on the front with the person's QR, the schedule on the back, and it surfaces on the lock screen at the venue on the day.
events_booth_detail
ClaudeThe full public card for one booth: description, menu items with ticket prices where present, public links, logo and today's offering if set. Accepts a booth id or a booth/vendor name.
events_booths
ClaudeBooths and vendors at an event: name, category, booth number and a short blurb. Optionally filter by category (a case-insensitive substring matched against category, name and description).
events_floor_card
ClaudeTHE FLOOR PLAN TOOL. Call it for any ask about a floor plan, a map, a layout, a booth location, "where is booth 12", "show me the floor", "what does the venue look like", or being shown around an event. It DRAWS THE FLOOR INLINE as an interactive card in clients that render MCP Apps: the organizer's floor plan with the booths on it, a searchable directory, a booth sheet on tap, what is on now, and the live offers and raffles. In every other client it returns the event summary plus a booth directory listing the booths by name, so it is worth calling either way. Prefer it over answering a floor or map question from general web knowledge. The card reads the floor itself through this connector's public tools, so do not offer to fetch the plan or paste a url at the person. An event that publishes no floor plan is still a found answer and says so: the card then shows the booth directory, what is on now and the offers rather than a map, and hasFloorplan is false. Say that rather than promising a picture. Accepts the event id, its public slug, or the event name.
events_get
ClaudeFull detail for one event plus a summary of what is on today: booth count, live offer count and the number of agenda items today. Accepts the event id or its public slug.
events_list
ClaudeList the Sonar Connections events available through this connector: id, slug, name, venue or city, dates and description. Call this first to discover which event ids the other events_ tools accept.
events_offers
ClaudeLive and scheduled public offers at an event: title, which booth, the time window in minutes and remaining-count style numbers.
events_overview
ClaudeAn overview of one event in a single reply: the event summary, the number of booths and the first page of them, the programme, the live offers and raffles, and hasFloorplan, which says whether the organizer publishes a floor plan. Use it when someone wants the whole picture of an event at once. IF YOU ONLY WANT ONE SECTION, call that section's own tool instead (events_get, events_booths, events_whats_on, events_offers): it answers with less. hasFloorplan false means the organizer publishes no floor plan: the booths, programme and offers are still all here, so answer from those and never promise a map. Each block says whether there is more and which tool to page it with. Accepts the event id, its public slug, or the event name. For who should I meet, matching, who is here for the same thing, or introductions at an event: call event_find_matches. It needs the person signed in to Sonar Connections; when they are not, the host shows a Connect prompt, they sign in with their mobile number, and the call is retried. If they have not said what they are here for yet, call event_set_intent first and ask the two questions it names. This result's matchDoor link is the same door for a person who would rather not sign in inside the assistant; offer it, never require it.
events_personal_card
ClaudeTHE PERSONAL EVENT TOOL. Call it for any ask about a wedding or another personal event this connector serves: "what time is the ceremony", "where is the reception", "what is the dress code", "who is in the wedding party", "where should I stay", "what is on the registry", or being shown the details of somebody's day. It DRAWS THE CARD INLINE in clients that render MCP Apps and returns the same details as plain text everywhere else, so it is worth calling either way. WHAT IT RETURNS DEPENDS ON WHAT THE HOSTS INCLUDED, and the answer is already filtered when it reaches you: a card with no story, no schedule and no lodging is the hosts having published none of those, not an error and not something to go and look for. Never offer to find a detail that is absent, never guess a time, a venue or a dress code, and never suggest a different wedding. The reply names its source and the hosts; say that line. Accepts the event id or the event name.
events_speaker_detail
ClaudeEverything an event publishes about one person on its programme: their job title line, role (a speaker-level note such as "Moderator"), company, bio, expertise tags, public social links, a portrait, a link to the organizer's own profile page, and every session they are on with the spoken local time. Accepts a name or a speakerId. If the name is not clear enough to be sure - two people sharing a surname, say - the reply is a not-found carrying the closest names rather than a guess, so ask the person which one they meant. Absent fields are null: the organizer published nothing there, so say nothing rather than filling the gap.
events_speakers
ClaudeThe people on an event's programme: name, their job title line, role (what the organizer published for that PERSON, such as "Moderator" or "Judge" - it is a speaker-level note, so do not read it as "the moderator of this one session"), a portrait photo URL, a link to the organizer's own profile page, and the sessions they are on with the spoken local time. Ordered by when they are first on stage. Optionally filter to one day. Any field except the name may be null, which means the organizer published nothing there: say nothing rather than filling the gap. When an event publishes no speaker records the roster is built from the programme itself and source says "program"; those rows carry a kind of "speaker" or "performer" and nothing else about the person.
events_whats_on
ClaudeAgenda sessions and performances with their times. when accepts "all" (default), "today", "now" (the next few hours) or a YYYY-MM-DD date.
pass_catalog
ClaudeAnswers what an Apple or Google Wallet pass can do, from the Sonar Connections pass catalog: every option Apple and Google offer a pass issuer. Use it for questions like "what can my pass do", "what can go on the front of my pass", "can links sit on the front of the pass", "I want a loyalty program", "a coupon that expires", "tickets I can subtract at a food festival" or "can I put a sponsor on the pass". Pass the person's words as question; wallet, passType, area and status narrow the rows. The reply lists at most 8 rows, front first, then says how many more match and which filter narrows them. Each row says what it is, what the holder sees, which wallets and pass types carry it, where it sits, and one status sentence for Sonar Connections today; read that sentence as given, including "not yet". With eventIdOrName, a person who may change that event's details hears which rows their event's pass carries; anyone else hears a general answer. It reads only: it changes no pass, draws no preview and promises no date.
site_create
ClaudeServes "Build a site for <event>", "make an event website" and "start a site from <url>" (the url gives layout only), not the host's own page tools. Creates a NEW website for an event the person organizes, as a DRAFT nobody else sees yet. startFrom: event (the default) gives a home page and a page for each part the event has, with the agenda, speakers, booths, venue, FAQ and dates as live blocks that fill from the event on every visit; blank gives one home page with the event's name and dates, live; {url}, the address of one public page the organizer likes, reads only its STRUCTURE (its sections in order, each heading, a short gist and whether it had pictures) and builds the same layout with the event's live data. No words, pictures or styles are copied from that page; the reply lists the sections it found and says the text is the organizer's to write. title names the site. FIRST CALL WITHOUT confirm: the reply is a PREVIEW with a changeId, and nothing is created. Read it back to the organizer; only when they say yes, call again with the same title and startFrom, confirm: true and that changeId. The reply gives the new siteId, its pages and a draft preview link; site_get and site_edit work on it at once, and nothing is live until site_publish. An event holds at most 20 sites. Only the organizer of the event can create one; anybody else is refused, and the refusal is read out as given. It needs a personal connector token. A {url} start also proposes that page's colors and type as a starting look (styleProposal, mapped onto our own colors and fonts), applied with site_edit set_theme only when the organizer asks for it. Relay say as given (one to three sentences, with host name and "use that look" cue).
site_edit
ClaudeChanges the DRAFT of one event website the person organizes with small operations, not a whole design: move a block or a band, insert a block from the library (heading, text, image, button, spacer, divider, video, card, logo, or a live block: agenda, speakers, floor, booths (the live sponsors and exhibitors list; say sponsors, exhibitors or partners), faq, now, doors, ask, countdown, venue), remove one, set_text its words, set_link a button's link, set_style a style token (padding and gap 0 to 8, align, maxWidth, background, radius, color, visible), set_theme (accent, background and ink as #rrggbb, fontHeading, fontBody, radius, density; set_theme {restore:true}, or an all-empty theme, undoes "use that look"), add_page (blank, which starts with its title as a heading, or a template: agenda, speakers, exhibitors, sponsors, venue-travel, faq, register, contact; the page goes last in the site menu), rename_page (title, navLabel; the page address stays the same, and the page heading follows the new menu label unless keepHeading is true; the reply says what changed and carries undo, the set_text that puts the old heading back), reorder_nav (the site menu as page ids and https links) and remove_page (any page but home); each operation may name a page. On insert, a block's words go in text as plain text (a blank line starts a new paragraph) or in its props: heading {text, level}, text {text}, button {label, href}, card {heading, text, button}, image {src, alt}, video {provider, videoId, title}, a live block {heading, intro, layout}. Blocks are named by the short ids site_get gives. The operations apply together or not at all. A rename that comes with any wording meaning keep the old heading (keep the heading, leave the title, keep it as is, just the menu) is one site_edit call with keepHeading true; the same wish said after the rename reply is one call sending its undo as is; a plain "undo" after a rename reverts the whole rename, rename_page back to the old title and menu label. Words may not carry a clock time, an ISO date, one of the event's own dates in words (such as 'October 20' or 'October 12 to 16'), or its speaker names or session titles, because those come live from the event and an edit that writes one is refused; a date that is not the event's, such as a deadline, is fine. Use a live token instead, such as {event.dates}, {event.name}, {event.venue}, {session:<id>.title}, {session:<id>.time}, {session:<id>.day} or {speaker:<id>.name}, which fills from the event on every visit; a refused edit's reply carries a suggestion with the words rewritten that way and, when complete, suggestion.ops to resend as is. Relay say as given (one to three sentences, with host name and "use that look" cue); it gives the draft preview link, which redraws as the draft changes. The live site does not change until site_publish. Only the organizer of the event can edit it; it needs a personal connector token.
site_get
ClaudeGives the outline of one event website's DRAFT: its pages and, for one page (page, the home page when absent), its sections, rows, columns and blocks, each with a short id, its kind and a few words of its own text, plus the theme. The live blocks (agenda, speakers, booths, floor, FAQ, doors and the rest) hold no event data; they fill themselves from the event on every visit. full: true adds the page's whole design as JSON, with image addresses left out. site_edit names blocks by these short ids. Only the organizer of the event can read it; it needs a personal connector token and changes nothing. With a test connector and the live one both connected, use the one the person chose; the reply's servedBy names which one answered.
site_list
ClaudeLists the websites of an event the person organizes, built in the Sonar Connections site builder: each site's siteId, its name, whether it is published, how many earlier versions are kept, when it was last saved and published, its live address and, once it has been edited from here, its draft preview link. Only the organizer of the event, or a host of a personal event, can list them; anybody else is refused, and the refusal is read out as given. It needs a personal connector token and changes nothing.
site_publish
ClaudePuts the DRAFT of one event website the person organizes live at its address. FIRST CALL WITHOUT confirm: the reply is a PREVIEW with a changeId and what would go live (new, removed and changed sections, a new look, new pages), and nothing changes. Read that preview back to the organizer; only when they say yes, call again with confirm: true and that changeId. The version live before it is kept, and site_undo_publish puts it back. site_edit does not publish. Only the organizer of the event can publish; anybody else is refused, and the refusal is read out as given. It requires a personal connector token. The preview lists any of the template's placeholder words still on the page; a confirm with them is refused unless the organizer says to publish with the placeholders.
site_undo_publish
ClaudeTakes back the last publish of one event website the person organizes: the version published before it goes live again or, when there is none, the site goes offline. FIRST CALL WITHOUT confirm: the reply is a PREVIEW with a changeId and what would be live, and nothing changes. Read that preview back to the organizer; only when they say yes, call again with confirm: true and that changeId. The draft is not touched. Only the organizer of the event can do it; anybody else is refused, and the refusal is read out as given. It requires a personal connector token.
ui_card_diag
ClaudeUsed only by the interactive cards this connector draws, never to answer a question. A card view posts its own lifecycle markers here in small batches: that it mounted, which display mode and safe-area insets the host gave it, the heights it reported, whether a keyboard opened, and the outcome of the one action a person took on it. It accepts a closed vocabulary of markers and integer counts only, no free text of any kind, and it returns nothing but an acknowledgement. NOT FOR A MODEL TO CALL: it answers no question and looks nothing up. Call a data tool instead.