It checks your building, starts your setup and hands you one link to finish. Afterwards it gives you your new buzzer number and the message to send your building.
Set up BuzzMeBro for my apartment so the buzzer rings all of our phones. M4B 1B3, unit 1502.
Your building is coveredI’ve filled in your details. Tap this link to confirm your phone and add a card.buzzmebro.comFinish your BuzzMeBro setup
How it works
1
Your assistant checks your building
It finds out whether we can give your building a local buzzer number, and what it costs.
2
It fills in your setup and sends you one link
Your postal code, unit and mobile are already in. You confirm your phone and add a card.
3
It hands you your number and the building message
Step-by-step instructions and a ready-written message for whoever runs your buzzer.
What to ask
Tell your assistant something like this
“Set up BuzzMeBro for my apartment so the buzzer rings all of our phones. My postal code is M4B 1B3 and I’m in unit 1502. Use buzzmebro.com/agents.”
Swap in your own postal code and unit.
It works with assistants that can use connectors, apps or tools (often called MCP), and with assistants that can browse the web for you.
For people
Two things only you can do
Everything else is already filled in. If your assistant can drive a web browser, it can open the link with you and you only step in for these two moments.
Type the code we text you
Your phone will open your front door, so we make sure it is really yours. We only send the code when you ask for it on our page.
Add a card on Stripe’s secure page
Your card goes to Stripe, never to us or to your assistant. First month free, then $9.99 a month for the whole apartment.
Your assistant cannot pay for you or open your door. Once you have finished, it can see your new number and the message for your building, so it can help you send it to building management, your landlord, the concierge, the superintendent or a building portal.
For assistants and developers
Connect over MCP or REST
Three operations, no sign-in, the same on both. Canada only for now.
MCP server
Streamable HTTP
Add it as a custom connector in your assistant’s settings. Stateless JSON over POST, no sign-in.
Server URL
https://buzzmebro.com/api/mcp
REST API
OpenAPI 3.1
JSON over HTTPS. Read progress with the status_token from create_setup, sent as Authorization: Bearer.
Checks whether BuzzMeBro can give this building a local buzzer number, and returns the price, the free-trial terms and how the service works. Call this first. Stores nothing and costs nothing.
2
create_setupCreates a setup
POST /api/agent/v1/setups
Creates a pre-filled BuzzMeBro setup for the person and returns setup_url, the one link they open to finish, plus a status_token you must keep to call get_setup_status. Only call it after check_building said available and the person has asked you to set it up. No text message is sent and nothing is charged by this call.
3
get_setup_statusRead-only
GET /api/agent/v1/setups/{setup_id}
Reads how far the person has got. When status is "ready" it returns their new BuzzMeBro number and swap_the_buzzer: the steps to get the building to point the buzzer at that number, and ready-to-send messages for building management, the landlord, the concierge, the superintendent or a building portal.
Quote only prices, availability and promises the tools return.
Requests are rate-limited per caller. A 429 means wait a few minutes.
The person’s link works for 3 days. Progress stays readable for 30 days.
What an assistant sends us is used only to fill in your signup and to show that assistant your progress. The link works for 3 days and the record is deleted after 30.
