# AdExec AI > AdExec AI is a governed creative and publishing platform for organizations. Agents can generate image and video assets, create publishing drafts, request scheduling or immediate publishing, inspect approvals, and read credit usage through a remote MCP server. External integrations can use organization API keys for asset uploads and social-channel operations. ## Machine-readable documentation - [REST API](https://app.adexecai.shop/docs/api.md): Authentication, organization API keys, `/api/v1` asset and channel routes, dashboard routes, upload flow, generation-job workflow, credits, response envelopes, and error codes. - [MCP](https://app.adexecai.shop/docs/mcp.md): Endpoint, OAuth 2.1 with PKCE, initialize, tools/list, all 17 tools with descriptions and input-schema summaries, generation jobs, publishing, and safe error codes. ## Human-readable documentation - [REST API](https://app.adexecai.shop/docs/api): HTML rendering of `/docs/api.md`. - [MCP](https://app.adexecai.shop/docs/mcp): HTML rendering of `/docs/mcp.md`. ## Canonical endpoints - REST API base URL: https://app.adexecai.shop - MCP endpoint: https://mcp.adexecai.shop/mcp - MCP protected-resource metadata: https://mcp.adexecai.shop/.well-known/oauth-protected-resource - MCP authorization-server metadata: https://mcp.adexecai.shop/.well-known/oauth-authorization-server ## Authentication summary - External REST: `Authorization: Bearer ` on `/api/v1/*`. - Dashboard REST: `HttpOnly` session cookie on `/api/orgs/{orgId}/*`. - MCP: OAuth 2.1 bearer access token; dashboard sessions and organization API keys are not interchangeable with MCP tokens. ## Policy - Documentation is public and readable without login. - Use placeholders for credentials. Never publish API keys, OAuth tokens, refresh tokens, PKCE verifiers, presigned upload URLs, or presigned headers.