Hotspotsystem for AI agents
HotspotSystem manages public Wi-Fi hotspots and billing for venues and businesses, tracking customers, access vouchers, and paid transactions across one or many physical locations. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Hotspotsystem.
Generate a Wi-Fi voucher
Generate a new access voucher for a guest at a specific location.
Check paid transactions
List recent paid transactions at a location to reconcile hotspot revenue.
List subscribers by location
List active subscribers at a venue to check current hotspot usage.
19 Hotspotsystem actions, graded by risk.
Every Hotspotsystem action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
3Look things up. Allowed by default.
- hotspotsystem.get_meGet Me
- hotspotsystem.get_locations_optionsGet Locations Options
- hotspotsystem.list_paid_transactionsList Paid Transactions
write
16Create and change things. Allow, or ask the user first.
- hotspotsystem.misc_pingMisc Ping
- hotspotsystem.vouchers_listList Vouchers
- hotspotsystem.customers_listList Customers
- hotspotsystem.locations_listList Locations
- hotspotsystem.subscribers_listList Subscribers
- hotspotsystem.generate_voucher_v1Generate Voucher (v1)
- hotspotsystem.transactions_list_macList MAC Transactions
- hotspotsystem.transactions_list_socialList Social Transactions
- hotspotsystem.transactions_list_voucherList Voucher Transactions
- hotspotsystem.vouchers_list_by_locationVouchers List by Location
- hotspotsystem.customers_list_by_locationList Customers by Location
- hotspotsystem.subscribers_list_by_locationList Subscribers by Location
- hotspotsystem.transactions_list_mac_by_locationList MAC Transactions by Location
- hotspotsystem.transactions_list_paid_by_locationList Paid Transactions by Location
- hotspotsystem.transactions_list_social_by_locationList Social Transactions by Location
- hotspotsystem.transactions_list_voucher_by_locationList Voucher Transactions by Location
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Hotspotsystem in three steps.
- 01Your users connect HotspotsystemThey add their Hotspotsystem api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “misc Ping” can wait for the user to approve.
- 03Any agent can actYour agent calls Hotspotsystem through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('hotspotsystem', { read: 'allow', write: 'ask', // misc_ping destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Hotspotsystem connects.
Users add their Hotspotsystem api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Hotspotsystem connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Hotspotsystem from any agent.
Hotspotsystem and Arc0, answered.
Can I use Hotspotsystem with Claude, ChatGPT or Cursor?
Yes. Connect Hotspotsystem to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Hotspotsystem actions you allow.
How do users connect Hotspotsystem?
Users add their Hotspotsystem api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Hotspotsystem actions can my agent take?
19 in total: 3 read, 16 write and 0 destructive, such as “misc Ping”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Hotspotsystem?
Yes. Allow read actions and deny writes in the Hotspotsystem policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Hotspotsystem too?
Yes. The same Hotspotsystem connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Hotspotsystem into your agent.
Your users connect Hotspotsystem once, under your brand. Your agent gets 19 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan