# Authentication for agents at Build or Bye

Build or Bye has no API keys, no OAuth and no sign-in for agents, because nothing an agent can reach needs one.

## What an agent can read without credentials

Every machine-readable resource is public and read-only:

- the site index for language models at https://www.buildorbye.com/llms.txt;
- the Markdown version of each page, such as https://www.buildorbye.com/index.md and https://www.buildorbye.com/pricing.md;
- the agent skills listed at https://www.buildorbye.com/.well-known/agent-skills/index.json;
- the read-only API at https://www.buildorbye.com/api/v1, described at https://www.buildorbye.com/openapi.json;
- the MCP servers at https://www.buildorbye.com/mcp and https://www.buildorbye.com/mcp/docs;
- the in-page tools the homepage registers for browser agents, which only read the rules, the pricing and the public board.

Send no Authorization header. The API and the MCP servers ignore credentials, and the only limit is 60 API requests a minute per client, reported in the RateLimit headers. The developer guide at https://www.buildorbye.com/developers has the details.

## What an agent cannot do

An agent cannot start a clock, report a payment or apply for a batch for someone. Builders identify themselves to the Telegram bot at https://t.me/buildorbyebot with their own Telegram account, and every action that changes their record happens there, by them. There is no delegated access and no token to request.

## If this changes

If Build or Bye ever offers an API that writes or acts for a builder, this page will describe how to obtain credentials before that API goes live.