Get the hosted UCP presence summary
Plain-language summary plus the served profile, capabilities, and freshness declarations. Read-only in V1.
/stores/{store_id}/presenceAuthorizationBearer token (JWT) · headerrequiredJWT issued by the external IdP via the OAuth 2.0 authorization-code flow (Kinde in
production; a simulator in test). The client obtains it and sends it as a Bearer token on
every authenticated call. Sarvex's services verify it — issuer, audience, signature
(IdP JWKS), expiry — and read identity and tenant from its claims. Sarvex does not issue
or revoke these tokens. merchant_id/store_id are read from the verified claims (and the
merchant→store mapping), never from the URL. The operator scope is required for
/operator/*. Operators acting on a specific merchant pass the X-Operate-As header,
which is recorded in the audit log.
store_idstringrequiredA store the caller's merchant owns. Authorized server-side against the principal; not a free-form tenant selector.
Presence.
summarystringproduct_countintegercapabilitiesstring[]freshness_declarationsobjectservingstringservingdegradedprofile_onlynot_servingprofile_urlstring<uri>The merchant-domain well-known URL where the profile is served.
profile_reachablebooleanWhether the profile currently returns a 200 at the merchant origin.
published_versionstringThe single UCP spec version currently rendered into this store's /.well-known/ucp document. A discovery profile declares exactly one version; this is not a list.
supported_versionsstring[]UCP spec generations Sarvex's negotiation engine can actually serve a live response in for this store today, oldest first. A platform agent may negotiate this store into any of these, not only published_version.