Autumn vs Airwallex

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Airwallex
   Autumn✓fullprobed8/10

   A probe confirms llms.txt is live at docs.useautumn.com/llms.txt returning HTTP 200 with structured doc links, directly satisfying the ability to point an agent at agent-oriented docs; this is reinforced by an official MCP server for AI assistants. Missing for 10: no independent/community confirmation of an agent successfully consuming llms.txt in practice, and no openapi.json fallback.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.useautumn.com/llms.txt # Autumn - [Welcome to Autumn](https://docs.useautumn.com/welcome.md): Drop…”
   • [claimed-docs] “Autumn MCP connects AI assistants to Autumn's billing, customer, plan, balance, and log tools.”
   • [probe] “official MCP server documented at https://docs.useautumn.com/documentation/mcp”

   proof ↗⚑ flag

   Airwallex✓fullprobed9/10

   Airwallex publishes a live llms.txt (confirmed HTTP 200 probe) plus explicit agent-oriented docs (developer-connector.md, agentos.md, ai-agent-instructions.md) designed for machine/agent consumption, including instructions written specifically for AI agents and dedicated MCP endpoints. This directly matches pointing an agent at llms.txt/agent-oriented docs. Missing for 10: independent third-party confirmation that agents successfully consume these docs in practice (only vendor docs and a probe, no hands-on community report).

   • [probe] “PROBE llms.txt: HTTP 200 at https://www.airwallex.com/llms.txt # Airwallex > Airwallex is a leading global financial platform for modern bus…”
   • [claimed-docs] “The Airwallex developer connectors connects AI coding agents — Cursor, Claude Code, Codex, and similar tools — to Airwallex documentation an…”
   • [claimed-docs] “The docs publish dedicated "Instructions for AI agents" pages (Integration Best Practices and Payments integration notes) written for machin…”
   • [claimed-docs] “A second, integration-time MCP pair: "The Airwallex developer connectors connects AI coding agents — Cursor, Claude Code, Codex, and similar…”
   • [probe] “official MCP server documented at https://www.airwallex.com/docs/developer-tools/ai/agentos”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Airwallex
   Autumn~partialprobed5/10

   Autumn ships an `atmn` CLI that syncs pricing configs (`autumn.config.ts`) with a single command and supports non-interactive actions like `preview` and `pull`, which are scriptable and could run in CI, plus SDK calls (`check`, `track`) that are inherently headless. However, there's no explicit documentation or example of running Autumn in a CI/CD pipeline, no mention of non-interactive auth/token flags for automated environments, and no community confirmation of headless CI usage. Missing for 10: explicit CI/CD pipeline examples, non-interactive authentication guidance, and independent confirmation of automated/headless runs.

   • [claimed-docs] “The `atmn` CLI lets you define your pricing plans in code via an `autumn.config.ts` file, and sync them to Autumn with a single command.”
   • [claimed-docs] “You can preview your plans without pushing anything: bunx atmn preview”
   • [claimed-docs] “If you already have products created in the dashboard, run `atmn pull` to pull them into your local config.”
   • [claimed-docs] “const response = await autumn.check({ customerId: "user_123", featureId: "messages" });”
   • [claimed-docs] “await autumn.track({ customerId: "user_or_org_id_from_auth", featureId: "messages", value: 1, });”
   • [probe] “official CLI documented at https://docs.useautumn.com/cli/getting-started”

   proof ↗⚑ flag

   Airwallex✓fullprobed8/10

   Airwallex ships a documented CLI explicitly designed for scripting and CI ("script repeatable tasks, and wire Airwallex into automated systems"), plus API/webhook infrastructure enabling headless automation, corroborated by a probe confirming the CLI docs exist. Missing for 10: independent third-party evidence of actual CI pipeline usage and explicit CI/CD examples (e.g., GitHub Actions integration) beyond vendor docs.

   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [probe] “official CLI documented at https://www.airwallex.com/docs/developer-tools/cli”
   • [claimed-docs] “Webhooks with documented reliability semantics: "Your endpoint must respond with a 200 status code so that Airwallex can confirm delivery. E…”
   • [claimed-docs] “Webhooks enable Airwallex to send instant, real-time push notifications to your application when events occur in your Airwallex account.”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Airwallex
   Autumn✓fullprobed8/10

   Autumn is a billing/entitlements SaaS platform (not itself an agent), and it documents an official MCP server that connects AI assistants to its billing, customer, plan, balance, and log tools, confirmed by both docs and probe. Missing for 10: independent hands-on confirmation of the MCP server working and more detail on its tool coverage/setup.

   • [claimed-docs] “Autumn MCP connects AI assistants to Autumn's billing, customer, plan, balance, and log tools.”
   • [probe] “official MCP server documented at https://docs.useautumn.com/documentation/mcp”

   proof ↗⚑ flag

   Airwallex✓fullprobed9/10

   Airwallex documents an official hosted remote MCP server (AgentOS MCP at https://mcp.airwallex.com/mcp) with OAuth authentication, safety guardrails, and explicit connection instructions for MCP clients like Claude Code, plus a separate Developer MCP for docs/sandbox integration work — both first-party and independently probed as live docs. Missing for 10: independent hands-on third-party verification of the MCP server actually working end-to-end beyond vendor docs and a probe confirming the doc page exists.

   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “A second, integration-time MCP pair: "The Airwallex developer connectors connects AI coding agents — Cursor, Claude Code, Codex, and similar…”
   • [probe] “official MCP server documented at https://www.airwallex.com/docs/developer-tools/ai/agentos”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Airwallex
   Autumn✓fullprobed8/10

   Autumn ships an official `atmn` CLI documented in first-party docs, supporting config-as-code (autumn.config.ts), pushing/syncing plans, previewing changes (bunx atmn preview), and pulling existing dashboard products (atmn pull) — clearly enabling AI-native, code-first workflows. Missing for 10: independent/hands-on community verification of the CLI itself (community evidence covers billing/security topics, not CLI usage) and no evidence of scripting/automation-specific features beyond basic commands.

   • [claimed-docs] “The `atmn` CLI lets you define your pricing plans in code via an `autumn.config.ts` file, and sync them to Autumn with a single command.”
   • [claimed-docs] “You can preview your plans without pushing anything: bunx atmn preview”
   • [claimed-docs] “If you already have products created in the dashboard, run `atmn pull` to pull them into your local config.”
   • [probe] “official CLI documented at https://docs.useautumn.com/cli/getting-started”

   proof ↗⚑ flag

   Airwallex✓fullprobed9/10

   Airwallex documents an official CLI (installable via a public install script) that exposes API resources as terminal commands, supports sandbox/production modes, scripting, and is explicitly positioned as the foundation for AI coding agents to operate accounts, corroborated by a probe confirming the docs page exists. Missing for 10: independent/hands-on third-party review of the CLI beyond vendor docs and probes.

   • [claimed-docs] “The Airwallex CLI lets you work with your Airwallex account directly from a command line.”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “Explore the API interactively — discover endpoints, preview requests, and inspect schemas before you commit to a full integration.”
   • [probe] “official CLI documented at https://www.airwallex.com/docs/developer-tools/cli”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Airwallex
   Autumn✓fullprobed8/10

   Autumn ships a documented public API with clear reference pages (check, track, attach) and code examples, webhooks, and an API-reference section, letting an AI-native user drive billing/entitlements programmatically. Missing for 10: a discoverable machine-readable OpenAPI/swagger spec (probe found only 404s at expected paths), and independent hands-on confirmation of API robustness beyond docs.

   • [claimed-docs] “const response = await autumn.check({ customerId: "user_123", featureId: "messages" });”
   • [claimed-docs] “await autumn.track({ customerId: "user_or_org_id_from_auth", featureId: "messages", value: 1, });”
   • [claimed-docs] “You can also [check and reserve] balance in a single, atomic API call for concurrent events.”
   • [claimed-docs] “Attaches a plan to a customer. Handles new subscriptions, upgrades and downgrades.”
   • [claimed-docs] “Fired whenever a customer's plans change — new subscriptions, upgrades, downgrades, etc.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.useautumn.com/openapi.json, https://docs.useautumn.com/swagger.json, https://docs.useau…”

   proof ↗⚑ flag

   Airwallex✓fullprobed9/10

   Airwallex publishes extensive first-party API documentation, scoped API keys, a sandbox environment, CLI, webhooks with retry semantics, and even dedicated 'Instructions for AI agents' pages plus AgentOS/MCP tooling explicitly built for agentic/programmatic use, confirmed live via probes (llms.txt 200, CLI and AgentOS docs pages resolving). Missing for 10: independent third-party developer corroboration (e.g. community reviews of the public API itself) beyond vendor docs and probes.

   • [claimed-docs] “Programmatically create connected accounts for businesses and individuals, and enable them with rich financial capabilities.”
   • [claimed-docs] “A scoped API key grants only the resource permissions you assign (Read or Write on specific APIs), instead of full account access.”
   • [claimed-docs] “The Airwallex CLI lets you work with your Airwallex account directly from a command line.”
   • [claimed-docs] “Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulati…”
   • [claimed-docs] “Webhooks enable Airwallex to send instant, real-time push notifications to your application when events occur in your Airwallex account.”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “"Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulat…”
   • [claimed-docs] “Webhooks with documented reliability semantics: "Your endpoint must respond with a 200 status code so that Airwallex can confirm delivery. E…”
   • [claimed-docs] “The docs publish dedicated "Instructions for AI agents" pages (Integration Best Practices and Payments integration notes) written for machin…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://www.airwallex.com/llms.txt # Airwallex > Airwallex is a leading global financial platform for modern bus…”
   • [probe] “official CLI documented at https://www.airwallex.com/docs/developer-tools/cli”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Airwallex
   Autumn—none0/10

   Autumn's docs describe customerId-based check/track/attach calls and an MCP server for billing tools, but there is no evidence of an API-key or credential system that lets an AI-native user mint scoped, least-privilege credentials for an agent. Community reports even describe unauthenticated server actions and customer_id spoofing (IDOR), the opposite of least-privilege access control.

   • [claimed-docs] “const response = await autumn.check({ customerId: "user_123", featureId: "messages" });”
   • [claimed-docs] “await autumn.track({ customerId: "user_or_org_id_from_auth", featureId: "messages", value: 1, });”
   • [claimed-docs] “Autumn MCP connects AI assistants to Autumn's billing, customer, plan, balance, and log tools.”
   • [community] “Commenters criticized Autumn's 'backendless billing' approach as reinventing JWTs poorly: "Your encrypted customer ID has the exact same sem…”
   • [community] “Security concern raised: Autumn's server actions were public, unauthenticated routes, meaning "a simple curl request with a different custom…”

   proof ↗⚑ flag

   Airwallex✓fullclaimed8/10

   Airwallex documents scoped API keys with granular Read/Write permissions per resource (not full account access), and explicitly ties this to agent use cases via AgentOS/MCP with additional layered safety defaults (no money-out actions by default, OAuth-scoped roles, role-gated CLI authorization). This directly matches the story of issuing least-privilege credentials for an agent. Missing for 10: independent/hands-on verification of scope enforcement and no documented UI/API walkthrough of creating a scoped key specifically for an agent identity.

   • [claimed-docs] “A scoped API key grants only the resource permissions you assign (Read or Write on specific APIs), instead of full account access.”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “A second, integration-time MCP pair: "The Airwallex developer connectors connects AI coding agents — Cursor, Claude Code, Codex, and similar…”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Airwallex
   Autumn✓fullprobed7/10

   Docs consistently show official SDK code (autumn.check, autumn.track, autumn.attach) across many endpoints, plus a companion CLI (atmn) for config sync, indicating a first-party SDK for building AI-native billing integrations. Missing for 10: explicit multi-language SDK coverage/package registry links and independent developer corroboration of SDK usage beyond docs.

   • [claimed-docs] “const response = await autumn.check({ customerId: "user_123", featureId: "messages" });”
   • [claimed-docs] “await autumn.track({ customerId: "user_or_org_id_from_auth", featureId: "messages", value: 1, });”
   • [claimed-docs] “The `atmn` CLI lets you define your pricing plans in code via an `autumn.config.ts` file, and sync them to Autumn with a single command.”
   • [claimed-docs] “Attaches a plan to a customer. Handles new subscriptions, upgrades and downgrades.”
   • [probe] “official CLI documented at https://docs.useautumn.com/cli/getting-started”

   proof ↗⚑ flag

   Airwallex✓fullprobed9/10

   Airwallex documents a full official SDK/API surface for AI-native building: REST API, official CLI, hosted MCP servers (AgentOS MCP and Developer MCP), dedicated AI-agent instructions pages, sandbox environment, webhooks, and plugin installs for Claude Code/Cursor. This is well beyond a typical SDK — it includes machine-readable docs, scoped API keys, and agent-specific tooling with safety guardrails, confirmed by both docs and independent probes. Missing for 10: independent third-party developer reviews/hands-on validation of SDK ergonomics beyond vendor docs.

   • [claimed-docs] “The Airwallex developer connectors connects AI coding agents — Cursor, Claude Code, Codex, and similar tools — to Airwallex documentation an…”
   • [claimed-docs] “Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiarie…”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “A second, integration-time MCP pair: "The Airwallex developer connectors connects AI coding agents — Cursor, Claude Code, Codex, and similar…”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “The docs publish dedicated "Instructions for AI agents" pages (Integration Best Practices and Payments integration notes) written for machin…”
   • [claimed-docs] “"Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulat…”
   • [probe] “official MCP server documented at https://www.airwallex.com/docs/developer-tools/ai/agentos”
   • [probe] “official CLI documented at https://www.airwallex.com/docs/developer-tools/cli”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Airwallex
   Autumn~partialclaimed6/10

   Autumn documents webhooks fired on plan/subscription changes (autumn-docs-8), giving basic event subscription capability, but evidence doesn't cover a broad event catalog (e.g. usage/track events), payload schemas, signing/verification, or subscription management API — missing for 10: full webhook event catalog, payload/signature docs, subscription management endpoints, independent hands-on confirmation.

   • [claimed-docs] “Fired whenever a customer's plans change — new subscriptions, upgrades, downgrades, etc.”

   proof ↗⚑ flag

   Airwallex✓fullclaimed9/10

   Airwallex documents a full webhooks system with real-time push notifications, stable event IDs for safe retry handling, delivery status inspection, and re-delivery for debugging — clearly enabling event subscription for automated/AI-native workflows. Missing for 10: no independent/hands-on corroboration beyond first-party docs.

   • [claimed-docs] “Webhooks enable Airwallex to send instant, real-time push notifications to your application when events occur in your Airwallex account.”
   • [claimed-docs] “Webhooks with documented reliability semantics: "Your endpoint must respond with a 200 status code so that Airwallex can confirm delivery. E…”

   proof ↗⚑ flag

Agentic features

1. ai-native userOperate the product with natural-language commands

   weight 2 · round to Airwallex
   Autumn~partialprobed5/10

   Autumn ships an official MCP server that 'connects AI assistants to Autumn's billing, customer, plan, balance, and log tools,' enabling AI-native/natural-language operation indirectly through an MCP-connected assistant rather than a built-in chat interface. There's no first-party or community evidence of actual natural-language command usage in practice, and the product is fundamentally a CLI/API/dashboard tool otherwise. Missing for 10: direct natural-language command interface (not just MCP passthrough), hands-on demonstration of NL commands working, independent user corroboration.

   • [claimed-docs] “Autumn MCP connects AI assistants to Autumn's billing, customer, plan, balance, and log tools.”
   • [probe] “official MCP server documented at https://docs.useautumn.com/documentation/mcp”

   proof ↗⚑ flag

   Airwallex✓fullprobed8/10

   Airwallex ships AgentOS with an MCP server and CLI explicitly designed so AI agents (Claude Code, Cursor, Codex) can read balances, create beneficiaries, issue cards, and run multi-step financial workflows via natural-language instructions, plus dedicated 'AI agent instructions' docs to guide correct NL-driven API use. Missing for 10: independent/hands-on validation of real-world NL command reliability and no third-party review beyond first-party docs.

   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “The docs publish dedicated "Instructions for AI agents" pages (Integration Best Practices and Payments integration notes) written for machin…”
   • [probe] “official MCP server documented at https://www.airwallex.com/docs/developer-tools/ai/agentos”
   • [probe] “official CLI documented at https://www.airwallex.com/docs/developer-tools/cli”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to Airwallex
   Autumn—none0/10

   Autumn's docs include static code snippets for API endpoints (e.g. check, attach) but there is no evidence of an interactive, runnable API console—probes for openapi/swagger specs all 404'd, indicating no interactive reference tooling exists.

   • [claimed-docs] “const response = await autumn.check({ customerId: "user_123", featureId: "messages" });”
   • [claimed-docs] “Attaches a plan to a customer. Handles new subscriptions, upgrades and downgrades.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.useautumn.com/openapi.json, https://docs.useautumn.com/swagger.json, https://docs.useau…”

   proof ↗⚑ flag

   Airwallex~partialclaimed5/10

   Airwallex docs claim you can 'explore the API interactively — discover endpoints, preview requests, and inspect schemas before you commit to a full integration' via the CLI, and a sandbox environment lets you run real requests without live money, which together approximate an interactive, runnable API exploration experience. However, there's no evidence of a traditional in-browser interactive API reference (e.g., Swagger/Redoc-style docs with embedded runnable code snippets) — the interactivity is CLI-driven rather than a reference page. Missing for 10: a dedicated interactive web API reference UI, embedded runnable code samples in docs, and independent confirmation of this workflow.

   • [claimed-docs] “Explore the API interactively — discover endpoints, preview requests, and inspect schemas before you commit to a full integration.”
   • [claimed-docs] “Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulati…”
   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Autumn—none0/10

   There's an api-reference section implying documented endpoints, but a direct probe for OpenAPI/Swagger specs at standard paths returned 404s with no alternate machine-readable spec found or linked anywhere in the docs.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.useautumn.com/openapi.json, https://docs.useautumn.com/swagger.json, https://docs.useau…”

   proof ↗⚑ flag

   Airwallex—none0/10

   While Airwallex documents extensive API tooling (CLI, MCP servers, sandbox, interactive schema explorer), none of the evidence explicitly confirms a downloadable OpenAPI (or equivalent) spec file. The 'inspect schemas' feature (airwallex-docs-20) hints at schema-driven tooling but doesn't confirm exportable machine-readable spec access.

   • [claimed-docs] “Explore the API interactively — discover endpoints, preview requests, and inspect schemas before you commit to a full integration.”
   • [probe] “official CLI documented at https://www.airwallex.com/docs/developer-tools/cli”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Airwallex
   Autumn—none0/10

   Autumn is a billing/entitlements layer where sandbox/test-mode testing is a reasonable ask (similar to Stripe test mode), but the evidence pack has no mention of a dedicated sandbox/test environment separate from production—only 'atmn preview' for previewing pricing plan changes before pushing config, which is not the same as isolating test transactions/customers from production data.

   • [claimed-docs] “You can preview your plans without pushing anything: bunx atmn preview”

   proof ↗⚑ flag

   Airwallex✓fullclaimed9/10

   Airwallex documents a dedicated sandbox environment fully separate from production, covering nearly all products/APIs, with self-serve signup and simulation guides, and even AI-specific sandbox MCP/connector tooling (mcp.sandbox.airwallex.com/developer) explicitly for agents to 'create test resources, simulate events, and call sandbox endpoints' without touching production. The CLI also defaults to sandbox unless --prod is passed, reinforcing safe-by-default testing. Missing for 10: independent/hands-on confirmation of sandbox parity beyond docs.

   • [claimed-docs] “Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulati…”
   • [claimed-docs] “"Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulat…”
   • [claimed-docs] “A second, integration-time MCP pair: "The Airwallex developer connectors connects AI coding agents — Cursor, Claude Code, Codex, and similar…”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Autumn—none0/10

   No evidence of API versioning scheme or documented deprecation policy; changelog entries show ongoing changes but no version numbers or deprecation guarantees, and OpenAPI/spec probes 404. missing for 10: versioned API endpoints/headers, explicit deprecation policy documentation, migration guides for breaking changes.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.useautumn.com/openapi.json, https://docs.useautumn.com/swagger.json, https://docs.useau…”
   • [claimed-docs] “Usage alerts gain a `basis` field that defines what 100% means: the full `balance` (the default, unchanged), the plan’s `included` grants, `…”
   • [claimed-docs] “Catalog plans now accept a `processors` object so Autumn can reuse your existing Stripe catalog instead of minting new objects.”

   proof ↗⚑ flag

   Airwallex—none0/10

   The evidence pack covers API keys, sandbox, CLI, MCP/AgentOS, webhooks, and AI-agent instructions, but nowhere documents API versioning conventions or a formal deprecation policy/timeline for endpoints. The only related hint is steering away from a 'legacy' SDK library, which is not evidence of a documented API versioning/deprecation policy.

   ⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Airwallex
   Autumn—none0/10

   Autumn's docs show only single-item operations (check, track, attach for one customer/feature at a time) and CLI commands (pull/preview/push) that sync a single config, but no batch/bulk API for operating across many customers, features, or items at once. missing for 10: bulk/batch API endpoints, documentation of batch customer or feature updates, evidence of any multi-item transaction support.

   • [claimed-docs] “const response = await autumn.check({ customerId: "user_123", featureId: "messages" });”
   • [claimed-docs] “await autumn.track({ customerId: "user_or_org_id_from_auth", featureId: "messages", value: 1, });”
   • [claimed-docs] “Attaches a plan to a customer. Handles new subscriptions, upgrades and downgrades.”
   • [claimed-docs] “The `atmn` CLI lets you define your pricing plans in code via an `autumn.config.ts` file, and sync them to Autumn with a single command.”

   proof ↗⚑ flag

   Airwallex~partialclaimed4/10

   The Airwallex CLI and AgentOS toolkit let AI agents 'script repeatable tasks' and 'wire Airwallex into automated systems' or run 'multi-step financial workflows,' which implies looping over many items via API/CLI calls, but there is no documented native batch/bulk endpoint (e.g., bulk beneficiary creation, batch payouts, bulk invoice generation) for processing many items in a single call. Missing for 10: explicit bulk/batch API or CLI subcommands, evidence of batch-processing limits or throughput, and independent confirmation of bulk usage in practice.

   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “Airwallex Transfers allows you to move funds across the globe easily to your suppliers, employees, contractors and/or own bank accounts.”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Airwallex
   Autumn~partialclaimed4/10

   Autumn supports event-driven mechanisms like webhooks fired on plan changes and usage alerts with configurable thresholds (basis field), which act as simple automated triggers tied to billing state. However, there is no evidence of a general-purpose rule engine where users can define custom trigger→action logic across arbitrary events; the automation is scoped narrowly to billing/entitlement events. Missing for 10: a documented rules/automation DSL or workflow builder, support for arbitrary custom triggers/actions beyond billing events, and evidence of chaining multiple actions per rule.

   • [claimed-docs] “Fired whenever a customer's plans change — new subscriptions, upgrades, downgrades, etc.”
   • [claimed-docs] “Usage alerts gain a `basis` field that defines what 100% means: the full `balance` (the default, unchanged), the plan’s `included` grants, `…”
   • [claimed-docs] “await autumn.track({ customerId: "user_or_org_id_from_auth", featureId: "messages", value: 1, });”
   • [claimed-docs] “You can also [check and reserve] balance in a single, atomic API call for concurrent events.”

   proof ↗⚑ flag

   Airwallex~partialclaimed5/10

   Airwallex supports event-driven automation via webhooks (real-time push notifications with retry/dedupe semantics) and AgentOS/CLI/MCP tooling that lets agents run multi-step workflows, but there is no documented user-facing 'rules engine' where an AI-native user declaratively defines trigger-condition-action rules — automation still requires building a webhook consumer or scripting agent workflows rather than configuring rules in-product. missing for 10: a native rules/automation builder (event + condition + action) exposed via API or UI, and independent evidence of such rule-based automation actually firing in production.

   • [claimed-docs] “Webhooks with documented reliability semantics: "Your endpoint must respond with a 200 status code so that Airwallex can confirm delivery. E…”
   • [claimed-docs] “Webhooks enable Airwallex to send instant, real-time push notifications to your application when events occur in your Airwallex account.”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”

   proof ↗⚑ flag

Ai billing ops

1. ai-native userHave an agent monitor failed payments via API and webhooks and drive retries and dunning outreach

   weight 3 · round to Airwallex
   Autumn—none0/10

   Evidence shows Autumn webhooks fire only on plan changes (new subscriptions, upgrades, downgrades) and covers usage/credit tracking, but there is no mention of failed-payment events, retry logic, or dunning outreach workflows anywhere in the docs, changelog, or community threads. This is a fair axis for a billing product (Stripe-based dunning is a common billing capability) but no evidence supports Autumn delivering it.

   • [claimed-docs] “Fired whenever a customer's plans change — new subscriptions, upgrades, downgrades, etc.”
   • [claimed-docs] “Attaches a plan to a customer. Handles new subscriptions, upgrades and downgrades.”
   • [claimed-docs] “Usage alerts gain a `basis` field that defines what 100% means: the full `balance` (the default, unchanged), the plan’s `included` grants, `…”

   proof ↗⚑ flag

   Airwallex~partialclaimed5/10

   Airwallex provides the raw building blocks an agent could use for this story: webhooks with retry-safe event IDs and delivery inspection/re-delivery, an AgentOS MCP/CLI toolkit that can read balances and act on the production account, and API access to payments/billing data. However, there is no documented failed-payment monitoring workflow, no dunning/retry-specific Skill, and 'no money-out actions by default' in AgentOS suggests retry/charge actions would be restricted, requiring custom agent logic rather than a built-in capability. missing for 10: a documented failed-payment retry or dunning skill/workflow, evidence of automated retry logic tied to webhook failed-payment events, and confirmation that money-out/retry actions are actually permitted for agents rather than blocked by default guardrails.

   • [claimed-docs] “Webhooks with documented reliability semantics: "Your endpoint must respond with a 200 status code so that Airwallex can confirm delivery. E…”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “Webhooks enable Airwallex to send instant, real-time push notifications to your application when events occur in your Airwallex account.”
   • [claimed-docs] “Multi-item: Billing for multiple products in one place, for example, a software license plus a support package.”

   proof ↗⚑ flag

2. ai-native userHave an agent provision a new product, price, and payment link via the API in a single session

   weight 3 · round to Airwallex
   Autumn~partialprobed5/10

   Autumn's API/CLI supports creating products/plans (attach, config.ts, atmn CLI) and MCP server exposes billing/plan/customer tools to AI assistants, suggesting an agent could provision products and prices programmatically, but there is no direct evidence of generating a 'payment link' via API or of a documented single-session workflow combining product+price+payment link creation. missing for 10: explicit payment-link creation endpoint/API, end-to-end example of an agent provisioning product+price+payment link in one session, independent verification of this workflow.

   • [claimed-docs] “The `atmn` CLI lets you define your pricing plans in code via an `autumn.config.ts` file, and sync them to Autumn with a single command.”
   • [claimed-docs] “Attaches a plan to a customer. Handles new subscriptions, upgrades and downgrades.”
   • [claimed-docs] “Autumn MCP connects AI assistants to Autumn's billing, customer, plan, balance, and log tools.”
   • [probe] “official MCP server documented at https://docs.useautumn.com/documentation/mcp”
   • [probe] “official CLI documented at https://docs.useautumn.com/cli/getting-started”

   proof ↗⚑ flag

   Airwallex~partialclaimed6/10

   Airwallex has real billing/invoicing/payment-link APIs and an agent-facing toolkit (AgentOS/CLI/MCP) that can create beneficiaries, cards, and run multi-step workflows, and docs explicitly cover products, subscriptions, invoicing, and payment links, but no evidence shows a documented single-session flow where an agent creates a product, sets a price, and generates a payment link end-to-end via one skill/workflow. missing for 10: an explicit worked example or skill covering product+price+payment-link creation in one agent session, and independent/hands-on confirmation this multi-step billing workflow works in practice.

   • [claimed-docs] “Payment Links are the easiest way for you to accept payments online without a digital storefront.”
   • [claimed-docs] “Multi-item: Billing for multiple products in one place, for example, a software license plus a support package.”
   • [claimed-docs] “Generate invoices and digital payment links with over 160+ local payment methods”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “Airwallex Billing layers subscriptions, invoicing, and hosted/embedded billing checkout on top of payments acceptance — documented getting-s…”

   proof ↗⚑ flag

Subscriptions

1. finance-ops userAutomatically retry failed subscription payments with smart dunning and recovery emails

   weight 2 · round drawn
   Autumn—none0/10

   Autumn's evidence covers metering, entitlements, plan attachment, and Stripe catalog sync, but there is no mention of dunning, retry logic for failed payments, or recovery emails anywhere in the docs, changelog, or community discussion.

   ⚑ flag

   Airwallex—none0/10

   Airwallex Billing docs cover subscriptions, invoicing, and payment collection but there is no mention of automatic retry logic for failed subscription payments, smart dunning rules, or automated recovery email sequences.

   • [claimed-docs] “Multi-item: Billing for multiple products in one place, for example, a software license plus a support package.”
   • [claimed-docs] “Generate invoices and digital payment links with over 160+ local payment methods”
   • [claimed-docs] “Multi-frequency: Charging for different items on different schedules, for example, an annual upfront software fee combined with monthly supp…”
   • [claimed-docs] “You can issue invoices in two ways with Airwallex Billing: One-time invoices ... Recurring invoices”
   • [claimed-docs] “Airwallex Billing layers subscriptions, invoicing, and hosted/embedded billing checkout on top of payments acceptance — documented getting-s…”

   proof ↗⚑ flag

2. developerSet up recurring subscription billing with plans, trials, upgrades, and proration

   weight 3 · round to Autumn
   Autumn✓fullcommunity8/10

   Autumn's docs explicitly cover defining plans (autumn.config.ts + atmn CLI), attaching plans to customers with automatic handling of new subscriptions, upgrades, and downgrades, usage-based/pay-per-use pricing with proration-like billing period logic, and webhooks firing on plan changes (new subscriptions, upgrades, downgrades). Community feedback corroborates real-world use for billing/entitlements and notes Autumn's team handling of annual/monthly billing transitions and race conditions. Missing for 10: explicit first-party documentation of free trials and detailed proration mechanics, plus independent hands-on verification of trial/upgrade billing flows.

   • [claimed-docs] “The `atmn` CLI lets you define your pricing plans in code via an `autumn.config.ts` file, and sync them to Autumn with a single command.”
   • [claimed-docs] “Attaches a plan to a customer. Handles new subscriptions, upgrades and downgrades.”
   • [claimed-docs] “Fired whenever a customer's plans change — new subscriptions, upgrades, downgrades, etc.”
   • [claimed-docs] “Pay-per-use (usage-based) pricing charges customers based on how much of a feature they actually consume, billed at the end of each billing …”
   • [claimed-docs] “Catalog plans now accept a `processors` object so Autumn can reuse your existing Stripe catalog instead of minting new objects.”
   • [community] “Autumn combines billing, metering, and entitlements into a single state, unlike Lago which only handles billing—users must sync permissions …”
   • [community] “"love this as someone who's been fixing the same billing bugs over and over and who sometimes finds stripe more complex than it should be." …”

   proof ↗⚑ flag

   Airwallex~partialclaimed5/10

   Airwallex Billing documents subscription management with multi-item and multi-frequency billing plus recurring invoicing, indicating core plan-based recurring billing capability. However, the evidence pack never mentions trial periods, plan upgrades/downgrades, or proration logic explicitly. Missing for 10: documented trial period support, upgrade/downgrade workflows, and proration calculation mechanics.

   • [claimed-docs] “Multi-item: Billing for multiple products in one place, for example, a software license plus a support package.”
   • [claimed-docs] “Multi-frequency: Charging for different items on different schedules, for example, an annual upfront software fee combined with monthly supp…”
   • [claimed-docs] “You can issue invoices in two ways with Airwallex Billing: One-time invoices ... Recurring invoices”
   • [claimed-docs] “Airwallex Billing layers subscriptions, invoicing, and hosted/embedded billing checkout on top of payments acceptance — documented getting-s…”

   proof ↗⚑ flag

Card acceptance

1. founderAccept an online card payment within a day of signing up

   weight 3 · round to Airwallex
   Autumn~partialcommunity4/10

   Autumn is a billing/metering layer built on top of Stripe, with an `attach` API that handles new subscriptions/upgrades/downgrades and a CLI that syncs pricing plans in a single command, suggesting reasonably fast setup. However, there's no direct evidence of a turnkey checkout page or explicit same-day payment acceptance flow, and the product only works atop Stripe (comm-4), meaning a founder still needs a separate Stripe account/setup for actual card processing. Missing for 10: an end-to-end checkout UI or hosted payment page, explicit time-to-first-payment claims, and independent confirmation of same-day integration speed.

   • [claimed-docs] “Attaches a plan to a customer. Handles new subscriptions, upgrades and downgrades.”
   • [claimed-docs] “The `atmn` CLI lets you define your pricing plans in code via an `autumn.config.ts` file, and sync them to Autumn with a single command.”
   • [community] “Concern raised that Autumn is only built on Stripe, with no support for other payment providers like Paystack, which is needed for regions l…”

   proof ↗⚑ flag

   Airwallex~partialclaimed6/10

   Airwallex offers fast-to-integrate options for accepting online card payments quickly (Payment Links requiring no storefront, Hosted Payment Page, Drop-in Element, sandbox quickstart), which are consistent with a founder going live within a day. However, the evidence does not document the actual account-opening/KYC onboarding timeline or approval SLA for a brand-new founder signing up, which is the critical gatekeeper before any live payment can be accepted. Missing for 10: documented onboarding/KYB approval turnaround time, explicit same-day go-live confirmation, and independent/hands-on evidence of a founder completing signup-to-first-payment within 24 hours.

   • [claimed-docs] “Payment Links are the easiest way for you to accept payments online without a digital storefront.”
   • [claimed-docs] “Hosted Payment Page is a secure, pre-built payment page hosted by Airwallex that lets you accept multiple payment methods with a single inte…”
   • [claimed-docs] “Automatically adjusts input fields to collect information based on the payment method and country.”
   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”

   proof ↗⚑ flag

Checkout surfaces

1. developerEmbed customizable payment components directly in my own site or app instead of redirecting to a hosted page

   weight 3 · round to Airwallex
   Autumn—none0/10

   Autumn's evidence describes a billing/metering/entitlements API, CLI, and MCP integration built on top of Stripe, but nothing in the pack mentions embeddable payment/checkout UI components as an alternative to hosted checkout pages—attach/billing calls appear to route through Stripe's own flows.

   ⚑ flag

   Airwallex✓fullclaimed8/10

   Airwallex offers a Drop-in Element and embeddable checkout components (createElement with customizable appearance/layout, field auto-adjustment) as an alternative to the Hosted Payment Page, plus embedded checkout in Billing, directly enabling in-page/in-app embedded payments rather than redirects. Missing for 10: independent/hands-on developer corroboration of the embedded element's real-world customization depth and no evidence of broader UI kit flexibility beyond docs.

   • [claimed-docs] “Automatically adjusts input fields to collect information based on the payment method and country.”
   • [claimed-docs] “Pass appearance and layout in createElement(...). For examples and supported values, see Customize style and appearance”
   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”
   • [claimed-docs] “Airwallex Billing layers subscriptions, invoicing, and hosted/embedded billing checkout on top of payments acceptance — documented getting-s…”
   • [claimed-docs] “Custom styling rules so you can match the look and feel of your site”

   proof ↗⚑ flag

2. developerRedirect customers to a vendor-hosted, conversion-optimized checkout page without building my own payment UI

   weight 3 · round to Airwallex
   Autumn—none0/10

   The evidence pack covers Autumn's metering, entitlements, CLI, MCP, and plan-attach APIs, but nowhere describes a vendor-hosted, conversion-optimized checkout page that a developer can redirect customers to; 'attach' only documents subscription state changes, not a hosted checkout flow.

   ⚑ flag

   Airwallex✓fullclaimed9/10

   Airwallex documents a Hosted Payment Page — a secure, pre-built, Airwallex-hosted checkout supporting multiple payment methods with custom styling, plus a quickstart showing end-to-end integration without building custom payment UI, and payment links for no-code acceptance. missing for 10: independent/hands-on conversion-optimization benchmarks beyond vendor docs.

   • [claimed-docs] “Hosted Payment Page is a secure, pre-built payment page hosted by Airwallex that lets you accept multiple payment methods with a single inte…”
   • [claimed-docs] “Custom styling rules so you can match the look and feel of your site”
   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”
   • [claimed-docs] “Payment Links are the easiest way for you to accept payments online without a digital storefront.”

   proof ↗⚑ flag

No code selling

1. founderCreate a shareable payment link from the dashboard with no code and start selling immediately

   weight 2 · round to Airwallex
   Autumn—none0/10

   Autumn is a code-first billing/entitlements layer requiring SDK calls, an autumn.config.ts file, or CLI (atmn) to define and attach plans—there is no evidence of a no-code, dashboard-generated shareable payment link feature for founders to start selling immediately.

   • [claimed-docs] “The `atmn` CLI lets you define your pricing plans in code via an `autumn.config.ts` file, and sync them to Autumn with a single command.”
   • [claimed-docs] “If you already have products created in the dashboard, run `atmn pull` to pull them into your local config.”
   • [claimed-docs] “Attaches a plan to a customer. Handles new subscriptions, upgrades and downgrades.”
   • [claimed-docs] “Pay-per-use (usage-based) pricing charges customers based on how much of a feature they actually consume, billed at the end of each billing …”

   proof ↗⚑ flag

   Airwallex~partialclaimed6/10

   Payment Links are documented as 'the easiest way to accept payments online without a digital storefront,' supporting no-code shareable link creation, and other docs (invoicing, quickstart) reinforce a self-serve dashboard flow. However, there's no direct evidence of the dashboard UI/UX for founders (e.g., screenshots, step count, signup-to-first-sale time) or independent/hands-on confirmation of ease of setup. missing for 10: dashboard UI walkthrough or screenshots, independent/hands-on confirmation of no-code simplicity, evidence of account approval/KYC turnaround time before selling.

   • [claimed-docs] “Payment Links are the easiest way for you to accept payments online without a digital storefront.”
   • [claimed-docs] “Generate invoices and digital payment links with over 160+ local payment methods”
   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”

   proof ↗⚑ flag

Payment methods

1. founderOffer digital wallets and local payment methods (Apple Pay, Google Pay, bank redirects, BNPL) from the same integration

   weight 2 · round to Airwallex
   Autumn—none0/10

   Autumn is a billing/entitlement/metering layer built on top of Stripe (confirmed by autumn-comm-4, which notes it lacks support for other payment providers like Paystack), but the evidence pack contains no mention of Autumn configuring or exposing digital wallets, local payment methods, bank redirects, or BNPL options in checkout. Missing for 10: any documentation of wallet/BNPL/local payment method support, checkout configuration options, or evidence Autumn surfaces Stripe's payment-method capabilities to founders.

   • [community] “Concern raised that Autumn is only built on Stripe, with no support for other payment providers like Paystack, which is needed for regions l…”

   proof ↗⚑ flag

   Airwallex~partialclaimed6/10

   Docs confirm a single integration (Hosted Payment Page / Drop-in Element / Payment Links) that adapts fields per payment method/country and mentions 160+ local payment methods via invoicing, plus multi-currency pricing to unlock local methods, but no explicit evidence naming Apple Pay, Google Pay, bank redirects, or BNPL support. Missing for 10: explicit listing/documentation of specific wallets (Apple Pay/Google Pay) and BNPL providers, and independent confirmation these render correctly in a single checkout integration.

   • [claimed-docs] “Hosted Payment Page is a secure, pre-built payment page hosted by Airwallex that lets you accept multiple payment methods with a single inte…”
   • [claimed-docs] “Automatically adjusts input fields to collect information based on the payment method and country.”
   • [claimed-docs] “Generate invoices and digital payment links with over 160+ local payment methods”
   • [claimed-docs] “The Multi-Currency Pricing API (MCP API) enables you to display prices and enable payment in your shoppers' preferred currencies, while also…”
   • [claimed-docs] “Payment Links are the easiest way for you to accept payments online without a digital storefront.”

   proof ↗⚑ flag

Integration reliability

1. developerSafely retry any API request using idempotency keys so network failures never create duplicate charges

   weight 2 · round drawn
   Autumn—none0/10

   No evidence pack item mentions idempotency keys or request-retry safety mechanisms anywhere in Autumn's docs, changelog, or community discussion; the API examples shown (check, track, attach) don't reference idempotency handling.

   ⚑ flag

   Airwallex—none0/10

   The evidence pack describes webhook delivery reliability (stable event IDs for webhook retries) but contains no documentation of idempotency keys for outbound API requests (e.g., payment creation) to prevent duplicate charges on retry. This is a distinct, applicable axis for a payments API but is unevidenced here.

   ⚑ flag

2. developerRely on signed webhook deliveries with automatic retries, event logs, and replay to keep my system consistent with payment state

   weight 3 · round to Airwallex
   Autumn—none0/10

   Docs mention webhooks are fired for plan changes, but there is no evidence of signed payloads, automatic retries, event logs, or replay functionality for webhook deliveries; the evidence pack shows only a single event type description with no delivery guarantees.

   • [claimed-docs] “Fired whenever a customer's plans change — new subscriptions, upgrades, downgrades, etc.”

   proof ↗⚑ flag

   Airwallex~partialclaimed6/10

   Airwallex's webhook docs describe reliability primitives that map to most of this story: a required 200 response for delivery confirmation, a stable event id explicitly for safe retry handling/deduplication, and a web app view to inspect delivery status and re-deliver events after downtime or debugging (covers automatic retries, event logs, and replay). However, none of the evidence explicitly documents cryptographic signature verification for webhook payloads. Missing for 10: explicit signed-webhook/signature-verification documentation, and independent/hands-on confirmation of retry behavior in practice.

   • [claimed-docs] “Webhooks with documented reliability semantics: "Your endpoint must respond with a 200 status code so that Airwallex can confirm delivery. E…”
   • [claimed-docs] “Webhooks enable Airwallex to send instant, real-time push notifications to your application when events occur in your Airwallex account.”

   proof ↗⚑ flag

Onboarding dx

1. developerIntegrate a working payment flow from the docs alone in under a day, with copy-paste examples in my language

   weight 2 · round drawn
   Autumn~partialcommunity6/10

   Docs provide multiple copy-paste TypeScript/JS snippets (check, track, attach, gating) and a CLI/config flow that suggest a fast path to a working payment flow, and community comments (comm-2, comm-5) reflect developers finding it appealing to integrate quickly. However all examples are JS/TS only (no other languages), there's no explicit hands-on confirmation of a 'under a day' integration timeline, and separate security reports (comm-6/7) show at least one integration built from the docs' approach ended up with an IDOR vulnerability, suggesting the docs alone may not guarantee a fully working/secure flow without extra care. Missing for 10: multi-language code samples, an independent hands-on report confirming rapid end-to-end integration, and evidence the documented flow is secure by default.

   • [claimed-docs] “const response = await autumn.check({ customerId: "user_123", featureId: "messages" });”
   • [claimed-docs] “await autumn.track({ customerId: "user_or_org_id_from_auth", featureId: "messages", value: 1, });”
   • [claimed-docs] “The `atmn` CLI lets you define your pricing plans in code via an `autumn.config.ts` file, and sync them to Autumn with a single command.”
   • [claimed-docs] “You can preview your plans without pushing anything: bunx atmn preview”
   • [claimed-docs] “If you already have products created in the dashboard, run `atmn pull` to pull them into your local config.”
   • [claimed-docs] “Attaches a plan to a customer. Handles new subscriptions, upgrades and downgrades.”
   • [community] “"I've suffered so much with all the pricing changes I've been experimenting with (early stage solo founder)... I'm going to integrate autumn…”
   • [community] “"love this as someone who's been fixing the same billing bugs over and over and who sometimes finds stripe more complex than it should be." …”
   • [community] “Security concern raised: Autumn's server actions were public, unauthenticated routes, meaning "a simple curl request with a different custom…”

   proof ↗⚑ flag

   Airwallex~partialclaimed6/10

   There is a clear quickstart doc ('Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page') plus a self-serve sandbox and multiple integration options (Hosted Payment Page, Drop-in Element) with styling/config snippets, suggesting a fast path to a working payment flow. However, the evidence pack never shows actual copy-paste code samples in specific languages (e.g., Node, Python, PHP) or confirms multi-language SDK coverage, nor any independent developer report confirming a sub-day integration time. Missing for 10: concrete multi-language code snippets, language/SDK coverage, and independent hands-on confirmation of integration speed.

   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”
   • [claimed-docs] “Hosted Payment Page is a secure, pre-built payment page hosted by Airwallex that lets you accept multiple payment methods with a single inte…”
   • [claimed-docs] “Automatically adjusts input fields to collect information based on the payment method and country.”
   • [claimed-docs] “"Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulat…”
   • [claimed-docs] “Pass appearance and layout in createElement(...). For examples and supported values, see Customize style and appearance”

   proof ↗⚑ flag

Sandbox fidelity

1. developerBuild and test the entire payment flow in a sandbox or test mode that mirrors production, with test cards for every scenario including declines and disputes

   weight 3 · round to Airwallex
   Autumn—none0/10

   No evidence in the pack mentions a sandbox/test mode, test cards, or simulated decline/dispute scenarios; Autumn's docs cover CLI, config, gating, webhooks, and MCP but nothing about a testing environment mirroring production payment flows. Since Autumn sits atop Stripe, this is a fair and applicable axis for a billing product, but it's simply undocumented here.

   • [claimed-docs] “The `atmn` CLI lets you define your pricing plans in code via an `autumn.config.ts` file, and sync them to Autumn with a single command.”
   • [claimed-docs] “You can preview your plans without pushing anything: bunx atmn preview”
   • [claimed-docs] “If you already have products created in the dashboard, run `atmn pull` to pull them into your local config.”
   • [claimed-docs] “Attaches a plan to a customer. Handles new subscriptions, upgrades and downgrades.”

   proof ↗⚑ flag

   Airwallex~partialclaimed6/10

   Airwallex documents a full sandbox environment mirroring production (all products except Connected Account APIs), simulation docs for payments/payouts/deposits/issuing/risk, and a quickstart for an end-to-end sandbox payment flow, plus dispute-handling docs. However, there is no explicit mention of a documented set of test card numbers covering specific decline reason codes or dispute-triggering scenarios. missing for 10: documented test card numbers/scenarios for specific decline codes, explicit dispute-simulation test cards, independent developer confirmation of sandbox fidelity to production.

   • [claimed-docs] “"Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulat…”
   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”
   • [claimed-docs] “Airwallex will facilitate your dispute management step-by-step, but generally does not have influence over the outcome.”
   • [claimed-docs] “A second, integration-time MCP pair: "The Airwallex developer connectors connects AI coding agents — Cursor, Claude Code, Codex, and similar…”

   proof ↗⚑ flag

Refunds

1. finance-ops userIssue full or partial refunds from both the dashboard and the API

   weight 3 · round to Airwallex
   Autumn—none0/10

   No evidence pack items mention refunds at all—no dashboard refund UI, no refund API endpoint, or partial-refund logic; docs cover checks, tracking, attach/subscriptions, credit systems, and CLI/MCP but never refunds.

   ⚑ flag

   Airwallex~partialclaimed6/10

   Docs confirm refunds are a documented capability ('When a shopper returns goods or services, you can issue a refund to return their funds') and the CLI/API expose broad read/write access to Airwallex resources including presumably refunds, but no evidence explicitly confirms a dashboard refund UI or distinguishes full vs partial refund support at the API/dashboard level. Missing for 10: explicit documentation of partial refund amounts, dashboard UI screenshots/flow for issuing refunds, and independent/hands-on confirmation of both channels working.

   • [claimed-docs] “When a shopper returns goods or services, you can issue a refund to return their funds.”

   proof ↗⚑ flag

Multi currency

1. founderCharge customers in their local currencies and settle to my bank in mine with transparent FX handling

   weight 2 · round to Airwallex
   Autumn—none0/10

   No evidence in the pack addresses multi-currency charging, FX conversion, or settlement to a founder's home currency; documentation covers pricing models, metering, and Stripe catalog sync only. Community threads even highlight Autumn's dependency on Stripe alone with no other payment processors, but nothing on currency/FX handling either way.

   • [claimed-docs] “Catalog plans now accept a `processors` object so Autumn can reuse your existing Stripe catalog instead of minting new objects.”
   • [community] “Concern raised that Autumn is only built on Stripe, with no support for other payment providers like Paystack, which is needed for regions l…”

   proof ↗⚑ flag

   Airwallex✓fullclaimed8/10

   Airwallex directly supports charging customers via 160+ local payment methods and multi-currency pricing (accepting in local currencies), and its multi-currency Wallet enables like-for-like settlement without forced FX conversion, explicitly marketed as eliminating FX fees versus traditional gateways that force home-currency settlement. Transfers/payouts and invoicing further round out the collect-and-settle flow, backed by first-party docs. Missing for 10: independent/hands-on verification of actual FX rates charged and real-world transparency (e.g., third-party review of fee disclosure) beyond vendor documentation.

   • [claimed-docs] “Eliminates FX fees with like-for-like settlement: Unlike traditional gateways that settle global payments into your home currency, Airwallex…”
   • [claimed-docs] “The Multi-Currency Pricing API (MCP API) enables you to display prices and enable payment in your shoppers' preferred currencies, while also…”
   • [claimed-docs] “Generate invoices and digital payment links with over 160+ local payment methods”
   • [claimed-docs] “Airwallex Transfers allows you to move funds across the globe easily to your suppliers, employees, contractors and/or own bank accounts.”
   • [claimed-docs] “The Multi-Currency Pricing API (MCP API) enables you to display prices and enable payment in your shoppers' preferred currencies”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Airwallex
   Autumn~partialprobed6/10

   Autumn exposes a broad API (check, track, attach, credit systems, usage-based pricing) plus a CLI (`atmn push/pull/preview`) that can define and sync pricing config as code, and an MCP server for AI-native access to billing/customer/plan tools — strong evidence of API-driven control. However, the docs also show a 'pull' workflow for dashboard-created products, implying some setup still originates in the dashboard UI, and there's no explicit statement or independent test confirming full 1:1 parity between every UI action and API/CLI capability. Missing for 10: explicit parity documentation or proof that all dashboard-only actions (e.g., initial product/catalog creation, Stripe processor linking) are fully replicable via API/CLI without ever touching the UI, and independent verification of this parity.

   • [claimed-docs] “const response = await autumn.check({ customerId: "user_123", featureId: "messages" });”
   • [claimed-docs] “await autumn.track({ customerId: "user_or_org_id_from_auth", featureId: "messages", value: 1, });”
   • [claimed-docs] “Credit systems let you track actions with different credit costs from a single balance pool.”
   • [claimed-docs] “The `atmn` CLI lets you define your pricing plans in code via an `autumn.config.ts` file, and sync them to Autumn with a single command.”
   • [claimed-docs] “You can preview your plans without pushing anything: bunx atmn preview”
   • [claimed-docs] “Autumn MCP connects AI assistants to Autumn's billing, customer, plan, balance, and log tools.”
   • [claimed-docs] “If you already have products created in the dashboard, run `atmn pull` to pull them into your local config.”
   • [probe] “official MCP server documented at https://docs.useautumn.com/documentation/mcp”
   • [probe] “official CLI documented at https://docs.useautumn.com/cli/getting-started”

   proof ↗⚑ flag

   Airwallex~partialclaimed7/10

   Airwallex documents an extensive API surface plus a CLI that 'exposes a broad slice of the Airwallex API as terminal commands' and an AgentOS/MCP toolkit letting agents read balances, create beneficiaries, issue cards, and run workflows — strong evidence that most UI actions have programmatic equivalents. However, AgentOS explicitly ships with 'no money-out actions by default' as a safety guardrail, and Connected Account APIs are excluded from sandbox, indicating some UI-capable actions are deliberately restricted or gated via role/OAuth permissions rather than fully mirrored in the API/agent tooling. Missing for 10: confirmation that all money-movement and account-management UI actions are reachable via API without special unlocking, and independent/hands-on verification that the CLI/MCP truly cover 100% of UI functionality.

   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “"Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulat…”
   • [claimed-docs] “A scoped API key grants only the resource permissions you assign (Read or Write on specific APIs), instead of full account access.”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round drawn
   Autumn—none0/10

   Autumn's docs show CLI sync/pull for pricing config (autumn.config.ts) and webhooks for event data, but there is no documented feature for exporting all customer/usage/billing data in an open format to allow a user or team to leave the platform. missing for 10: a documented full data-export or account-portability feature, open-format bulk export of customer/usage records, evidence of data portability upon offboarding.

   • [claimed-docs] “The `atmn` CLI lets you define your pricing plans in code via an `autumn.config.ts` file, and sync them to Autumn with a single command.”
   • [claimed-docs] “If you already have products created in the dashboard, run `atmn pull` to pull them into your local config.”
   • [claimed-docs] “Fired whenever a customer's plans change — new subscriptions, upgrades, downgrades, etc.”

   proof ↗⚑ flag

   Airwallex—none0/10

   Airwallex is a financial platform (payments, treasury, billing) with an API/CLI/MCP for account operations, but there is no evidence of a bulk data export feature or open-format data portability that would let a user export all their account data and leave the platform. The APIs allow reading individual resources but no documented full-account export/migration tool is mentioned.

   ⚑ flag

Marketplace

1. developerBuild a marketplace or platform that onboards sellers, splits payments between parties, and pays out to each seller

   weight 2 · round to Airwallex
   Autumn—none0/10

   Autumn's evidence focuses entirely on single-party SaaS billing—metering, plans, entitlements, customer subscriptions via Stripe—with no mention of multi-party marketplace features like seller onboarding, payment splitting, or payouts (e.g., Stripe Connect-style functionality). No evidence pack item addresses marketplace/platform payment distribution.

   ⚑ flag

   Airwallex✓fullclaimed8/10

   Airwallex explicitly documents programmatic creation of connected accounts for businesses/individuals with financial capabilities (marketplace onboarding), plus Transfers/payouts to move funds to suppliers/contractors, and multi-currency wallet settlement — the core building blocks for onboarding sellers and paying them out. Payment splitting isn't explicitly named as a feature but is a natural extension of connected accounts + transfers, and sandbox/webhooks support building and testing such flows end-to-end. Missing for 10: explicit documentation of a 'split payment' or marketplace-specific API/feature, and independent case studies of marketplaces built on Airwallex.

   • [claimed-docs] “Programmatically create connected accounts for businesses and individuals, and enable them with rich financial capabilities.”
   • [claimed-docs] “Airwallex Transfers allows you to move funds across the globe easily to your suppliers, employees, contractors and/or own bank accounts.”
   • [claimed-docs] “Eliminates FX fees with like-for-like settlement: Unlike traditional gateways that settle global payments into your home currency, Airwallex…”
   • [claimed-docs] “Webhooks enable Airwallex to send instant, real-time push notifications to your application when events occur in your Airwallex account.”
   • [claimed-docs] “"Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulat…”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Autumn—none0/10

   Autumn is a billing/entitlements layer for AI and SaaS products; there is no mention anywhere in the evidence pack of data residency, region selection, or data storage location controls. This is an applicable axis for a data-handling SaaS product, but no evidence supports it.

   ⚑ flag

   Airwallex—none0/10

   No documentation describes a data residency/region-selection feature letting users choose where their data is stored; the community item raises concerns about China/HK data access but does not confirm or deny any residency-choice capability.

   ⚑ flag