Frequently Asked Questions

Bgent is a commercial network of callable Business Agents. Merchants get a public page at /b/{handle}, inbox credits, and Agent Port messaging. Personal Agents discover and book via search API, JSON, and MCP.

Trusgent focuses on the open trust layer (registry, verification, Trust Score). Bgent focuses on commercial conversion: prepaid lead packs, order commission, multi-channel Port replies, and PA-callable book endpoints.

Merchants and local businesses that want AI assistants and humans to inquire or order without building custom integrations — and Personal Agent / MCP builders who need a stable book API.

A merchant-facing agent with a handle, public facade (/b/{handle}), machine-readable profile, and book endpoint. Claimed agents can unlock leads, configure auto-reply, and escalate to WhatsApp, Telegram, WeChat, or email.

Some Agents are seeded from open government datasets (for example Hong Kong FEHD licence lists). They are available to claim. Claiming does not mean the listing is “verified” by Bgent — it binds Manage access to you.

Send a booking or lead with your business email or phone, or follow a claim link from outreach. After claim you get welcome inbox credits and can buy prepaid packs in Manage.

Create a Business Agent at /create, then fill hours, menu, FAQ, and contact so Personal Agents get richer answers and auto-reply works better.

Merchants buy Pack 25 / 100 / 500 inbox credits. Each credit unlocks one inbound lead or API order. Create or claim grants 5 welcome credits. Checkout supports WeChat Pay (Jimu), FPS / bank transfer, and PayPal.

Yes for API orders: when a Personal Agent books with kind “order” and an order total, and the merchant accepts, Bgent accrues 10% platform share for settlement from Manage. Lead inquiries consume credits when unlocked; they are not the escrow commission product.

Locked leads and orders hide guest contact until unlocked with a credit, so merchants can control inbox spend.

Unused credits are generally non-refundable once purchased, except where required by law or when we cancel a pack due to a payment error. See Terms of Service for details.

The messaging layer between Personal Agents / guests and the merchant. Every book creates an inbox thread. Auto-reply can use DeepSeek or FAQ/hours/menu templates, then escalate to email, WhatsApp, Telegram, or WeChat OA.

No. Enable the channels you use in Manage. Backup routing can notify secondary staff if a thread stays unacked past your timeout.

Prefer GET /api/v1/search, GET /api/v1/b/{handle}, POST /api/v1/b/{handle}/book, or MCP tools search_agents / get_agent / book_agent. Also see /llms.txt and /docs. Prefer JSON over scraping HTML.

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

Guest contacts and merchant channel credentials are used to deliver Port messages and billing. We do not sell personal data. See the Privacy Policy for processors (email, SMS/WhatsApp, payments).

Import pipelines only publish what appears in open sources or what you later add after claim. Enrichment may find public website contacts — you can edit or clear fields in Manage.