← Back homeDEVELOPERS / API

Wrap an API with clear authority.

API adapters must declare exact operations, credential scope and externally visible effects.

api.concept ILLUSTRATION
{
  "name": "crm.read",
  "input": "typed_input",
  "output": "typed_output",
  "runtime": "declared",
  "permissions": [
    "minimum_scope"
  ],
  "status": "candidate"
}

Three things a Capacity needs

A specific contract before a Solution can rely on it.

01 / CONTRACTMethod and input

Declare, document and test this boundary.

02 / CONTRACTAuth / scope

Declare, document and test this boundary.

03 / CONTRACTOutput and retries

Declare, document and test this boundary.

CONCRETE EXAMPLE

A CRM read endpoint cannot be promoted as a write connector. A timeout after sending requires reconciliation.

NEXT / PROVIDER

Make your capability usable by builders

Conceptual guidance for Capacity creators. No public production SDK/API is offered by this website.

info@kabin.cloudBack to homepage