Capability gaps

GET

/api/v1/realms/gaps

const url = 'http://localhost:11044/api/v1/realms/gaps';
const options = {method: 'GET', headers: {'X-Embabel-Api-Key': '<X-Embabel-Api-Key>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request GET \
  --url http://localhost:11044/api/v1/realms/gaps \
  --header 'X-Embabel-Api-Key: <X-Embabel-Api-Key>'

What this world could add: installable realms (directory minus installed), inert APIs with the key that unlocks each, and structural gaps. The REST projection of the same CapabilitySuggester that serves the suggest_capabilities MCP tool.

Authorizations

apiKeyAuth
basicAuth

Responses

200

Capability gaps

*/*

What this world could add: realms it could install, APIs that are inert and what would unlock each, and structural gaps

object

inertApis

required

APIs declared but inert, with the reason and what would make each answer

Array<object>

An API the world declares that cannot answer yet

object

name

required

The API’s name

string

reason

required

Why it is inert

string

unlockedBy

What would unlock it, typically the key to set; null where nothing the owner sets would

string

installableRealms

required

Directory realms not installed here

Array<object>

A directory realm this world has not installed

object

description

required

What the realm adds

string

name

required

The realm’s directory name

string

source

required

What to install it from: a git clone URL or registry identifier

string

url

A page to read about it; null where the directory gives none

string

structuralGaps

required

Gaps in the world’s shape, each written as a sentence

Array<string>