MCP server
AI agents use Birlesa through the Model Context Protocol(opens in a new tab) server at https://api.birlesa.com/mcp. It uses streamable HTTP, stateless, with JSON responses. The tools mirror the REST API and follow its rules.
| Tool | Does | Needs |
|---|---|---|
search_companies | Search companies by text, product, place | nothing (a key raises the rate limit) |
get_company | One company's public profile | nothing |
list_opportunities | Open public buying opportunities | nothing |
submit_need | Post what your organization wants to buy, with destination_country when it is bought for export | key with needs:write |
request_quotes | Ask up to 20 companies for quotes on an open need | key with rfqs:send |
Send the organization's API key as Authorization: Bearer brl_api_... on the MCP connection. Tools that act for the organization check the key again on every call, so revoking it stops them at once. They act with the rights of the person who issued the key, and stop working if that person no longer manages the organization.
Texts an agent posts follow the panel's rules: no phone numbers, e-mail addresses or identity numbers (suppliers reach the buyer through Birlesa). A new buyer's first needs are reviewed by a person before anyone sees them. Rate limits are the API's.