# 3DBAE Developer Platform

3DBAE offers three integration surfaces: a public REST API for published scene data, a JavaScript Model API for embedded viewer control and events, and an authenticated Model Context Protocol server for workspace automation.

## Machine-readable entry points

- OpenAPI: `https://3dbae.com/openapi.json`
- Platform MCP: `https://3dbae.com/api/mcp/platform/mcp`
- OAuth authorization metadata: `https://3dbae.com/.well-known/oauth-authorization-server`
- MCP protected-resource metadata: `https://3dbae.com/.well-known/oauth-protected-resource/api/mcp/platform/mcp`
- Capabilities: `https://3dbae.com/api/agent/v1/capabilities`

## Authentication

Standard MCP clients should use OAuth 2.0 Authorization Code with PKCE and dynamic client registration. Ask only for the named scopes required by the current task. Personal bearer tokens are an advanced fallback for desktop DCC integrations and other clients that cannot complete OAuth.

## Errors

Documented REST endpoints use JSON responses. Machine-facing REST failures use RFC 9457 Problem Details with the `application/problem+json` media type, a stable `code`, and a `resolution` hint.

## Agent and developer resources

- [Developer hub](https://3dbae.com/developers)
- [OpenAPI 3.1 document](https://3dbae.com/openapi.json)
- [Agent instructions](https://3dbae.com/agent-instructions.md)
- [LLM index](https://3dbae.com/llms.txt)
- [Sitemap](https://3dbae.com/sitemap.xml)

Use the public 3DBAE Platform MCP server at `https://3dbae.com/api/mcp/platform/mcp` for authenticated work. OAuth-capable clients discover sign-in and least-privilege scopes automatically.