BAPECLUB Developers — build on BAPECLUB Scout

Quickstart

Search the catalog via MCP (any agent or CLI):

curl -X POST https://bapeclub.app/api/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Read the OpenAPI spec:

curl https://bapeclub.app/openapi.json

Machine resources

• OpenAPI specification (/openapi /openapi.json)
  All public REST endpoints, typed schemas, error model, rate limits.
• MCP server (Streamable HTTP) (/openapi — POST JSON-RPC)
  JSON-RPC 2.0 — tools/list, tools/call. Claude/ChatGPT-compatible.
• MCP manifest (/openapi /mcp.json)
  Standard client discovery manifest (also at /.well-known/mcp.json).
• Agent instructions (llms.txt) (/openapi /llms.txt)
  When-to-use guidance + full agent surface index.
• Agent manifest (/openapi /.well-known/agent.json)
  Capabilities + content-signals declaration.
• API catalog (RFC 9727) (/openapi /.well-known/api-catalog)
  Link-format catalog of machine endpoints.
• Sitemap (/openapi /sitemap.xml)
  Canonical URLs.

Versioning & deprecation

Current API version: 1.1.0 (semver, tracked in /openapi.json). Breaking changes bump the major version and publish under /v1/, keeping the current surface available for at least 90 days. Deprecated endpoints are marked deprecated: true in the spec and respond with Deprecation / Sunset headers. Pin the version you integrate against.