Secure your environment and eliminate secrets sprawl by removing hard-coded credentials from your source code, config files and CI/CD systems. Learn More
Custom Pricing
Request a Quote"},{"seq":69,"quote":"\"SecretManager\": {\n \"secretManagerMonthlyOverageCost\": 20,\n \"secretManagerUserCost\": 2400\n }"}]}]},"run":"cmw3qd62q000d0ishtasfvhh8","completed":true,"usage":{"inputTokens":37939,"outputTokens":8314,"cacheReadInputTokens":430283,"cacheCreationInputTokens":0},"gaugeUrl":"https://agents.withgauge.com/p/runs/fc25cc66-7cc4-4f31-b0ab-efd2160072ed","transcript":"https://www.ax-check.com/keepersecurity.com/sessions/kimi.json"},{"id":"qwen","name":"Qwen 3.8 Max","short":"Qwen","language":"Python","duration":"2m 0s","http":0,"auth":0,"pricing":136,"pricingReview":"Quoted ~$3.75–4.50/user/month for Business, annual billing, and said the figures were unverified because the page renders them in JS. The figures came from memory and Secrets Manager got no number (seq 123, seq 129, seq 136)","analysis":{"status":"complete","onboarding":{"status":"login_required","detail":"Agent never obtained real Keeper Secrets Manager credentials. It installed the SDK and ran it against the SDK's own built-in mock (MockConfig/ResponseQueue), which generates fake tokens and fake encrypted responses entirely locally with no network calls to Keeper's hosted service. When run without a real KSM_CONFIG token, the actual example script exited immediately with a blocked message instructing the user to get a token from the Keeper Admin Console. No authenticated operation against the real hosted Keeper service was ever demonstrated.","evidence":[{"kind":"operation","seq":118,"quote":"Application can access 2 secret(s):\n - uid=0ee32efab29c41c4b506ca title=Prod DB\n login: ['admin']\n password: ['s3cret-prod']"},{"kind":"blocker","seq":118,"quote":"BLOCKED: no KSM_CONFIG env var.\nSet KSM_CONFIG to a base64 application config token from your\nKeeper Admin Console (Secrets Manager -> Add Application)."},{"kind":"credentials","seq":71,"quote":"config = MockConfig.make_config()"}]},"hallucinatedUrls":[],"blockers":[{"title":"No self-service way to get a Keeper Secrets Manager token","detail":"Calling the real hosted KSM service requires an application config token issued from the Keeper Admin Console, which requires human admin access. This is a normal credential/login requirement (not a product defect) and the agent correctly identified it rather than attempting workarounds that touch the live service.","evidence":[{"seq":118,"quote":"BLOCKED: no KSM_CONFIG env var.\nSet KSM_CONFIG to a base64 application config token from your\nKeeper Admin Console (Secrets Manager -> Add Application)."},{"seq":136,"quote":"actually calling the live service needs a real `KSM_CONFIG` token from your Keeper Admin Console (Secrets Manager → Add Application → copy one-time config token). I can't create that without your admin credentials"}]},{"title":"SDK v17 API differs from older examples/docs, causing repeated trial-and-error","detail":"The agent's first attempts used an older API shape (SecretsManager(configuration=...), record.fields, client.get_secret(uid)) that failed against the installed v17.3.0 SDK, requiring multiple rounds of introspection and fixes. This is an agent-side mismatch with stale assumptions rather than a live product failure, but it added friction and wasted turns.","evidence":[{"seq":35,"quote":"fails gracefully with bad token: TypeError SecretsManager.__init__() got an unexpected keyword argument 'configuration'"},{"seq":76,"quote":"AttributeError: 'Record' object has no attribute 'fields'. Did you mean: 'field'?"},{"seq":136,"quote":"the SDK API changed in v17 (`SecretsManager(token=...)`, fields live in `record.dict[\"fields\"]` / `get_standard_field_value()` rather than the old `.fields` attribute) — some docs/examples online still show the old signatures."}]},{"title":"Public pricing page renders figures via JavaScript, blocking scrape","detail":"Fetching the static pricing.html page returned only placeholder text with no dollar figures, since the numbers load client-side via JS; a plain curl could not extract them, forcing the agent to report rounded/approximate figures instead of exact pricing.","evidence":[{"seq":123,"quote":"- How much does Keeper charge? Keeper offers flexible, user-based pricing to meet the needs of businesses and enterprises: Keeper Business - Starts at per user per month, billed annually."},{"seq":136,"quote":"Keeper's public pricing page renders actual numbers via JavaScript, so I couldn't scrape exact figures"}]}],"suggestedChanges":[{"title":"Add a static/server-rendered pricing fallback on keepersecurity.com/pricing.html","detail":"The pricing page's dollar figures only populate via client-side JavaScript, so a plain HTTP fetch (curl) returns text with blank numeric fields. Render the per-user dollar amounts server-side (or in page HTML/meta) so simple fetch-based tools can read exact figures. Verify by curling the page and confirming the per-user price appears in the raw HTML/text, not just after JS execution.","evidence":[{"seq":123,"quote":"Keeper Business - Starts at per user per month, billed annually."}]},{"title":"Document the v17 keeper-secrets-manager-core API surface in the package/README","detail":"The installed SDK (v17.3.0) exposes SecretsManager(token=...) and record.dict['fields']/get_standard_field_value(), which differ from what the agent initially assumed (configuration= kwarg, record.fields attribute, get_secret() singular method). Add or update the PyPI package README / docstrings with the current v17 constructor signature and field-access pattern so first-time integrators do not hit AttributeError/TypeError on first try. Verify by having a fresh agent import the SDK and construct a client purely from the README instructions without errors.","evidence":[{"seq":35,"quote":"fails gracefully with bad token: TypeError SecretsManager.__init__() got an unexpected keyword argument 'configuration'"},{"seq":76,"quote":"AttributeError: 'Record' object has no attribute 'fields'. Did you mean: 'field'?"}]}]},"run":"cmw3qd62q000b0ishxyvahky6","completed":true,"usage":{"inputTokens":16148,"outputTokens":8979,"cacheReadInputTokens":236435,"cacheCreationInputTokens":0},"gaugeUrl":"https://agents.withgauge.com/p/runs/2ec9d421-7fb8-4630-a1e7-24f585defc51","transcript":"https://www.ax-check.com/keepersecurity.com/sessions/qwen.json"}]}