Vayyar Imaging · Authentication Profile

Vayyar Imaging Authentication

Authentication

Vayyar publishes no OpenAPI, so no securitySchemes could be derived. The only documented authentication surface found is on the Walabot DIY storefront (walabot.com, Shopify): customer-account OAuth 2.0 / OIDC published via RFC 8414 discovery at /.well-known/oauth-authorization-server and OIDC discovery at /.well-known/openid-configuration (both saved verbatim under well-known/). Authorization code flow with PKCE (S256), RS256 ID tokens, issuer https://shopify.com/authentication/10514071618, endpoints hosted on account.walabot.com. The storefront's UCP MCP endpoint additionally requires a UCP agent-profile handshake, and read-only storefront browsing (/products/{handle}.json) requires no authentication. The Walabot SDK (api.walabot.com) is a local USB device library with no network authentication.

Vayyar Imaging secures its APIs with oauth2, openIdConnect, and none across 1 declared security scheme, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).

CompanySensorsRadarImagingIoTHealthcareElderly CareAutomotiveSmart Home

Methods: oauth2, openIdConnect, none Schemes: 1 OAuth flows: authorizationCode API key in:

Security Schemes

walabot-customer-account-oidc openIdConnect

· flows: authorizationCode

Source

Authentication Profile

generated: '2026-07-21'
method: searched
source: https://walabot.com/.well-known/openid-configuration
docs: https://walabot.com/llms.txt
description: >-
  Vayyar publishes no OpenAPI, so no securitySchemes could be derived. The only
  documented authentication surface found is on the Walabot DIY storefront
  (walabot.com, Shopify): customer-account OAuth 2.0 / OIDC published via RFC
  8414 discovery at /.well-known/oauth-authorization-server and OIDC discovery
  at /.well-known/openid-configuration (both saved verbatim under well-known/).
  Authorization code flow with PKCE (S256), RS256 ID tokens, issuer
  https://shopify.com/authentication/10514071618, endpoints hosted on
  account.walabot.com. The storefront's UCP MCP endpoint additionally requires
  a UCP agent-profile handshake, and read-only storefront browsing
  (/products/{handle}.json) requires no authentication. The Walabot SDK
  (api.walabot.com) is a local USB device library with no network
  authentication.
summary:
  types: [oauth2, openIdConnect, none]
  oauth2_flows: [authorizationCode]
  pkce: S256
  notes: read-only storefront JSON endpoints are unauthenticated
schemes:
  - name: walabot-customer-account-oidc
    type: openIdConnect
    openIdConnectUrl: https://walabot.com/.well-known/openid-configuration
    issuer: https://shopify.com/authentication/10514071618
    flows:
      - flow: authorizationCode
        authorizationUrl: https://account.walabot.com/authentication/oauth/authorize
        tokenUrl: https://account.walabot.com/authentication/oauth/token
    grant_types: [authorization_code, refresh_token, "urn:ietf:params:oauth:grant-type:jwt-bearer"]
    token_endpoint_auth_methods: [client_secret_basic]
    code_challenge_methods: [S256]
    id_token_signing_alg: [RS256]
    sources: [well-known/vayyar-imaging-openid-configuration.json]

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This security artifact

curl "https://apis.io/api/v1/security/vayyar-imaging-authentication"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.