Glam already exposes account-scoped Agent and MCP surfaces. They reuse the same projects, Elements, quotes and spend controls as the customer product instead of handing provider credentials to outside agents.
REST AGENT
Account-scoped orchestration
Signed-in customers and customer-issued Glam API keys can read account/project truth, estimate work, create drafts and attach saved Elements. Paid generation submit remains signed-in customer-session only.
AVAILABLE IN CURRENT PRODUCTMCP
Reads + draft-only writes
The MCP surface can read account/project/Element truth, estimate generation, create a draft and attach saved Elements. It deliberately has no generation-submit tool.
AVAILABLE IN CURRENT PRODUCT
REST Agent routes
Read and draft routes accept the existing Glam customer session or a customer-issued gl_live_... key. Paid generation submit stays customer-session only. Provider identity, provider credentials and private provider economics remain underneath Glam.
GET /api/agent/accountRead the signed-in customer's safe account view.READ
GET /api/agent/estimateGet the current customer-facing Glam Credit quote.ZERO SPEND
GET /api/agent/projectsList account-owned Glam projects.READ
POST /api/agent/projectsCreate an idempotent draft project.ZERO SPEND
POST /api/agent/projects/:id/elementsAttach account-owned saved Elements to a draft.ZERO SPEND
POST /api/agent/projects/:id/submitSubmit one project only after explicit APPROVE_GENERATION + exact quoted-credit confirmation.CONSEQUENTIAL
MCP tool catalog
The current MCP endpoint is /api/mcp and accepts the existing customer session or a customer-issued gl_live_... key. It is provider-neutral, draft-write only, and exposes no generation-submit, direct credit-mutation or provider-execution tool.
glam_project_create_draftCreate an idempotent project draft.ZERO SPEND
glam_project_attach_elementsAttach saved Elements to that draft.ZERO SPEND
Your Glam API keys
Create account-scoped keys for REST Agent and MCP read/draft automation. The raw gl_live_... secret is shown once. Keys have fixed read + draft scopes and no generation-submit authority.
Checking your Glam account…
Sign in to manage developer keys
Copy this key now. Glam will not show the raw secret again.
What Glam still does not claim
There is no Glam CLI product yet. API keys have no spend scope. REST generation submit remains customer-session only, and MCP has no generation-submit tool. External automation cannot mint credits, mutate payment credentials, select hidden provider credentials or bypass the normal customer generation approval gate.