Query the NCR Voyix BSP sites and organization hierarchy using nep-organization and nep-enterprise-unit headers
domain: developer.ncrvoyix.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Send nep-organization on every request to scope it to a specific organization/tenant
Add nep-enterprise-unit to further scope to one specific site; omit it to get results across every enterprise unit in the organization
Query the Site service to retrieve, geo-radial/polygon search, or resolve enterprise-configured settings for sites
Use the site/organization identifiers returned here to correctly scope subsequent Catalog, Orders, and other BSP service calls
Confirm exact resource path names against your authenticated API Explorer access, since public docs describe the header-based scoping model but not the literal path strings
Known gotchas
Multi-tenancy in BSP is expressed entirely through headers (nep-organization, nep-enterprise-unit), not through the URL path — treating it as purely path-based will cause scoping bugs
Omitting nep-enterprise-unit is a valid, meaningful choice (org-wide results), not an error — don't assume it's always required
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?