Lap Account Management Overview

Account Management Overview API skill. Use when working with Account Management Overview for resources. Covers 25 endpoints.

Security Scan

The skill is an instruction-only mapping of 25 Frontegg tenant-management endpoints and requests a single API key/token which is generally proportional, though there are small wording inconsistencies you should check before use.

Purpose & Capability

Name/description indicate an Account Management Overview API for tenant resources and the SKILL.md documents 25 tenant-related endpoints against api.frontegg.com/tenants — the requested credential (one env var) is what you'd expect for calling that API.

Instruction Scope

Instructions are limited to setting an Authorization header and calling listed endpoints (verify access with GET, create with POST). They reference a local spec file (references/api-spec.lap) and include example npx CLI commands to fetch/search the spec; those CLI commands would invoke external tooling if the agent were to run them, but they are presented as optional examples rather than required steps. The doc does not instruct the agent to read unrelated files or exfiltrate data.

Install Mechanism

This is instruction-only with no install spec and no code files, so nothing is written to disk by the skill itself — lowest-risk on install mechanics.

Credentials

Only one env var is required (ACCOUNT_MANAGEMENT_OVERVIEW_API_KEY), which matches the need for an API credential. Minor inconsistency: the Auth section says "Bearer bearer" / "Set Authorization header with your Bearer token" while the variable name includes "API_KEY" — confirm whether the service expects a bearer JWT/token or an API key and scope the credential appropriately.

Persistence & Privilege

The skill does not request always:true and is user-invocable; it does not attempt to modify other skills or system settings.

Assessment

This skill is essentially a documented mapping of Frontegg tenant-management endpoints and appears coherent. Before installing: (1) confirm what form of credential Frontegg requires (Bearer token vs API key) and store a least-privilege token in ACCOUNT_MANAGEMENT_OVERVIEW_API_KEY; (2) be aware that if the agent executes the example npx commands it will run external npm tooling and perform network access; (3) do not provide broad credentials (e.g., full platform admin tokens) unless necessary — prefer scoped tokens. If you need stronger assurance, ask the skill author/source for the original API spec (references/api-spec.lap) and confirmation of the expected token format.

Account Management Overview

Auth

Bearer bearer

Base URL

https://api.frontegg.com/tenants

Setup

1. Set Authorization header with your Bearer token
2. GET /resources/tenants/v2 -- verify access
3. POST /resources/tenants/v1 -- create first tenants

Endpoints

25 endpoints across 1 groups. See references/api-spec.lap for full details.

resources

Method	Path	Description
GET	/resources/tenants/v1/{tenantId}	Get account (tenant) by ID
PUT	/resources/tenants/v1/{tenantId}	Update account (tenant)
DELETE	/resources/tenants/v1/{tenantId}	Delete account (tenant)
POST	/resources/tenants/v1	Create an account (tenant)
DELETE	/resources/tenants/v1	Delete current account (tenant)
POST	/resources/tenants/v1/{tenantId}/metadata	Add account (tenant) metadata
DELETE	/resources/tenants/v1/{tenantId}/metadata/{key}	Delete account (tenant) metadata
GET	/resources/tenants/v2	Get accounts (tenants)
GET	/resources/tenants/v2/alias/{alias}	Get account (tenant) by alias
GET	/resources/tenants/v2/{tenantId}	Get an account (tenant)
PUT	/resources/tenants/v2/{tenantId}	Update an account (tenant)
POST	/resources/sub-tenants/v1	Create sub-account
PUT	/resources/sub-tenants/v1/{tenantId}/management	Update sub-account (tenant) management
PUT	/resources/sub-tenants/v1/{tenantId}/hierarchy-settings	Update sub-account hierarchy settings
DELETE	/resources/sub-tenants/v1/{tenantId}	Delete a sub-account by ID
GET	/resources/account-settings/v1	Get account settings
PUT	/resources/account-settings/v1	Update account settings
GET	/resources/account-settings/v1/public	Get public settings
POST	/resources/migrations/v1/tenants	Migrate accounts (tenants)
GET	/resources/migrations/v1/tenants/status/{migrationId}	Accounts (tenants) migration status
GET	/resources/hierarchy/v1	Get sub-accounts (tenants)
POST	/resources/hierarchy/v1	Create sub-account (tenant)
DELETE	/resources/hierarchy/v1	Delete sub-account (tenant)
GET	/resources/hierarchy/v1/parents	Get parent accounts (tenants)
GET	/resources/hierarchy/v1/tree	Get sub-accounts (tenanants) hierarchy tree

Common Questions

Match user requests to endpoints in references/api-spec.lap. Key patterns:

• "Get tenant details?" -> GET /resources/tenants/v1/{tenantId}
• "Update a tenant?" -> PUT /resources/tenants/v1/{tenantId}
• "Delete a tenant?" -> DELETE /resources/tenants/v1/{tenantId}
• "Create a tenant?" -> POST /resources/tenants/v1
• "Create a metadata?" -> POST /resources/tenants/v1/{tenantId}/metadata
• "Delete a metadata?" -> DELETE /resources/tenants/v1/{tenantId}/metadata/{key}
• "List all tenants?" -> GET /resources/tenants/v2
• "Get alia details?" -> GET /resources/tenants/v2/alias/{alias}
• "Get tenant details?" -> GET /resources/tenants/v2/{tenantId}
• "Update a tenant?" -> PUT /resources/tenants/v2/{tenantId}
• "Create a sub-tenant?" -> POST /resources/sub-tenants/v1
• "Delete a sub-tenant?" -> DELETE /resources/sub-tenants/v1/{tenantId}
• "List all account-settings?" -> GET /resources/account-settings/v1
• "List all public?" -> GET /resources/account-settings/v1/public
• "Create a tenant?" -> POST /resources/migrations/v1/tenants
• "Get status details?" -> GET /resources/migrations/v1/tenants/status/{migrationId}
• "List all hierarchy?" -> GET /resources/hierarchy/v1
• "Create a hierarchy?" -> POST /resources/hierarchy/v1
• "List all parents?" -> GET /resources/hierarchy/v1/parents
• "List all tree?" -> GET /resources/hierarchy/v1/tree
• "How to authenticate?" -> See Auth section

Response Tips

• Check response schemas in references/api-spec.lap for field details
• Create/update endpoints typically return the created/updated object
• Error responses use types: When

CLI

# Update this spec to the latest version
npx @lap-platform/lapsh get account-management-overview -o references/api-spec.lap

# Search for related APIs
npx @lap-platform/lapsh search account-management-overview

References

• Full spec: See references/api-spec.lap for complete endpoint details, parameter tables, and response schemas

Generated from the official API spec by LAP