Open Concept Lab (OCL) Capabilities API

The capabilities API from Open Concept Lab (OCL) — 2 operation(s) for capabilities.

GitHub OpenAPI

Operations 2

POST /capabilities/consume/ Capabilities consume create #
POST /capabilities/refund/ Capabilities refund create #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/openconceptlab:openconceptlab-capabilities-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openconceptlab-capabilities-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: OCL Capabilities API
  description: 'OCL API (2.3.250-d17a48ac)


    FHIR terminology Swagger.'
  version: 2.3.250-d17a48ac
servers:
- url: https://api.openconceptlab.org/
security:
- Basic: []
- Token: []
tags:
- name: Capabilities
paths:
  /capabilities/consume/:
    parameters: []
    post:
      operationId: capabilities_consume_create
      description: 'Cross-service check-and-consume. Used by services that don''t share oclapi2''s

        database (e.g. ocl-ai-assistant, TQ4) — they hold the same bearer token the

        caller authenticated with, so consumption is always scoped to `request.user`;

        no service can consume against another user''s ledger.'
      responses:
        '201':
          description: ''
      tags:
      - Capabilities
      summary: Capabilities consume create
      x-summary-source: derived
  /capabilities/refund/:
    parameters: []
    post:
      operationId: capabilities_refund_create
      description: 'Manual ledger correction (see CapabilityPolicy.refund) - e.g. staff fixing an

        over-count after a bug. Staff-only, and operates on a user given explicitly

        in the request body: this is an admin tool for correcting ANY user''s

        ledger, not a per-request refund a service would issue against its own

        caller''s ledger (a caller should consume a capability only once the action

        it gates has actually succeeded - see

        UserProfile.check_and_consume_capability - which needs no refund path at

        all, so no cross-service caller needs staff access to reach this).'
      responses:
        '201':
          description: ''
      tags:
      - Capabilities
      summary: Capabilities refund create
      x-summary-source: derived
components:
  securitySchemes:
    Basic:
      type: http
      scheme: basic
    Token:
      type: apiKey
      name: Authorization
      in: header