# AX Check: attio.com Checked 2026-09-19. Attio's docs and pricing are clear, machine-readable, and quick to find. Pricing lists exact per-seat costs for Free, Plus, Pro and Enterprise with limits spelled out; a compact guide indexes docs, API, MCP and pricing in one place. ## Onboarding needs a login ## Coding sessions All three independent sessions (DeepSeek V4 Pro, Kimi K3, Qwen 3.8 Max) completed successfully, each producing a full pricing table for Free, Plus, Pro and Enterprise plans sourced directly from attio.com/pricing with clear per-seat, monthly/annual and limit assumptions noted. ### DeepSeek V4 Pro [View public run](https://agents.withgauge.com/p/runs/37125cbb-2bdf-4264-a7d1-7095f3df83ef) · [Read transcript](https://www.ax-check.com/attio.com/sessions/deepseek.json) Final output gives a full pricing table (Free/Plus/Pro/Enterprise) sourced from attio.com/pricing with explicit assumptions (per-user/month, annual discount, seat/record/credit limits) and flags an unresolved caveat about Free-tier API access. #### End-to-end onboarding - **Onboarding needs a login**: The agent never obtained a real Attio API key or account during the session. It searched the sandbox environment for existing credentials, found none, and confirmed via the docs that a workspace API key must be manually generated by a human in the Attio UI. It then wrote a working script and validated its request-handling logic only against a syntactically-valid but fake 64-character key, which correctly received a 401 from the live API. No authenticated write or read against real workspace data ever occurred. Event 6: ```text PI_GATEWAY_API_KEY= GIT_CONFIG_KEY_0= ``` Event 111: ```text "message": "The API Key provided could not be found. This is most commonly caused by the token having been revoked." ``` Event 130: ```text I'm blocked on **credentials**: making real authenticated calls requires an API key generated in your Attio workspace (Settings → developer/API keys → create key). I can't create an account or mint that key for you. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No self-service way to get an Attio API key**: Attio's REST API requires a workspace API key created by a human via the account's admin/developer settings UI; there is no signup or key-issuance flow the agent could complete on its own. This is normal product behavior (expected authentication gate), not a defect, but it fully prevented any authenticated call in this session. Event 41: ```text If you only need a token for a single workspace, you can generate an API key in the developer settings page of your apps. ``` Event 130: ```text I'm blocked on **credentials**: making real authenticated calls requires an API key generated in your Attio workspace (Settings → developer/API keys → create key). ``` #### Suggested Changes - **Clarify which pricing tiers include API/webhook access**: The scraped attio.com/pricing feature comparison lists 'API and webhook access' and 'App SDK' as line items in the plan table, but the agent could not determine from the static text which tiers actually gate these features. Check the rendered pricing page comparison table (the feature-by-tier grid) to confirm whether the Free tier includes API access, and make the tier-gating explicit in adjacent text rather than only in a visual table. Event 130: ```text One caveat I couldn't fully resolve from the static page: the comparison table lists "API and webhook access" and "App SDK" as features, but I couldn't read which tiers gate them ``` ### Kimi K3 [View public run](https://agents.withgauge.com/p/runs/6160767c-3dc6-4de3-b5b4-018845ea0b1b) · [Read transcript](https://www.ax-check.com/attio.com/sessions/kimi.json) Final output gives Free/Plus/Pro/Enterprise prices with explicit assumptions (seat counts, annual vs monthly billing, region conversions) sourced from attio.com/pricing (seq 13/22/31). #### End-to-end onboarding - **Onboarding needs a login**: The agent never obtained a real Attio API key. It explicitly stated it could not create an Attio workspace itself because signup requires human Google/email auth, and it only tested the script against a syntactically-valid but fake 64-character placeholder token, which the live API correctly rejected as invalid/revoked. No authenticated write or read operation against real workspace data was ever demonstrated. Event 159: ```text **Blocked on:** one thing only — a real API key. I can't create an Attio workspace myself (signup requires human Google/email auth). ``` Event 153: ```text ✗ API key is invalid or revoked. exit=1 ``` Event 135: ```text FAKE=$(printf 'a%.0s' {1..64}); curl -s --max-time 10 -H "Authorization: Bearer $FAKE" https://api.attio.com/v2/self | head -c 300 ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No self-service way to create an Attio workspace/API key**: Attio requires a human to sign up for a workspace (Google/email auth) and manually generate an API key via the workspace settings UI before any authenticated API call can succeed. This is a normal login/signup requirement, not a product defect, and it stopped the agent from running its script against live data. Event 159: ```text I can't create an Attio workspace myself (signup requires human Google/email auth). To finish the demo: create a free workspace at attio.com, generate a key (Workspace settings → Apps; scopes `record_permission:read-write`, `object_configuration:read`) ``` #### Suggested Changes - **Return a distinct error code from GET /v2/self for malformed tokens**: Currently /v2/self returns HTTP 400 with a 'Token was not recognised' message for a missing/malformed Authorization header, but returns 200 with {"active": false} for a well-formed but invalid 64-char key, and 401 elsewhere for wrong-length keys. This inconsistency forced the agent to special-case the /self response shape. Standardize the auth-failure status codes/response shape across /v2/self and other endpoints; verify by re-running the same fake-token requests shown in this session (GET /v2/self, POST /v2/objects/people/records/query) and confirming consistent status codes. Event 131: ```text {"status_code":400,"type":"invalid_request_error","code":"missing_value","message":"Token was not recognised, either make a form-encoded request with a token= parameter, or include it in the Authorization bearer header"} {"status_code":401,"type":"auth_error","code":"unauthorized","message":"The API Key provided was invalid because it was the wrong length (API Keys should be 64 characters long). You might not have copied the entire API key from your Admin panel?"} ``` Event 137: ```text {"active":false} ✓ Token OK: undefined ``` ### Qwen 3.8 Max [View public run](https://agents.withgauge.com/p/runs/0fc7b08a-ee5d-40fd-8915-ed4b99f385dd) · [Read transcript](https://www.ax-check.com/attio.com/sessions/qwen.json) Final output gives a pricing table (Free/Plus $44-35/Pro $99-79/Enterprise) sourced from attio.com/pricing with explicit assumptions noted: per-seat/month, ~20% annual discount, seat-credit tiers, and no separate API charge. #### End-to-end onboarding - **Onboarding needs a login**: The agent never obtained real Attio credentials. It only had a placeholder env var (PI_GATEWAY_API_KEY=unused) and no ATTIO_API_KEY. It tested the live API with no token and then a fabricated 64-char dummy string, both of which correctly returned 401 unauthorized. The final message explicitly states it is blocked on credentials and asks the product owner to supply a real API token, so no authenticated operation against the hosted product was ever demonstrated. Event 67: ```text curl -s --max-time 15 -w "\nHTTP %{http_code}\n" https://api.attio.com/v2/objects; curl -s --max-time 15 -w "\nHTTP %{http_code}\n" -H "Authorization: Bearer fake" https://api.attio.com/v2/objects | head -5 ``` Event 77: ```text Attio API error 401: {'status_code': 401, 'type': 'auth_error', 'code': 'unauthorized', 'message': 'The API Key provided was invalid because it contained invalid characters. Double check that you are using the API key from your Attio Admin panel and not another value.'} ``` Event 84: ```text The caveat: **I'm currently blocked on credentials** — I have no `ATTIO_API_KEY` in this environment, so I couldn't run the example end-to-end against a real workspace. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No Attio API key available in the sandbox**: The environment only exposed an unrelated PI_GATEWAY_API_KEY; there was no ATTIO_API_KEY or any mechanism to self-provision one. This is a test-environment/credential limitation, not a product defect — creating an Attio API token is a normal authenticated action inside the Attio dashboard that requires a human to sign up and generate it. The agent correctly identified this and stopped rather than faking success. Event 69: ```text {"status_code":401,"type":"auth_error","code":"unauthorized","message":"The Authorization header was not provided. Double check that you are including the header and that there is not a typo in the name."} ``` Event 84: ```text I have no `ATTIO_API_KEY` in this environment, so I couldn't run the example end-to-end against a real workspace. Give me a 64-char API token (Settings → Developer → API access in your Attio workspace) and I can run and iterate on it immediately. ``` - **Official npm SDK package does not exist**: The agent tried installing an official-sounding npm package before discovering only a third-party PyPI client exists; this cost a couple of quick lookups but was resolved immediately without blocking further progress. Event 6: ```text npm error code E404 npm error 404 Not Found - GET https://registry.npmjs.org/@attio%2fsdk - Not found npm error 404 ``` #### Suggested Changes - **Publish or link an official Python/JS SDK from the developer docs**: The agent found only a third-party generated client (elviskahoro/attio-sdk-python) on PyPI; there is no official @attio/sdk on npm. On developers.attio.com/reference/quickstart, add a direct link to an official SDK package (or explicitly state 'community-maintained' next to any third-party client) so agents and developers don't have to guess which package is authoritative. Verify by checking that `pip install ` or `npm install @attio/` resolves to an Attio-maintained package. Event 6: ```text pip index versions attio 2>&1 | head -3 ``` Event 15: ```text Attio API client library from elviskahoro {'homepage': 'https://github.com/elviskahoro/attio-sdk-python'} ``` - **Add a copy-pasteable curl/API-key quickstart snippet on the quickstart page**: The rendered quickstart page (developers.attio.com/reference/quickstart) returned only high-level marketing copy about the four platform pillars (App SDK, REST API, MCP, SQL) with no immediate code sample or 'create your first API key' snippet. Add a short 'Get an API key and make your first call' code block directly on that page so a first-time developer does not need to cross-reference the authentication and create-a-record pages separately. Verify by loading the quickstart page and confirming a runnable curl/Python snippet with the api.attio.com base URL appears above the fold. Event 21: ```text Attio is a revolutionary CRM platform which is highly customisable, incredibly powerful and data-driven. In these guides, you can find everything you need to build powerful integrations, automations and data pipelines on top of Attio. ``` ### Task given to each agent Help me build a simple example using Attio. 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 · 84/100 (provisional) Grades come from completed site checks. Coding sessions and skipped checks do not affect the score. ### Clarity - **Failed** — Homepage answers Markdown requests ```text Homepage returned text/html for a text/markdown request; no Markdown representation served. ``` - **Pass** — llms.txt provides an actionable documentation index ```text llms.txt links docs, API, OpenAPI, SDK, MCP, help center and pricing with organized sections. ``` - **Pass** — llms.txt provides navigation guidance ```text llms.txt groups content under Product, Help Center, Resources, Developer Platform and Pricing headings. ``` - **Pass** — llms.txt mentions offered API, MCP, and skills ```text llms.txt links REST API, OpenAPI spec, App SDK and hosted MCP server with connection guidance. ``` - **Pass** — A compact guide representation exists ```text llms.txt is a compact Markdown guide covering product, developer platform, MCP, pricing and onboarding. ``` - **Pass** — A focused guide is directly retrievable ```text llms.txt fetched directly at attio.com/llms.txt with 200 and full Markdown body. ``` - **Pass** — Equivalent instructions fit a token budget ```text llms.txt is 2142 tokens, well under the 8000-token budget. ``` - **Skipped** — Product-docs links survive format changes ```text Homepage Markdown unsupported, so link preservation across formats cannot be measured. ``` - **Pass** — The compact guide is independently actionable ```text llms.txt gives concrete onboarding steps, MCP connect instructions, and developer docs links. ``` - **Pass** — Install and next-step links resolve ```text Fetched docs, MCP, OpenAPI and developer pages all returned HTTP 200. ``` ### Onboarding - **Pass** — Docs lead to a relevant quickstart ```text llms.txt links Developer Docs Overview, REST API Overview, App SDK Intro and MCP overview for builders. ``` - **Skipped** — Installation commands are extractable ```text No installation or CLI command page was fetched; only llms.txt index is available. ``` - **Skipped** — Code examples are available without interaction ```text No docs page with code examples was fetched; llms.txt only links to them. ``` - **Pass** — Prerequisites and auth boundaries are explicit ```text llms.txt states REST API uses OAuth and MCP authenticates via OAuth 2.0, no API keys. ``` ### Pricing - **Pass** — Pricing is readable without interaction ```text Pricing page renders plan cards and full comparison table as static HTML, no interaction needed. ``` - **Pass** — Prices are stated, not gated ```text Free $0, Plus $44/$35, Pro $99/$79 per user/month stated; Enterprise custom quote. ``` - **Pass** — Pricing units and limits are explicit ```text Seats, objects, records, credits, email limits and storage stated per plan. ``` - **Pass** — Agents identify pricing and its assumptions ```text 3 of 3 sessions were judged on pricing; 0 fell short. DeepSeek V4 Pro: Final output gives a full pricing table (Free/Plus/Pro/Enterprise) sourced from attio.com/pricing with explicit assumptions (per-user/month, annual discount, seat/record/credit limits) and flags an unresolved caveat about Free-tier API access. Kimi K3: Final output gives Free/Plus/Pro/Enterprise prices with explicit assumptions (seat counts, annual vs monthly billing, region conversions) sourced from attio.com/pricing (seq 13/22/31). Qwen 3.8 Max: Final output gives a pricing table (Free/Plus $44-35/Pro $99-79/Enterprise) sourced from attio.com/pricing with explicit assumptions noted: per-seat/month, ~20% annual discount, seat-credit tiers, and no separate API charge. This behavioural item does not affect the fast grade. ``` ### Activation - **Pass** — An API reference or OpenAPI spec is reachable ```text REST API overview and a public OpenAPI 3.1 spec at api.attio.com/openapi/api are both reachable. ``` - **Pass** — An MCP server is documented and well-formed ```text Hosted MCP server at mcp.attio.com/mcp documented with OAuth setup and full tool list. ``` - **Skipped** — A CLI install path is documented ```text No CLI install path is documented in the fetched Attio developer pages. ``` - **Skipped** — SDK packages resolve on their registries ```text No Attio SDK package registry lookup result was supplied in the evidence. ``` - **Skipped** — Agent skills are published ```text No agent skills are published or referenced in the fetched Attio documents. ``` [Full report data](https://www.ax-check.com/attio.com/report.json)