> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dapta-mcp/skills/accounts.md). # Accounts, Identity & Billing These skills answer "who am I, what can I see, how healthy is my account, and what am I spending?" {% hint style="info" %} Every skill here is **read-only**. None of them change your account. {% endhint %} ### iam-account-searcher **What it does:** Searches and inspects the accounts, users, and workspaces you have access to. Your discovery tool for "who am I and what can I see?" **Use it when:** You want to know which workspaces or accounts you have access to, find an account or user by name or email, or look up the details of a specific account or workspace. **Try saying:** * "What workspaces do I have access to?" * "Find the account named Acme Corp." * "Look up the user with email ." **You get back:** A one-line summary plus a table of matching workspaces, accounts, or users (with id, name, parent account, subscription, status), or the full detail row for a single account or workspace. If nothing matches, it says so clearly. **Writes data?** No, read-only. **Behind the scenes:** `get_user_workspaces`, `get_user_accounts`, `search_iam_account`, `get_iam_account_details`, `list_iam_workspaces`, `search_iam_user`, `get_workspace_by_id`, `get_account_workspace_ids`. *** ### iam-legacy-mapper **What it does:** Connects older Dapta "organization" IDs with their current workspace and parent billing account, so data from legacy logs can be tied back to the right account. Also confirms which workspace owns a given agent, call, or usage record. **Use it when:** You have a legacy organization ID from a log line and need its account or workspace, you have an account and want all its workspaces, or you only have an entity ID (agent, call, usage) and need to confirm which workspace owns it. **Try saying:** * "I have an organization\_id from a legacy log, what account and workspace is it?" * "For account , what are all its workspaces?" * "Who owns agent ?" **You get back:** The IAM workspace plus parent account details for a legacy ID, the full list of workspaces under an account, or the owning workspace for an entity, with clear messaging if a mapping is not found. **Writes data?** No, read-only. **Behind the scenes:** `map_legacy_to_iam`, `map_iam_to_legacy`, `get_workspace_by_id`, `verify_workspace_entity_ownership`. *** ### account-evaluation **What it does:** Gives you a full health check of your Dapta account. It pulls your company profile, agents, call performance, feedback, and billing, then classifies your account into a stage (Setup, Optimization, or Scaling) and hands you a prioritized action plan. **Use it when:** You want a diagnosis of your account, want to know what stage you are at, what is missing before you can scale, or whether you are ready to make real calls. **Try saying:** * "Evaluate my account, what phase am I in?" * "How is my account doing, and what's missing to scale?" * "Am I ready to start making real calls?" **You get back:** A prominent stage badge with an explanation, a checklist of which setup and optimization milestones you have hit (with real values), your actual call metrics when calls exist, three to five prioritized next steps naming your specific agents, and a compact account-context summary. **Writes data?** No, read-only. **Behind the scenes:** `get_workspace_company_context`, `list_agents`, `get_agent_call_statistics`, `get_connection_rate`, `list_calls`, `get_feedback_summary`, `analyze_variable_usage` and `get_agent_post_call_schema`, `get_my_balance`. *** ### industry-intelligence **What it does:** Tells you what industry your Dapta account is classified in and surfaces how peers in that same industry use their voice agents: popular use cases, comparable accounts, and the hours and days they typically run calls. **Use it when:** You want to know your industry, what other businesses like yours are doing on Dapta, which use cases to try next, or when similar companies tend to run their agents. **Try saying:** * "What industry is my account in?" * "What use cases are popular for businesses like mine?" * "When do similar companies usually run their voice agents?" **You get back:** Your industry classification, suggested use cases personalized to your account, a list of peer accounts in your industry, and timing patterns (hour-of-day and day-of-week) aggregated across peers. **Writes data?** No, read-only. **Behind the scenes:** resolves your industry via a fast cached lookup (`get_account_classification`, `get_industry_from_iam`, `infer_industry_from_agents` and `infer_industry_from_context`, with `classify_account_industry` as a last resort), then `get_use_case_recommendations`, `get_use_case_adoption_by_industry`, `get_top_accounts_by_industry`, `get_timing_patterns`, `get_industry_overview`. *** ### billing-analytics **What it does:** Pulls up your current plan, remaining credit balance, recent usage, and subscription details straight from Dapta's billing system. **Use it when:** You want to check your credits, see how much you have used this month, confirm which plan you are on, or review your subscription and renewal date. **Try saying:** * "How many credits do I have left?" * "What plan am I on and when does it renew?" * "Show me my usage this month." **You get back:** Your credit balance and plan name, a daily usage breakdown, and your full subscription details (status, renewal date, tier). If your account is not connected to Stripe, you are told you are on the free tier and pointed to the upgrade flow. **Writes data?** No, read-only. **Behind the scenes:** first reads your account row (`get_iam_account_details`) to find your Stripe customer ID, then `get_my_balance`, `get_my_usage`, `get_my_subscription`. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.dapta.ai/dapta-mcp/skills/accounts.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.