People and agents, working together.
Benebid works
with agents, too.
Use clean public resources to understand the platform and help people plan their next event.
Readable by design.
Product, pricing, purpose, security and developer pages have clean Markdown equivalents. The llms.txt index gives agents a concise starting point.
Public information API.
Read-only content endpoints require no credentials and return Markdown. The OpenAPI contract describes these public resources; it does not describe private customer operations.
A small, useful MCP surface.
Public tools answer product, pricing and security questions. Resources expose the same source-controlled content as the website. No organization credentials or guest information are involved.
STREAMABLE HTTP · PUBLIC, READ-ONLY
https://www.benebid.org/mcpTools: get_product_overview, get_pricing, get_security_information
Resources: benebid://product, benebid://pricing, benebid://security, benebid://developers
Permissions travel
with the work.
Customer event operations belong to the same permission model as the application. Public product-information tools have no access to customer records and cannot perform writes or payments.
Give agents useful context. Keep authority explicit.