XAI

List prices per 1M tokens (input/output) published on an official page without login.

Captured 2026-08-27

Price unit is unambiguous (per 1M tokens; input vs output separated).

Captured 2026-08-27

Page states an effective/updated date (attributable to a snapshot).

Re-scored MET on our 2026-09-13 re-verification. At our 2026-08-27 capture the page carried no effective date, last-updated stamp or version marker, and that is what we sent xAI on 2026-08-28. The page now states "Last updated: September 7, 2026" at its foot, which satisfies the criterion as written. xAI did not reply within the window; we record the change without attributing it.

Captured 2026-08-27 · re-verified against the live page 2026-09-13

Cached/batch/discount tiers (where offered) published officially.

Captured 2026-08-27

Promotional pricing labeled as promotional (with end date if time-limited).

Your console has a promotional code field, which suggests promotions exist, but we found no official page publishing their terms or end dates. Not verifiable either way.

Captured 2026-08-27 · re-verified against the live page 2026-09-13

How usage is metered is documented (tokenizer, counting rules, rounding).

Captured 2026-08-27

Cached/prefix behavior is documented (automatic vs opt-in).

Captured 2026-08-27

A tool/formula to estimate request cost before sending is published.

Two of our reviewers read the same billing FAQ page incompatibly - one as offering two ways to estimate cost before a request, the other as pointing only to a tokenizer for estimating token counts without publishing a cost formula. Our methodology resolves reviewer disagreement to the stricter reading, so this is NOT VERIFIABLE rather than MET. A pointer to an explicit pre-request cost estimator would settle it.

Captured 2026-08-27 · re-verified against the live page 2026-09-13

Known billing surprises (TTLs, write premiums, minimums) disclosed in docs.

Captured 2026-08-27

Historical prices are discoverable or retrievable on request.

Captured 2026-08-27

Usage available per model in console/API (not only aggregated).

Captured 2026-08-27

Token counts (input/output) reported alongside spend.

Captured 2026-08-27

Per-request or per-API-key breakdown available.

Captured 2026-08-27

Usage/cost export exists (CSV/API) without premium tier.

Captured 2026-08-27

Near-real-time spend tracking (sub-hour refresh) exists.

Your API returns each request's cost immediately, which we verified. We read this criterion as asking about aggregate spend tracking rather than per-request cost echo, and your console documentation states daily granularity without publishing a refresh interval. If a sub-hour spend view exists and is documented, we will re-score.

Captured 2026-08-27 · re-verified against the live page 2026-09-13

Invoices line-item by service/model.

Captured 2026-08-27

Invoice shows unit quantities and rates, not only totals.

Captured 2026-08-27

Usage CSV/API and invoice are reconcilable without manual mapping.

Captured 2026-08-27 · re-verified against the live page 2026-09-13

Invoice/notification includes readable date range and currency.

Captured 2026-08-27

Billing docs/invoices available via API for automation.

Captured 2026-08-27

Data-use-for-training policy is clearly published.

Captured 2026-08-27

Energy/environmental information is clearly published (yes/no — never a grade).

Captured 2026-08-27 · re-verified against the live page 2026-09-13

Pricing/support changes are communicated before taking effect.

Re-scored MET on our 2026-09-13 re-verification. At capture we could not verify advance notice of any pricing change. Your pricing page, stamped "Last updated: September 7, 2026", now announces a change to X Search billing taking effect on September 21, 2026 - at least fourteen days' notice, published on the pricing page itself. This is the same evidence standard we applied to every provider on this criterion: a dated, specific notice of a price change, published before it takes effect. xAI did not reply within the window; we record the change without attributing it.

Captured 2026-08-27 · re-verified against the live page 2026-09-13

Official API status page is published.

Captured 2026-08-27

Terms specify billing, refund and cancellation terms unambiguously.

Captured 2026-08-27