Puma.tech developer resources

Puma.tech is a public, read-only site. Agents can read company pages and discovery documents. Puma AI is the research effort. Puma Browser is the product. Nothing on this host takes an API key, and nothing here is a sandbox.

Start with llms.txt for when to use the site. The short API index is API documentation.

What exists

How to read pages

Send Accept: text/markdown to a public HTML page. The response is Markdown with Content-Type: text/markdown; charset=utf-8 and Vary: Accept. The homepage also registers four read-only WebMCP tools: list_puma_pages, find_puma_page, get_puma_summary, and get_puma_app_links. Those tools run in the browser on the homepage. They are not available as a network API.

An unknown path requested with Accept: text/markdown stays HTTP 404 and returns Markdown that links to /llms.txt, /sitemap.xml, and /docs/api.

Errors

JSON documents and every /api/* path return RFC 9457 application/problem+json errors. Each object includes type, title, status, detail, instance, a stable code, and a resolution that says what to do next. There is no general /api service. Unknown paths under it are 404s, not missing features of a private API.

api_route_not_found

HTTP 404. No route exists under /api. Resolution: read /openapi.json, /llms.txt, and this page.

not_found

HTTP 404. A JSON document path does not exist. Resolution: use the OpenAPI description or llms.txt to find a published document.

method_not_allowed

HTTP 405, with Allow: GET, HEAD. These documents are read-only. Resolution: retry with GET or HEAD.

internal_error

HTTP 500. The document could not be read. Resolution: retry, then fall back to /llms.txt.

Product decisions

API keys are not available. Issuing API keys is an open product decision. Do not send an Authorization header and do not invent a key.

A sandbox is not available. Providing a sandbox environment is an open product decision. The public site is the only environment, and it is read-only.

OAuth and OpenID metadata files are published so discovery tools can see them. Token issuance, client registration, and a populated JWKS are not implemented. Building that authorization server is a product decision, separate from the static documents above.

Contact

Humans: [email protected], or [email protected] for roles. AI-generated job applications are not reviewed. Company pages: team, investors, careers.