API reference

Scopes & bundles

Scope format

Business scopes use {actor}:{resource}:{action}. Managed keys receive only the exact scopes selected in Lucra.

Brand scopes

Resource	Actions
`organization`	`read`, `write`
`creator`	`read`
`programs`	`read`, `review`
`submissions`	`read`, `review`
`ads`	`read`
`products`	`read`
`analytics`	`read`
`finance`	`read`

Agency scopes

Agency scopes use the partner: prefix and expose the same supported action set as brand scopes: organization read and write, resource reads, and program and submission reviews. They apply to the agency's own workspace by default and to a managed client only when client is supplied.

MCP scopes

mcp:tools:read permits MCP initialization and tool discovery;
mcp:tools:call permits invocation, but every tool still requires its matching brand or partner business scope.

Bundles

Lucra presents convenient bundles while persisting their exact expanded scopes:

Bundle	Description
`brand.read`	All supported brand reads
`brand.manage`	Supported brand reads, organization write, and reviews
`partner.read`	All supported agency reads
`partner.manage`	Supported agency reads, organization write, and reviews
`mcp.call`	MCP discovery and invocation

Fetch the live taxonomy without authentication:

curl https://api.onlucra.com/v1/scopes

Scopes for integrations, OAuth, provider connection management, billing changes, payouts, member administration, invites, media upload, campaign launch, or resource deletion do not exist on the public surface.