Hotspotsystem MCP integration

Yes, and most reads exist in both forms. List Customers, List Subscribers, List Paid Transactions, List Vouchers, and the MAC and social transaction actions each have a by-location counterpart, so once Ayro has the ID from List Locations it can answer for a single site.

Almost everything else is read-only. Generate Voucher is the single write action in the toolkit, so Ayro can hand out access and report on customers, subscribers, and transactions, but it cannot create a location, edit a customer record, or reverse a paid session.

Generate Voucher draws on credits held against that specific location and needs the location to be active, so it fails rather than silently issuing an unusable code. Ayro validates the location with List Locations first and reports the shortfall instead of promising a code it cannot produce.

The customer and subscriber reads return names, emails, phone numbers, addresses, and registration dates, and subscriber records also carry the social network used to sign in, such as Facebook or Google. Both support field selection, so Ayro can request only the fields an answer needs rather than pulling the full profile.