Skip to main content
POST
Resolve a connect client_id to its display name + eligibility

Authorizations

Authorization
string
header
required

A Nevermined API key: Authorization: Bearer <sandbox:… | live:…>. Environment-prefixed, not a bare JWT — send the whole string.

Body

application/json
client_id
string
required

A registered connector id, or a CIMD client_id (an https URL such as https://chatgpt.com/oauth/client.json).

Example:

"fleet"

Response

Connector details

connectorName
string
required

The connector's display name: the registered name of a static client, or the client_name its Client ID Metadata Document declares for a CIMD (https-URL) client — never the caller-supplied client_id. Falls back to the client_id when the registry has no name. A CIMD name is self-asserted: show clientOrigin beside it.

Example:

"LangSmith Fleet"

clientOrigin
string | null
required

For a CIMD (https-URL) client, the origin of its client_id URL — the verified identity behind the self-asserted connectorName; the consent screen displays its host beside the name. null for a statically registered client. Always present.

Example:

"https://chatgpt.com"

accountLevelAllowed
boolean
required

True when the client may request at least one account-level consent type (registered, allowAccountLevel, verified, and allowedConsentTypes non-empty). Check allowedConsentTypes for the type being requested.

Example:

true

The account-level consent types this client may request: account_access (a capped card mandate) and/or commerce (a capped on-chain spending mandate for external merchants). Empty when the client may request neither.

Available options:
account_access,
commerce
Example: