---
name: bountii-agent-access
description: How an AI agent reads getbountii.com programmatically: markdown content negotiation, llms.txt, the read-only public JSON API with its OpenAPI description, the MCP server, and how authentication works for account-bound calls.
---

# Reading Bountii as an agent

## Content

- Any public page returns Markdown when requested with the header `Accept: text/markdown`. The response carries `Content-Type: text/markdown` and an estimated `x-markdown-tokens` header. Browsers keep getting HTML.
- https://getbountii.com/llms.txt is the short overview; https://getbountii.com/llms-full.txt is every article in one file.

## Read-only JSON API (no key needed)

- GET https://getbountii.com/api/public/posts lists articles; add `?q=` for a keyword search. GET https://getbountii.com/api/public/posts/{slug} returns one article with its markdown body.
- GET https://getbountii.com/api/public/pricing returns plans and bounty ranges.
- GET https://getbountii.com/api/public/health is the status endpoint.
- The OpenAPI 3.1 description is at https://getbountii.com/api/public/openapi.json; human docs at https://getbountii.com/docs/api.

## MCP

A Streamable HTTP MCP server at https://getbountii.com/mcp exposes the same data as tools (overview, pricing, FAQ, article search and retrieval) and resources. The server card is https://getbountii.com/.well-known/mcp/server-card.json. No authentication; stateless, so send each JSON-RPC request as its own POST.

## Authentication

Bountii has no agent-only accounts. Account-bound calls use the operator's own Bountii session token (a Supabase Auth JWT) as `Authorization: Bearer <token>`; GET https://getbountii.com/api/public/me echoes who the token belongs to. Details and the OAuth metadata are in https://getbountii.com/auth.md.

## Courtesy

Identify your agent in the User-Agent header. Do not post content, create accounts or send email on a person's behalf without their explicit instruction; the dashboard has no public write API today.