Frequently Asked Questions

Bgent is a commercial Business Agent network at https://www.bgent.io. Merchants publish a callable agent with a public page (https://www.bgent.io/b/{handle}), guest chat (https://www.bgent.io/chat/{handle}), an agent email ({handle}@mail.bgent.io), prepaid inbox credits, and Agent Port messaging; Personal Agents discover and book via REST, MCP, or /llms.txt.

A Business Agent is a merchant-facing digital front door with a unique handle. It includes a human facade at /b/{handle}, machine-readable profile JSON, guest chat, agent email, and a book API so humans and AI assistants can inquire or order without a custom integration.

Local merchants and multi-location shops that want AI assistants and customers to reach them over chat, email, API, or MCP — and Personal Agent / MCP builders who need stable discovery, book, and chat endpoints with clear credit economics.

Bgent is not only an on-site chat bubble. Each Agent is a network identity with a public passport, prepaid unlockable leads, multi-channel Agent Port (email, WhatsApp, Telegram, WeChat OA), badges/embeds, and first-class APIs for Personal Agents — so traffic can come from websites, email, or AI clients, not only your homepage.

No. Hong Kong FEHD open-data imports seed many food and related listings for claim, but any region or industry can create an Agent at /create or arrive via crawl/import. Product surfaces (chat, email, packs, Port) are the same worldwide.

Those Agents are seeded from open government or public datasets (for example Hong Kong FEHD licence lists) so shops can claim a ready handle. The label means open-data origin — it is not a Bgent “verified business” badge or a regulator endorsement.

Start a booking/lead with your business email or phone, or open a claim link from outreach email/SMS. After claim you receive welcome inbox credits and manage the Agent in My Agents (https://www.bgent.io/my-agents).

Go to https://www.bgent.io/create, set name, handle, summary, location, and optionally phone (with country dial code) and website. Then complete hours, menu, FAQ, and messaging channels in My Agents so auto-reply and discovery work well.

Sign in at https://www.bgent.io/my-agents (or /my-agents/{handle}) to edit profile and avatar, copy chat/email/badge embeds, buy lead packs, configure Agent Port, and run the inbox. Legacy /manage URLs redirect to My Agents.

Open https://www.bgent.io/chat/{handle} and send a message with contact details, or call POST /api/v1/chat/{handle}. Merchants can also embed the chat page with ?embed=1 or place “Chat with our Agent” badges from My Agents.

Every Agent gets {handle}@mail.bgent.io. Guests email that address; Bgent parses inbound mail, opens or continues an inbox thread, and escalates to the merchant when needed under the same lead-credit rules as chat and book.

Follow the stable URL pattern (/chat/{handle} → /api/v1/chat/{handle}), read JSON-LD and link alternates on the chat page, or load GET /api/v1/b/{handle} / MCP get_agent for chatUrl, chatApiUrl, and mailAddress. Network notes live at https://www.bgent.io/llms.txt.

Yes. From My Agents copy the chat URL, mailto:{handle}@mail.bgent.io, iframe embed, or badge HTML. Embed and badge loads can record referring hostnames so you see which sites drive traffic (bgent.io itself is excluded where practical).

No. Guests message for free. Merchants spend prepaid inbox credits when a new lead or order is unlocked — guests are not charged by Bgent for sending chat or email.

Merchants buy Pack 25, 100, or 500 inbox credits on https://www.bgent.io/pricing. Each credit unlocks one inbound lead or API order — including a new guest chat or a new conversation started by email to {handle}@mail.bgent.io. Create or claim typically grants 5 welcome credits. Checkout supports WeChat Pay (Jimu), FPS / bank transfer, and PayPal.

No. Unlocking a new guest conversation (book, chat, or first email to the agent mailbox) may consume one credit. Follow-ups on the same thread with the same contact do not charge again.

A lead is an inquiry unlocked with one inbox credit. An order is an API/MCP booking with kind “order” and an order total; when the merchant accepts, Bgent also accrues a 10% platform share for settlement from My Agents, separate from the credit unlock.

Locked leads and orders hide guest contact until the merchant spends a credit. That lets shops control inbox spend while Personal Agents can still book and chat through the network.

Unused credits are generally non-refundable once purchased, except where required by law or when Bgent cancels a pack due to a payment error. See the Terms of Service at https://www.bgent.io/terms.

Agent Port is the messaging layer between guests or Personal Agents and the merchant. Every book, chat, or agent-email creates an inbox thread; auto-reply can use DeepSeek or FAQ/hours/menu rules, then escalate to email, WhatsApp, Telegram, or WeChat Official Account.

Email, WhatsApp (Twilio), Telegram Bot, and WeChat Official Account, plus guest delivery by email or WhatsApp based on contact shape. Enable only the channels you use in My Agents; backup routing can notify secondary staff if a thread stays unacked past your timeout.

No. Configure the channels your team already uses. Agent Port works with a subset; unconfigured channels are simply skipped when escalating.

Prefer GET /api/v1/search, GET /api/v1/b/{handle}, POST /api/v1/b/{handle}/book, POST /api/v1/chat/{handle}, or MCP tools search_agents, get_agent, and book_agent. Profile JSON includes chatUrl, chatApiUrl, and mailAddress. Start at https://www.bgent.io/docs and https://www.bgent.io/llms.txt; prefer JSON over scraping HTML.

Yes. POST https://www.bgent.io/api/mcp exposes search_agents, get_agent, and book_agent. Discovery metadata is published at https://www.bgent.io/.well-known/mcp.json for MCP-capable clients.

Optional Bearer bgk_… keys attribute traffic to a Personal Agent. Public read and chat endpoints remain available without a key; respect rate limits and merchant unlock economics.

Humans can browse https://www.bgent.io/agents. Machines should use /api/v1/search, MCP search_agents, or agent profile JSON — not HTML scraping — for stable fields and filters (industry, country, region, city, claimed, contactable).

Guest contacts and merchant channel credentials are used to deliver Agent Port messages and billing. Bgent does not sell personal data. Details, processors, and rights requests are in the Privacy Policy at https://www.bgent.io/privacy.

Import pipelines only publish contacts that appear in open sources or that you add after claim. Enrichment may surface public website contacts; you can edit or clear fields anytime in My Agents.

Necessary cookies include bgent_session (Sign In), bgent_manage (My Agents manage-link access), and short-lived auth helpers such as bgent_wx_pending. Payment providers may set their own cookies at checkout. See https://www.bgent.io/cookie-policy.