Capabilities
On this page
How to read the machine-readable capabilities manifest
The Manage Bet Codes API publishes GET /v1/capabilities as a public, keyless manifest cached for 5 minutes with an ETag. It lists the API version (v1, 1.0.0), base URL (https://api.managebetcodes.app/v1), auth header (X-API-Key with mbc_live_ prefix), every /v1 action with its price and limits, and links to docs, OpenAPI, markets, bookmakers, and llms.txt.
GET /v1/capabilities{
"name": "Manage Bet Codes API",
"version": "1.0.0",
"api_version": "v1",
"base_url": "https://api.managebetcodes.app/v1",
"auth": {"header": "X-API-Key", "key_prefix": "mbc_live_",
"create": "https://managebetcodes.app/dashboard/api"},
"links": {
"docs": "https://managebetcodes.app/docs",
"openapi": "/v1/openapi.json",
"errors": "/v1/errors",
"markets": "/v1/markets",
"bookmakers": "/v1/bookmakers",
"llms": "https://managebetcodes.app/llms.txt"
},
"actions": [
{"name": "convert", "method": "POST", "path": "/v1/convert",
"price_credits": 2, "per": "target", "async": false,
"idempotent": true, "limits": {"targets": 6},
"next_actions": ["view", "history"]}
],
"limits": {
"sync_targets": 6,
"batch_targets": 15,
"job_codes": 20,
"job_targets": 15,
"job_pairs": 100,
"history_days": 90
},
"error_codes": "/v1/errors",
"sdk": {"python": "managebetcodes", "typescript": "@managebetcodes/sdk", "mcp": "@managebetcodes/mcp"},
"mcp": {"npm": "@managebetcodes/mcp", "endpoint": "https://api.managebetcodes.app/v1/mcp"}
}The manifest is public. It is cached for 5 minutes and sends an ETag. It lists only /v1 routes.
Which public catalogs need no API key
The Manage Bet Codes API serves six public catalogs without an API key: help index, OpenAPI contract, error catalog, canonical market catalog, bookmaker capability catalog, and the caller's plan readout. GET /v1/usage is the only keyed catalog; the bookmaker catalog adds supports_book, supports_search, supports_markets, supports_resolve, and supports_tracking flags.
| Route | Purpose | Key |
|---|---|---|
GET /v1 | Help index | No |
GET /v1/openapi.json | Full OpenAPI 3.1 contract | No |
GET /v1/errors | Error catalog | No |
GET /v1/markets | Canonical market catalog | No |
GET /v1/bookmakers | Bookmaker capability catalog | No |
GET /v1/usage | The caller's plan and limits | Yes |
The bookmaker catalog adds these flags: supports_book, supports_search, supports_markets, supports_resolve, and supports_tracking.
Which Link headers and agent catalogs aid discovery
The Manage Bet Codes API advertises service-desc, service-doc, service-meta, and status through Link headers, and /.well-known/api-catalog follows RFC 9727 with the same four links. AI agents should read llms.txt for the agent-readable index of every endpoint.
Link: </v1/openapi.json>; rel="service-desc"; type="application/vnd.oai.openapi+json",
</docs>; rel="service-doc",
</v1/capabilities>; rel="service-meta"; type="application/json",
</v1/health>; rel="status"; type="application/json"/.well-known/api-catalog follows RFC 9727 and lists service-desc, service-doc, service-meta, and status.
Use llms.txt for an agent-readable index.