Update to Pimlico

{
  "description": "Answer questions about a Pimlico account and change its API keys and gas sponsorship policies with the Pimlico tools — balance and invoices, usage, failed user operations, API keys, sponsorship policies, supported chains and ERC-20 paymaster tokens.",
  "included_files": [],
  "name": "get-started",
  "skill_md_contents": "---\nname: get-started\ndescription: Answer questions about a Pimlico account and change its API keys and gas sponsorship policies with the Pimlico tools — balance and invoices, usage, failed user operations, API keys, sponsorship policies, supported chains and ERC-20 paymaster tokens.\n---\n\n# Pimlico account\n\nPimlico is infrastructure for smart accounts (ERC-4337 and EIP-7702): a bundler, a paymaster that sponsors gas, and the same on Solana. These tools read and change the settings of the Pimlico account the user connected. They do not sign transactions, move funds or send tokens.\n\n## Which tool answers what\n\n| Question | Tools |\n| --- | --- |\n| Which account and organization is connected | `pimlico_whoami` |\n| Balance, unbilled usage, invoices | `pimlico_balance`, `pimlico_invoices` |\n| Requests, API credits and sponsored gas over a period, by chain, key or day | `pimlico_usage` |\n| Why a user operation failed | `pimlico_op` for one hash, `pimlico_ops` for recent operations |\n| Operations rejected before they reached the chain | `pimlico_requests` (failed `eth_sendUserOperation` and `pm_*` calls) |\n| Solana transactions | `pimlico_solana_txs` |\n| API keys | `pimlico_keys_list`, `pimlico_keys_get`, `pimlico_keys_create`, `pimlico_keys_rename`, `pimlico_keys_disable` |\n| Sponsorship policies | `pimlico_policies_list`, `pimlico_policies_get`, `pimlico_policies_create`, `pimlico_policies_update`, `pimlico_policies_enable`, `pimlico_policies_disable` |\n| Supported chains and ERC-20 paymaster tokens | `pimlico_chains`, `pimlico_erc20_tokens` |\n\n## Facts that shape the answers\n\n- Chains are identified by chain ID. `pimlico_chains` maps names such as \"Base Sepolia\" to IDs (84532).\n- A new API key's secret appears only once, in the result of `pimlico_keys_create`. Existing secrets are never returned.\n- Policy caps are in USD, not in the chain's native token.\n- Disabling keys or policies and reading billing require the organization admin role; other members get a FORBIDDEN error.\n- Usage figures come from hourly aggregates and lag by one to two hours.\n- If `warnings` in a result is non-empty, the account has open invoices.\n\n## Example requests\n\n- \"Why did my user operations on Base Sepolia fail in the last 24 hours?\"\n- \"Create a sponsorship policy on Base Sepolia with a $20 total budget.\"\n- \"What is my balance, and do I have unpaid invoices?\"\n"
}