Integration status report
Report configured merchant integration surfaces and explicit payment capability flags. Direct merchant payment and optional credit purchases are distinct.
/v1/integrationsAuthorizationBearer token (JWT) · headerrequiredClerk human owner session JWT; iss must equal the configured Clerk issuer and the identity must be a human (not agent) owner with a verified email.
AuthorizationBearer token (JWT) · headerrequiredVerified AgentID agent JWT (iss https://auth.agentid.com) or an agentsub OAuth access token (typ at+jwt, iss https://api.agentsub.dev, scope agentsub:agent). The agent's human owner must exist in Clerk with the same verified email.
AuthorizationBearer token · headerrequiredScoped merchant API key (asm_...) issued via POST /v1/merchants/{id}/api-keys. Path/scope-restricted; cannot access human or agent routes.
AuthorizationOAuth2 access token · headerrequiredagentsub:ownerIdentity providers, merchant access endpoints and payment capability flags. No provider credentials or provider command integrations are exposed.
identityobjectShow propertiesHide properties
agentstringhumanstringaccessCheckobjectShow propertiesHide properties
endpointstringenabledbooleanmerchantRegistryobjectShow propertiesHide properties
endpointstringenabledbooleanpaymentsobjectShow propertiesHide properties
directMerchantLinkobjectShow propertiesHide properties
enabledbooleanoptionalCreditPurchasesobjectShow propertiesHide properties
enabledbooleanx402objectShow propertiesHide properties
enabledbooleanunauthorized problem; live 401s advertise WWW-Authenticate: Bearer resource_metadata=...
typestringrequiredtitlestringrequiredstatusintegerrequiredcodestringrequiredRuntime or provider configuration unavailable (runtime_configuration_required, signing_configuration_required, runtime_unavailable, workspace_unavailable, provider_configuration_required)
typestringrequiredtitlestringrequiredstatusintegerrequiredcodestringrequired