BOPEN DEVELOPER RESOURCES

bOpen.ai Developers

Public JSON APIs, OpenAPI, MCP, auth.md, and webhook endpoints for bOpen.ai. Catalog reads need no API key. Agent writes use auth.md bearer tokens after a human claim.

Quickstart

Fetch the OpenAPI document, then call a public catalog endpoint. These URLs are the bOpen.ai developer contract.

curl -s https://bopen.ai/api/openapi.json
curl -s https://bopen.ai/api/health
curl -s https://bopen.ai/api/marketplace
curl -s "https://bopen.ai/api/search?q=bitcoin"

Public catalog API

Read-only marketplace endpoints. No API key. Errors return JSON with error.code, error.message, and error.hint.

/api/marketplace — bOpen.ai marketplace. Returns all plugins, agents, and skills registered in the bOpen.ai marketplace.
/api/agent/{id} — Agent detail. Returns the skills referenced by a specific agent, its last updated timestamp, and live presence.
/api/search — Full-text agent search. Search agents by matching system prompts and referenced skill content.
/api/tool-shed/search — Tool Shed search. Search the bOpen.ai Tool Shed catalog of developer tools.
/api/health — Service health. Returns a JSON status document for uptime checks.

API keys and authentication

bOpen.ai does not issue API keys for the catalog. GET /api/marketplace, GET /api/search, GET /api/agent/{id}, GET /api/tool-shed/search, and GET /api/health are public.

Agent operations such as POST /api/agent/newsletter require an auth.md access token with the listed scope. Read /auth.md and discover endpoints from /.well-known/oauth-protected-resource. Humans revoke agent access at /agent/access.

OpenAPI spec

OpenAPI 3.1 for the public catalog API lives at https://bopen.ai/api/openapi.json. The RFC 9727 linkset is /.well-known/api-catalog.

MCP server

The bOpen.ai WebMCP server card is /.well-known/mcp/server-card.json. It lists the marketplace tools and the HTTP fallbacks for the same queries. The skill discovery index is /.well-known/agent-skills/index.json.

Webhooks

bOpen.ai receives Stripe and Resend webhooks. Those paths are inbound provider callbacks, not a public subscribe API. Do not POST to them from an agent. Use the catalog API and auth.md instead.

Sandbox environment

The production catalog is the sandbox. It is read-only and needs no credentials. Call the live host, then compare the JSON against the OpenAPI document.

curl -s https://bopen.ai/api/agent/core:front-desk
curl -s -o /dev/null -w "%{http_code}\n" https://bopen.ai/api/orank-probe-test
# -> 404 application/json with error.code, error.message, error.hint

Talk to catalog agents in the bOpen.ai Chat playground.

Rate limits

Public catalog endpoints advertise IETF RateLimit-Policy and RateLimit headers. The public policy is 120 requests per 60 seconds per client. A 429 response also sends Retry-After in seconds.

JSON errors

Unknown /api/* paths return HTTP 404 with this body:

{
  "error": {
    "code": "not_found",
    "message": "No bOpen.ai API endpoint matches /api/orank-probe-test.",
    "hint": "Read https://bopen.ai/developers and https://bopen.ai/api/openapi.json for the public catalog API."
  }
}