# 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.

[Read llms.txt](https://www.benebid.org/llms.txt)

[Public content OpenAPI](https://www.benebid.org/openapi.json)

## 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.

- [GET /product.md](https://www.benebid.org/product.md)
- [GET /pricing.md](https://www.benebid.org/pricing.md)
- [GET /about.md](https://www.benebid.org/about.md)
- [GET /security.md](https://www.benebid.org/security.md)
- [GET /developers.md](https://www.benebid.org/developers.md)

[OpenAPI](https://www.benebid.org/openapi.json)

## 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 endpoint: https://www.benebid.org/mcp

Tools: get_product_overview, get_pricing, get_security_information.

Resources: benebid://product, benebid://pricing, benebid://security, benebid://developers.

Public read-only information. No credentials, customer records, writes or payments.

## 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.

## Your next event starts here.

Create your organization and start building your event.

[Get started](https://app.benebid.org/signup)