# AX Check: allium.com
Checked 2026-10-15.

No docs or quickstart exist for agents to find on allium.com
The homepage loads but has no documentation index, no quickstart, and no pricing page; 20 of 23 checklist items were unassessed for lack of content.

## Onboarding needs a login

## Coding sessions
All three sessions completed and reported per-call pricing of $0.01 to $0.03 in USDC with no subscription, citing docs and a live quote, though none found a published subscription rate.

### DeepSeek V4.1 Flash
[View public run](https://agents.withgauge.com/p/runs/a22e7f17-f9af-4c47-a20e-695441e28705) · [Read transcript](https://www.ax-check.com/allium.com/sessions/deepseek.json)
Quoted per-call USDC prices of $0.01–$0.03 from the docs, with the basis: machine-payments path, no subscription, rate limits, payment networks. Enterprise plans are contact-sales only. (seq 45, seq 35, seq 86)
#### End-to-end onboarding
- **Onboarding needs a login**: The agent only reached the free, unauthenticated discovery endpoint and a documented 402 payment-required response. It never obtained or used real credentials (API key or funded USDC wallet) to complete an authenticated operation. It explicitly wrote paid_tempo.py (the real paid path) but did not execute it, stating no funded wallet or private key was available in the sandbox environment.
  Event 62:

  ```text
  env | grep -iE 'allium|private|wallet|usdc|tempo|x402' | sed 's/=.*/=<redacted>/' || echo 'none'
  ```
  Event 53:

  ```text
  HTTP/2 402 
  date: Thu, 15 Oct 2026 16:54:38 GMT
  content-type: application/json
  server: cloudflare
  www-authenticate: Payment id=
  ```
  Event 86:

  ```text
  I **cannot execute an actual paid data call** — that requires a USDC-funded wallet / `YOUR_PRIVATE_KEY`, and none is present in this environment (`env` has no Allium key or wallet secret). So `paid_tempo.py` is written from the official quickstart but unexecuted.
  ```

#### Hallucinated URLs
None identified in this transcript.

#### Blockers
- **No funded USDC wallet or API key available to complete a paid call**: Allium's developer data endpoints require either a funded USDC wallet (for machine payments via Tempo MPP/x402) or an API key for keyed Explorer endpoints. Neither credential type exists in the sandbox environment, so the agent could only trigger the documented 402 Payment Required handshake and could not fetch real data. This is a missing-credentials limitation of the test environment, not a product defect — the product's machine-payments design intentionally requires a wallet.
  Event 53:

  ```text
  HTTP/2 402 
  date: Thu, 15 Oct 2026 16:54:38 GMT
  content-type: application/json
  server: cloudflare
  www-authenticate: Payment id="l7I_lzy2MilUZZ4fxop8lu0TJ-IZDCXERl4b4Zrl8fs"
  ```
  Event 86:

  ```text
  To get live data, provide a funded wallet (or an `X-API-KEY` for the keyed endpoints), and I can run it immediately.
  ```
- **Default urllib request blocked by Cloudflare (403)**: The first run of the example script failed with HTTP 403 Forbidden on the free discovery endpoint because the default Python urllib User-Agent was rejected by Cloudflare. This was an agent-side implementation detail, not a product outage — the agent fixed it by adding a custom User-Agent header and the request succeeded on retry.
  Event 72:

  ```text
  urllib.error.HTTPError: HTTP Error 403: Forbidden
  ```
  Event 79:

  ```text
  prices endpoint supports 13 chains
  ```

#### Suggested Changes
- **Reconcile testnet vs mainnet USDC addresses in the Tempo MPP quickstart**: The Tempo MPP code sample at docs.allium.so/ai/machine-payments/tempo-mpp imports TESTNET_RPC_URL and TESTNET_CHAIN_ID, while the Endpoints & Pricing page lists a Tempo mainnet USDC contract address. Align the quickstart sample with the pricing/network table (or add a note on when to switch from testnet to mainnet) so developers don't have to reconcile the discrepancy themselves before going live.
  Event 60:

  ```text
  from mpp.methods.tempo._defaults import TESTNET_RPC_URL, TESTNET_CHAIN_ID
  ```
  Event 46:

  ```text
  | **Tempo MPP** | Tempo (mainnet) | `0x20c000000000000000000000b9537d11c60e8b50` |
  ```
- **Point the public /pricing URL to an actual price list**: https://www.allium.so/pricing resolves to a 'Contact Allium' sales page rather than any self-serve pricing information, forcing developers to dig through docs.allium.so/ai/machine-payments/endpoints-pricing for the only concrete price list (which only covers machine-payments, not the core Explorer/Datashares plans). Add a basic self-serve pricing summary or a direct link to the machine-payments pricing table from the main /pricing page.
  Event 35:

  ```text
  <title>Contact Allium | Enterprise Blockchain Data</title>
  ```

### Kimi K3
[View public run](https://agents.withgauge.com/p/runs/4c762c53-d01c-46df-9ad2-4db817873c3a) · [Read transcript](https://www.ax-check.com/allium.com/sessions/kimi.json)
Quoted per-call prices from the docs ($0.01–$0.03) and tied them to the pay-per-call USDC model with no subscription. It also said subscription plan prices aren't published. (seq 33, seq 57)
#### End-to-end onboarding
- **Onboarding needs a login**: No Allium API key was present in the sandbox environment, and obtaining one requires a human to sign up at app.allium.so and generate a key from Settings > API Keys (one key per user, per docs). The agent never obtained real credentials, so it could not exercise any authenticated operation. It only confirmed the endpoint enforces auth by sending an unauthenticated request and observing a 403.
  Event 4:

  ```text
  env | grep -iE "allium|api_key|token"
  ```
  Event 55:

  ```text
  BLOCKED: ALLIUM_API_KEY is not set.
  ```
  Event 57:

  ```text
  there's no `ALLIUM_API_KEY` in this environment, and creating one requires a human to register at https://app.allium.so/join (Settings → API Keys → Generate; one key per user)
  ```

#### Hallucinated URLs
None identified in this transcript.

#### Blockers
- **No API key available, blocking authenticated calls**: The sandbox had no ALLIUM_API_KEY, and the documented path to get one (register at app.allium.so/join, then generate a key in Settings > API Keys) requires human action. This is a missing-credentials limitation of the test environment, not a product defect: Allium's auth design (one key per user, human-gated signup) is standard practice. The agent correctly identified this and stopped rather than inventing a fake key or attempting the separate machine-payments (USDC wallet) path.
  Event 55:

  ```text
  BLOCKED: ALLIUM_API_KEY is not set.
  ```
  Event 57:

  ```text
  I did not attempt the machine-payments path since that would mean spending USDC from a wallet I don't have.
  ```

#### Suggested Changes
- **Publish concrete subscription plan pricing in the billing docs**: The usage-and-billing doc page explains overage behavior (uncapped/capped/blocked) but lists no actual dollar figures for subscription tiers, only directing users to Settings > Billing or sales. Add representative plan pricing (or a pricing page link) to docs.allium.so/app/organization-management/usage-and-billing so a first-time evaluator can estimate cost without signing up or contacting sales. Check by confirming the page lists at least one concrete price tier.
  Event 33:

  ```text
  Overage settings only applies to Explorer Units at the moment. Manage your access and costs by selecting your preferred option
  ```

### Qwen 3.8 Max
[View public run](https://agents.withgauge.com/p/runs/32a1fb6e-ea56-499b-a55f-b39b2cb99a00) · [Read transcript](https://www.ax-check.com/allium.com/sessions/qwen.json)
Quoted $0.02 per prices call from the live 402 quote and the docs. Named the assumptions: cost per endpoint and per batch input, no published USD rate for Developer Units, a limited free tier, and sales-led plans. (seq 47, seq 48, seq 65, seq 109)
#### End-to-end onboarding
- **Onboarding needs a login**: Agent called the one free, unauthenticated endpoint (supported-chains) successfully, but never obtained real API credentials. Getting-started docs require account creation via business email (human signup) for an API key, and the keyless machine-payments path needs a funded crypto wallet. Agent refused to generate/fund a wallet and built scripts that exit with instructions when credentials are missing. No authenticated paid operation was completed.
  Event 24:

  ```text
  https://docs.allium.so/api -> 200 https://docs.allium.so/login?redirect=%2Fapi
  ```
  Event 93:

  ```text
  Free endpoint, no auth: 23 realtime endpoints, 22 distinct chains
  ```
  Event 93:

  ```text
  blocked: ALLIUM_API_KEY is not set.
    1. create an account at https://app.allium.so/join
    2. Settings -> API Keys -> Generate
    3. export ALLIUM_API_KEY=...
  Or skip signup entirely and pay per call in USDC:
    export ALLIUM_PRIVATE_KEY=... && python3 example_machine_payments.py
  ```
  Event 47:

  ```text
  HTTP/2 402 
  date: Thu, 15 Oct 2026 16:54:49 GMT
  ```

#### Hallucinated URLs
None identified in this transcript.

#### Blockers
- **No self-service way to obtain an API key**: Allium's getting-started docs require creating an account at app.allium.so/join with a business email, a human-gated signup flow with no programmatic path. This is normal product behavior (standard account-gated auth), not a defect, but it stopped the agent from completing any authenticated Developer API call.
  Event 93:

  ```text
  blocked: ALLIUM_API_KEY is not set.
    1. create an account at https://app.allium.so/join
    2. Settings -> API Keys -> Generate
    3. export ALLIUM_API_KEY=...
  ```
- **Keyless machine-payments path requires real funded crypto wallet**: The alternative no-signup path (x402/Tempo MPP) works without an API key but needs a wallet funded with real USDC on mainnet. The agent correctly declined to spend real funds unilaterally, so this path also remained blocked by design/caution rather than by a product or test-environment fault.
  Event 47:

  ```text
  www-authenticate: Payment id="CXDChm_mBo1cmhHKBpPQI2uZfhSV7zF4QQ3ouxTQfNg", realm="agents.allium.so", method="tempo", intent="charge"
  ```
  Event 109:

  ```text
  the keyless path spends **real USDC on mainnet**, which I won't do unilaterally
  ```
- **Cloudflare blocked default HTTP client signature, looked like an auth error**: Agent error / edge-WAF behavior: the first call to agents.allium.so with Python's default urllib User-Agent returned a confusing Cloudflare 403 (browser_signature_banned) that initially resembled an authentication failure rather than a bot-detection block. The agent diagnosed and fixed this itself by setting an explicit User-Agent header.
  Event 84:

  ```text
  error: HTTP 403 from https://agents.allium.so/api/v1/supported-chains/realtime-apis/simple: {"type":"https://developers.cloudflare.com/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1010/","title":"Error 1010: Access denied"
  ```

#### Suggested Changes
- **Publish a public pricing page instead of redirecting to contact form**: Both allium.so/pricing and the bare apex path currently 200-redirect to /contact rather than showing any pricing information. Add a real pricing page (even tiered/indicative) so evaluators don't have to reverse-engineer costs from scattered docs pages. Verify by curling allium.so/pricing and confirming it returns pricing content instead of a contact form.
  Event 24:

  ```text
  https://www.allium.so/pricing -> 200 https://www.allium.so/contact
  ```
- **Document Cloudflare User-Agent filtering on agents.allium.so**: agents.allium.so's Cloudflare WAF rejects default HTTP client User-Agent strings with a 403 'browser_signature_banned' error easily mistaken for an auth failure. Add a note in the machine-payments or Endpoints & Pricing docs warning that non-browser HTTP clients need a custom User-Agent header, and verify by making a raw request with a default UA and confirming the documented workaround resolves it.
  Event 84:

  ```text
  error_name":"browser_signature_banned","error_category":"access_denied
  ```

### Task given to each agent
Help me build a simple example using Allium. 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: F · 0/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 even when Markdown was requested; no Markdown representation offered.
  ```

- **Failed** — llms.txt provides an actionable documentation index

  ```text
  /llms.txt returns 404; no documentation index exists for agents.
  ```

- **Skipped** — llms.txt provides navigation guidance

  ```text
  No llms.txt body exists (404), so navigation guidance cannot be assessed.
  ```

- **Skipped** — llms.txt mentions offered API, MCP, and skills

  ```text
  No llms.txt body exists (404); no API, MCP or skills surfaces are offered.
  ```

- **Skipped** — A compact guide representation exists

  ```text
  No compact guide or Markdown representation was fetched; only HTML homepage and a 404 page.
  ```

- **Skipped** — A focused guide is directly retrievable

  ```text
  No focused guide page was fetched; only homepage and 404 error page available.
  ```

- **Skipped** — Equivalent instructions fit a token budget

  ```text
  No compact guide representation was retrieved, so token budget cannot be judged.
  ```

- **Skipped** — Product-docs links survive format changes

  ```text
  Homepage Markdown unsupported, so link preservation across formats is unassessed.
  ```

- **Skipped** — The compact guide is independently actionable

  ```text
  No compact agent guide or Markdown docs page was fetched for this manufacturer site.
  ```

- **Skipped** — Install and next-step links resolve

  ```text
  No install or next-step links were sampled; only homepage navigation was fetched.
  ```


### Onboarding
- **Skipped** — Docs lead to a relevant quickstart

  ```text
  Only a 404 page was fetched; no docs or quickstart content is available.
  ```

- **Skipped** — Installation commands are extractable

  ```text
  No installation or setup page was fetched for this aluminum railing manufacturer.
  ```

- **Skipped** — Code examples are available without interaction

  ```text
  No documentation or code example pages were fetched.
  ```

- **Skipped** — Prerequisites and auth boundaries are explicit

  ```text
  No docs page with prerequisites or auth boundaries was fetched.
  ```


### Pricing
- **Skipped** — Pricing is readable without interaction

  ```text
  No pricing page was fetched; homepage shows only products and a dealer locator.
  ```

- **Skipped** — Prices are stated, not gated

  ```text
  No pricing page was fetched; no prices appear on the homepage.
  ```

- **Skipped** — Pricing units and limits are explicit

  ```text
  No pricing page was fetched, so units and limits cannot be judged.
  ```

- **Pass** — Agents identify pricing and its assumptions

  ```text
  3 of 3 sessions were judged on pricing; 0 fell short. DeepSeek V4.1 Flash: Quoted per-call USDC prices of $0.01–$0.03 from the docs, with the basis: machine-payments path, no subscription, rate limits, payment networks. Enterprise plans are contact-sales only. (seq 45, seq 35, seq 86) Kimi K3: Quoted per-call prices from the docs ($0.01–$0.03) and tied them to the pay-per-call USDC model with no subscription. It also said subscription plan prices aren't published. (seq 33, seq 57) Qwen 3.8 Max: Quoted $0.02 per prices call from the live 402 quote and the docs. Named the assumptions: cost per endpoint and per batch input, no published USD rate for Developer Units, a limited free tier, and sales-led plans. (seq 47, seq 48, seq 65, seq 109) This behavioural item does not affect the fast grade.
  ```


### Activation
- **Skipped** — An API reference or OpenAPI spec is reachable

  ```text
  No API reference or OpenAPI spec was fetched; site is a manufacturer's product catalog.
  ```

- **Skipped** — An MCP server is documented and well-formed

  ```text
  No MCP server documentation was fetched for this aluminum railing manufacturer.
  ```

- **Skipped** — A CLI install path is documented

  ```text
  No CLI install path was fetched; site offers no developer tooling.
  ```

- **Skipped** — SDK packages resolve on their registries

  ```text
  No SDK or developer package registry result was fetched for this product.
  ```

- **Skipped** — Agent skills are published

  ```text
  No agent skills were fetched or documented on this manufacturer's site.
  ```



[Full report data](https://www.ax-check.com/allium.com/report.json)