# AX Check: peec.ai Checked 2026-09-22. Docs and setup are clear, but Peec AI hides its prices. Quickstart and MCP/API docs are solid and actionable, but the pricing page shows only feature lists and plan names with no dollar figures for most tiers. ## Onboarding needs a login ## Coding sessions 2 of 3 coding sessions completed. Final output's pricing section contains only a feature table (prompts/models/projects per plan) with zero dollar/euro figures — it explicitly says 'exact figures render client-side, so treat these as… Final ### DeepSeek V4 Pro [View public run](https://agents.withgauge.com/p/runs/38ea7127-3967-487d-8bdb-aec70c6d21b2) · [Read transcript](https://www.ax-check.com/peec.ai/sessions/deepseek.json) #### End-to-end onboarding - **Onboarding needs a login**: The agent explored Peec AI's marketing site, docs, and OpenAPI spec but never obtained an API key. The docs explicitly state API access requires generating a key from a logged-in dashboard account, and is further gated to Enterprise customers. The agent tested the live API unauthenticated and got a 400 Missing API Key response, confirming the wall. No self-service signup or key-issuance flow was available to the agent within the sandbox, so it could not reach an authenticated operation. Event 25: ```text To use the API, you’ll need to generate an API key from your [Account](https://app.peec.ai/api-keys). This key is required for authenticating requests and securing access to your organization’s data. ``` Event 25: ```text Access to this API is currently limited to Enterprise customers. ``` Event 58: ```text {"message":"Missing API Key"} ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **API access requires a dashboard-issued key gated to Enterprise plans**: Peec AI's API docs state that generating an API key requires logging into the app dashboard, and that API access itself is restricted to Enterprise-tier customers. This is a product policy (not a test-environment or agent error): there is no self-serve signup-to-API-key path exposed to a first-time developer without a paid Enterprise account and a login session. Event 25: ```text To use the API, you’ll need to generate an API key from your [Account](https://app.peec.ai/api-keys). This key is required for authenticating requests and securing access to your organization’s data. ``` Event 25: ```text Access to this API is currently limited to Enterprise customers. ``` - **Unauthenticated API calls correctly rejected with 400**: The agent tried calling the live API without credentials to probe behavior; the API correctly returned a 400 with a clear error rather than any data, confirming there is no unauthenticated or trial pathway to exercise the API. Event 58: ```text {"message":"Missing API Key"} ``` #### Suggested Changes - **Publish real pricing figures in the server-rendered /pricing HTML**: Fetching /pricing via HTTP shows literal '$--' placeholders in the raw markup, while cached search-index content shows real numbers like $165/mo, $245/mo, $399/mo. Any developer or tool using curl instead of a full browser sees no usable pricing. Render actual price digits (or a JSON-LD block) server-side on /pricing and verify by curling the page and checking price digits appear. Event 63: ```text currency matches: ['$--', '$--', '$--', '$--', '$--'] ``` Event 76: ```text \b\d{2,3}(?:\.\d{1,2})?/mo\b => ['165/mo', '245/mo', '35/mo', '399/mo', '495/mo'] ``` - **Move the Enterprise-only API restriction to the top of the API intro doc**: docs.peec.ai/api/introduction describes the API as broadly available before a small Note reveals it is Enterprise-only. Move that restriction above the 'Getting Started' section so developers evaluating a lightweight integration learn immediately that a paid plan and login are required. Verify by confirming the restriction appears before any setup instructions on that page. Event 25: ```text Access to this API is currently limited to Enterprise customers. ``` Event 25: ```text To use the API, you’ll need to generate an API key from your [Account](https://app.peec.ai/api-keys). ``` ### Kimi K3 [View public run](https://agents.withgauge.com/p/runs/f10eb044-c23c-485d-a28f-499c50c80f31) · [Read transcript](https://www.ax-check.com/peec.ai/sessions/kimi.json) Final output's pricing section contains only a feature table (prompts/models/projects per plan) with zero dollar/euro figures — it explicitly says 'exact figures render client-side, so treat these as plan shapes,' even though the agent had actually scraped real numbers (€95/115/145/195/295/395/495, seq 63) and chose not to report any of them, so no cost figure was ever stated. #### End-to-end onboarding - **Onboarding needs a login**: The agent never obtained real Peec AI credentials. The Customer REST API is explicitly gated to Enterprise customers requiring a sales conversation, and the MCP server requires a Peec AI account with OAuth sign-in or a Personal Access Token generated from the dashboard, neither of which the agent could self-serve. The agent wrote an example script but never executed it against the live API since no API key or token existed. This is an unresolved credential block, not a recovered one. Event 30: ```text Access to this API is currently limited to Enterprise customers. ``` Event 78: ```text If you can supply either an Enterprise API key (`export PEEC_API_KEY=...`) or a Personal Access Token for the MCP server, the example runs as-is. ``` Event 76: ```text Python 3.12.3 syntax OK ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **Customer API locked behind Enterprise sales tier**: The Peec Customer API (api.peec.ai/customer/v1) is gated to Enterprise-plan customers per the docs, so no self-serve signup can produce an API key. This is a product/commercial packaging decision, not an agent error or test-environment limitation. Event 30: ```text Access to this API is currently limited to Enterprise customers. ``` - **MCP server requires an existing account and human OAuth/PAT step**: The MCP server route (api.peec.ai/mcp) needs a Peec AI account with a project plus either an OAuth browser sign-in or a Personal Access Token created manually in the dashboard at app.peec.ai/api-keys. The agent had no way to create an account or complete OAuth from the sandbox, so it could not obtain a token to call the live API. Event 49: ```text Personal Access Token. Create a token under **API Keys → Personal Access Tokens** in [app.peec.ai](https://app.peec.ai/api-keys), then attach it as an `Authorization: Bearer ` header on your client's MCP connection. ``` Event 78: ```text available to regular accounts, but still requires a Peec AI account with an active project, which I can't create from here (signup needs a real user, brand onboarding, and credentials). ``` - **Exact pricing figures not machine-readable**: Pricing page renders dollar amounts client-side (via JS), so curl-based scraping only pulled plan feature lists, not final prices. This is a test-environment/tooling limitation (no JS renderer available), not a product defect. Event 59: ```text Price reflects one additional model based on the prompts included in this plan. ``` Event 78: ```text exact figures render client-side, so treat these as plan shapes rather than exact quotes ``` #### Suggested Changes - **Add a note on the API introduction page clarifying no self-serve trial key exists**: On https://docs.peec.ai/api/introduction, the line 'Access to this API is currently limited to Enterprise customers' gives no path for a solo developer to test the API without contacting sales. Adding a sandbox/trial key option, or explicitly stating none exists with a contact-sales link, would save developers the time spent building an untestable example. Verify by having a non-Enterprise account attempt key generation and confirming the docs match the actual gate. Event 30: ```text Access to this API is currently limited to Enterprise customers. ``` - **Render pricing numbers in static HTML instead of client-side JS**: On https://peec.ai/pricing, plan prices are injected client-side, so a plain curl/GET only returns feature lists, not dollar or euro amounts. Serving prices in the initial HTML payload would let both crawlers and integrators fetch accurate pricing without a JS runtime. Verify by curling the page and checking that plan price values appear in the raw response body. Event 59: ```text Price reflects one additional model based on the prompts included in this plan. ``` ### Qwen 3.8 Max [View public run](https://agents.withgauge.com/p/runs/ae226b38-6d0f-40ff-b6ab-f67b1b42b4b5) · [Read transcript](https://www.ax-check.com/peec.ai/sessions/qwen.json) Final output lists concrete tiers (Starter/Pro/Advanced/Enterprise) with prompt/model/project limits and states pricing is usage-based on tracked prompts × models, sourced from the live pricing page (seq 53-56). #### End-to-end onboarding - **Onboarding needs a login**: The agent researched Peec AI's REST API and MCP server thoroughly, and built a working example client and demo script. However, the Customer API is gated to Enterprise-tier accounts, and API keys can only be generated by logging into app.peec.ai. The agent had no credentials in its environment and never obtained any — it explicitly tested with a bogus key (pk_test_not_real) against the live API and received 401 Invalid API Key, then stopped there. No self-service signup or credential-issuance flow was available or attempted; the session ends with the blocker unresolved. Event 33: ```text Access to this API is currently limited to Enterprise customers. ``` Event 104: ```text BLOCKED by the API: HTTP 401: Invalid API Key ``` Event 120: ```text The Customer API is Enterprise-only and I have no Peec API key in this environment.** Keys can only be created by logging into a paid account at `app.peec.ai/api-keys` — I can't self-serve one. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **Customer API requires an Enterprise-tier login-gated key**: Peec AI's docs state the Customer API is Enterprise-only, and keys are created only by signing into app.peec.ai/api-keys. This is a normal login/paid-tier requirement, not a product defect — the agent correctly identified it via docs and confirmed the live endpoint's auth behavior with a bogus key rather than fabricating success. Event 33: ```text Access to this API is currently limited to Enterprise customers. ``` Event 33: ```text you’ll need to generate an API key from your [Account](https://app.peec.ai/api-keys) ``` Event 104: ```text BLOCKED by the API: HTTP 401: Invalid API Key ``` #### Suggested Changes - **Add a self-service or trial API key path for non-Enterprise developers**: Currently the only way to evaluate the Customer API is to already be on Enterprise and log into app.peec.ai/api-keys. Consider offering a limited/sandbox key for Starter/Pro tiers or a trial API key so developers can validate integration code before committing to Enterprise. Check by having a Pro-tier test account attempt to generate a key at app.peec.ai/api-keys and confirm it succeeds without a sales conversation. Event 33: ```text Access to this API is currently limited to Enterprise customers. ``` ### Task given to each agent Help me build a simple example using Peec AI. Tell me how pricing works, and briefly tell me whether this product will be easy for you to manage. Let me know if you get blocked. If this product has no developer workflow you can act on, say so plainly and stop. Stay light: use the hosted product through its SDK or API. Do not start local service stacks or wait for long-running commands; if the quickstart requires either, say so plainly and stop. No product credentials were supplied and no purchases were authorized. ## Score: B · 68/100 (provisional) Grades come from completed site checks. Coding sessions and skipped checks do not affect the score. ### Clarity - **Failed** — llms.txt provides an actionable documentation index ```text https://peec.ai/llms.txt returned HTTP 404, so no documentation index exists at the standard path. ``` - **Pass** — Homepage answers Markdown requests ```text Homepage returned text/markdown (995 tokens) when requested with Accept: text/markdown. ``` - **Skipped** — llms.txt provides navigation guidance ```text llms.txt is 404, so no navigation guidance content exists to assess. ``` - **Skipped** — llms.txt mentions offered API, MCP, and skills ```text llms.txt is 404, so no API/MCP/skills mentions exist to assess. ``` - **Pass** — A compact guide representation exists ```text Homepage returns text/markdown (995 tokens) and docs pages serve .md representations. ``` - **Pass** — A focused guide is directly retrievable ```text Quickstart guide fetched as Markdown with concrete setup steps and tasks. ``` - **Pass** — Equivalent instructions fit a token budget ```text Markdown quickstart is 2160 tokens, well under the 8000-token budget. ``` - **Pass** — Product-docs links survive format changes ```text Homepage Markdown retains Docs, Pricing, MCP and product links. ``` - **Pass** — The compact guide is independently actionable ```text Quickstart gives concrete steps: add 10 prompts, 3-4 competitors, review dashboard and sources. ``` - **Pass** — Install and next-step links resolve ```text Fetched install/next-step links (docs quickstart, MCP setup, app signup) all returned 200. ``` ### Onboarding - **Pass** — Docs lead to a relevant quickstart ```text Docs quickstart guide gives concrete steps: add prompts, competitors, review dashboard and sources. ``` - **Skipped** — Installation commands are extractable ```text Quickstart is a UI walkthrough; no installation commands for a CLI or SDK are offered. ``` - **Skipped** — Code examples are available without interaction ```text Quickstart shows no code examples; it is a product UI walkthrough with videos. ``` - **Skipped** — Prerequisites and auth boundaries are explicit ```text Quickstart covers in-app setup but states no auth boundaries or API key prerequisites. ``` ### Pricing - **Failed** — Pricing is readable without interaction ```text Pricing page lists plan names and feature lists but no dollar figures; prices are not readable. ``` - **Failed** — Prices are stated, not gated ```text Only Enterprise shows 'Custom'; Starter, Pro and Advanced show no stated prices. ``` - **Failed** — Pricing units and limits are explicit ```text Pricing page lists feature names but no explicit units, quotas or per-plan limits. ``` - **Failed** — Agents identify pricing and its assumptions ```text 2 of 3 sessions were judged on pricing; 1 fell short. Kimi K3: Final output's pricing section contains only a feature table (prompts/models/projects per plan) with zero dollar/euro figures — it explicitly says 'exact figures render client-side, so treat these as plan shapes,' even though the agent had actually scraped real numbers (€95/115/145/195/295/395/495, seq 63) and chose not to report any of them, so no cost figure was ever stated. Qwen 3.8 Max: Final output lists concrete tiers (Starter/Pro/Advanced/Enterprise) with prompt/model/project limits and states pricing is usage-based on tracked prompts × models, sourced from the live pricing page (seq 53-56). This behavioural item does not affect the fast grade. ``` ### Activation - **Pass** — An API reference or OpenAPI spec is reachable ```text Customer API introduction and authentication docs fetched; API key required, JSON endpoints documented. ``` - **Pass** — An MCP server is documented and well-formed ```text MCP docs give server URL https://api.peec.ai/mcp, Streamable HTTP transport, OAuth/PAT auth. ``` - **Skipped** — A CLI install path is documented ```text No CLI install path documented in fetched pages; only MCP and API offered. ``` - **Skipped** — SDK packages resolve on their registries ```text No SDK or package registry evidence supplied for any Peec AI developer package. ``` - **Skipped** — Agent skills are published ```text No agent skills published; MCP prompts mentioned but no skills surface fetched. ``` [Full report data](https://www.ax-check.com/peec.ai/report.json)