OpenAPI 3.1.2
Typed operations, request and response schemas, unique operation IDs, scoped security, and structured errors.
Open OpenAPI JSON3DIMLI Developers
Verify purchases from software and game clients, or connect an AI assistant to creator-commerce workflows through the 3DIMLI remote MCP server. The public schemas below are designed for automated discovery and client generation.
Typed operations, request and response schemas, unique operation IDs, scoped security, and structured errors.
Open OpenAPI JSONUse Streamable HTTP with OAuth 2.0 Authorization Code + PKCE to give agents least-privilege access.
Open MCP server.jsonDiscover public product pages, policies, documentation, feeds, sitemaps, API metadata, and MCP resources.
Open llms.txtSellers generate a bearer token in the dashboard with only the license verification permission. Responses use typed JSON, and errors include stable codes, human-readable messages, and recovery hints.
POST /api/software/v1/verify
POST /api/games/v1/verify
Authorization: Bearer <license_verification_token>
Content-Type: application/json
{"key":"<order-item-uuid>","product_slug":"my-product"}MCP clients discover authorization endpoints and named scopes automatically. Request only the scopes needed for the intended workflow; users review and approve access before the connector receives tokens.