Research investigation R1117 / comparison

Asana’s Claude linked billing adds a per-request fee; Mintlify requires Enterprise

A common Claude billing mechanism does not produce identical purchasing requirements. The sampled documents establish different enrollment, contractual and rollout conditions, but cannot establish a total-cost winner.

Archived snapshotv1Nov 17, 2026
Verified observations
1

1 measured fields

Supported claims
6

6 material findings

Cited sources
4

4 primary or authoritative

Research score
78

Automated topic and evidence score

Interactive figureAsana’s Claude linked billing adds a per-request...
CSV JSON
Data statusAwaiting verified observations

The comparison covers only these three integrations and six primary documents. It extends the supplied launch coverage by separating payment routing from partner purchasing requirements and processing boundaries. The collection record includes reused snapshots and live page checks, but no authenticated execution, private contracts or historical verification of exact cutoff-time contents.

Verified observationNo chart values are being inferredLast updated Nov 17, 2026

Version ledger

Frozen public editions

Each edition preserves the records, method, sources, and downloads available at publication time.

  1. v1 / latestNov 17, 20261 records / 4 sources

    Initial public snapshot with 1 records and 4 cited sources.

Coverage note

The comparison covers only these three integrations and six primary documents. It extends the supplied launch coverage by separating payment routing from partner purchasing requirements and processing boundaries. The collection record includes reused snapshots and live page checks, but no authenticated execution, private contracts or historical verification of exact cutoff-time contents.

Dataset ID
spd:claude-linked-billing-across-asana-mintlify-and-harness-what-changes-besides-the-invoice-d9a5d5c5
Stable URL
/research/claude-linked-billing-across-asana-mintlify-and-harness-what-changes-besides-the-invoice-d9a5d5c5
Version
v1
Coverage
Live collection
Records
1
Fields
7
Updated

Read the data

The records behind the figure

CSV JSON
Asana’s Claude linked billing adds a per-request fee; Mintlify requires Enterprise data records
EntityMetricValueUnitObservedSourceTransform
—Evidence sample and cutoff limitationBounded to six primary documents: Anthropic implementation guide and Marketplace FAQ; Asana help article; Mintlify announcement and setup documentation; Harness announcement. Requested cutoff: 2026-11-17T21:31:02.030Z. Supplied snapshots were retrieved at 2026-11-17T21:32:18.118Z, after that cutoff;——https://claude.com/marketplace/agents-products—

Measurement technique

How to read this report

  1. 01Synthesize the supplied six-document primary-source sample: Anthropic’s implementation guide and Marketplace FAQ, Asana’s help article, Mintlify’s announcement and setup documentation, and Harness’s Cosmos release. This is evidence synthesis, not a new collection or authenticated integration test.
  2. 02Preserve the requested evidence cutoff of November 17, 2026, at 21:31:02.030 UTC. The collection record says supplied snapshots were retrieved at 21:32:18.118 UTC, after that cutoff. Without historical snapshots, exact page contents at the requested cutoff cannot be certified.
  3. 03Build an evidence_matrix with partner columns and rows for account eligibility, partner entitlement, approval roles, adoption scope, covered features, remaining charges, spend controls, failure behavior and processing boundaries. Attach source attribution and classify each proposition as supported, contradicted or unspecified; do not score documentation completeness as product capability.
  4. 04Record the common eligibility baseline separately: directly Anthropic-billed Claude Platform organizations qualify; Claude subscription plans, cloud-provider accounts and cloud-marketplace billing do not. An Anthropic commitment is optional, while some promotional credits are ineligible.
  5. 05Populate the Asana column with representative-enabled private preview, organization-wide eligible usage, other-provider disabling and a negotiated per-request fee. Do not infer an undisclosed fee rate.
  6. 06Populate the Mintlify column with Enterprise contractual entitlement, administrator/owner linking permissions, project-level selection and separate subscription billing. Record assistant, agent, Autopilot, automations and documented supporting tasks without equating named agents with Anthropic’s Managed Agents API.
  7. 07Populate the Cosmos column with the release’s directly billed account requirement, approval roles, monthly limits, Console unlinking, separate subscription and continued API-key support. Mark exhaustive feature coverage, additional usage fees, Harness-side linking roles and project-level selection unspecified.
  8. 08Keep Mintlify’s detailed controls partner-specific: list-price cap accounting before negotiated discounts, possible crossing-request overshoot, enforcement of whichever applicable cap is reached first, AI stopping on linked projects after billing failures, and organization-wide effects of unlinking.

Sources

Evidence

3 publishers supporting 1 record. Expand a publisher to inspect its cited pages.

Next report / 01AI Model Economics Index All research reports
YOUR READING SPACE

Notifications