The four scope dimensions
Brands
Which brands the key can touch. Empty = every brand the minter can access.
Platforms
Which platforms the key can reach (Meta, Amazon, Amazon Seller, Shopify, Google Ads, TikTok, LinkedIn, X, PostHog). Empty = all.
Access mode
read — audits, reads, status only. write — can also stage approvals and mutations (still HITL-gated).
Operations
Optionally narrow to specific operations (e.g. only
list_* reads), tighter than the read/write split.Roles re-intersect on every request
A key never grants more than its minter currently has. Mesh Pilot resolves access live on each call:- Per-brand role. Each member is a
viewer(read-only) oroperator(read + write) on each brand they’re on. A write-mode key minted by someone who is only a viewer on Brand A cannot write to Brand A. - Workspace role. Workspace
owner/admincan see org-wide audit across every key;operator/viewersee their own. - Live re-check. The ceiling is re-computed against current access every request. Remove someone’s access to a brand and every key they minted loses that brand immediately.
Worked example: outside consultant
You want a consultant to analyse one brand’s Amazon Ads, read-only, for two weeks. Mint a key with:- Brands:
ayurpetonly - Platforms:
amazononly - Access mode: read
- Expiry: 14 days
- Rate limit: 500 calls/day
What a denied call looks like
If a key attempts something outside its ceiling — a brand it isn’t scoped to, a platform it can’t reach, or a write from a read-only key — the server refuses and records adenied entry in the audit log with the reason. The action never reaches the platform.
See the audit log
Every ok / denied / error, per key.