Vision Core developer access

Machine clients, credentials, token issuance, installed Apps, organization context, public keys, and allowlisted publication retrieval.

Owner: Vision Core
Lifecycle: preview
Runtime: acceptance-gated
App entitlement: vision-core
Audience: Vision Platform audience
Workspace: Vision organization and installation context

Authority boundary

Vision owns machine identity and common API policy. Source Apps retain their resource and business authority.

Complete preview contract: Every operation and MCP capability in the approved definitions below is documented. The lifecycle and runtime labels describe stability and availability, not partial catalog coverage.

Platform API

Owning App: Vision Core
Contract version: 1.0.0-preview.2
Audience: Vision Platform audience
Workspace binding: Vision organization and installation context

Download the authoritative OpenAPI 3.1 definition

5 operations

Generated from Vision Platform API 1.0.0-preview.2

POST/oauth/token
Exchange a client credential for a short-lived access token
No bearer scope declared
Full operation reference →
GET/platform/v1/organization
Read organization and installation metadata
vision.organization.basic:read
Full operation reference →
GET/platform/v1/apps
List installed App API metadata
vision.apps:read
Full operation reference →
GET/platform/v1/publications/{appId}/{resourceType}/{sourceRecordId}
Read one allowlisted published App projection
platform.publications:read
Full operation reference →
GET/.well-known/jwks.json
Read active public token verification keys
No bearer scope declared
Full operation reference →

Publication evidence

This page is generated from the approval registry. Contract checksums, source drift, security declarations, scopes, references, and operation identifiers are verified before publication. A production documentation deployment remains a separate approval and rollback gate.