Square vs Autumn

Agent access

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

   weight 2 · round to Square
   Square✓fullprobed9/10

   Square publishes a live, verified llms.txt (probe confirms HTTP 200) explicitly designed for AI agents, with agent-specific guidance on idempotency keys, pagination, and instructions to fetch llms-full.txt or per-page .md files instead of loading the whole corpus; docs pages also render as raw markdown. This is corroborated by an independent probe hit. missing for 10: no independent third-party (non-vendor) confirmation that agents successfully consume this file in practice, and the docs.md/openapi fallback endpoints 404 rather than existing.

   • [claimed-docs] “Square's developer llms.txt declares the platform "Designed to be consumable by both human developers and AI agents" and ships explicit agen…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.squareup.com/llms.txt # Square Developer Platform > Square APIs and SDKs for accepting paymen…”
   • [probe] “PROBE docs-md: HTTP 404 at https://developer.squareup.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.squareup.com/openapi.json, https://developer.squareup.com/swagger.json, https://de…”
   • [claimed-docs] “The Square MCP server connects your AI tools directly to the full Square API platform, giving you programmatic access to everything the APIs…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Square
   Square~partialclaimed6/10

   Square's platform is fundamentally API/SDK-driven (Node.js SDK, REST/GraphQL APIs, idempotency keys) and ships a dedicated Sandbox environment explicitly for testing automation, plus a local MCP server mode (`npx square-mcp-server start`) with env-var controls like SANDBOX=true and DISALLOW_WRITES=true that suit scripted/CI use. However, there is no explicit CI/CD pipeline documentation, GitHub Actions integration, or hands-on evidence of running Square headlessly in an actual CI pipeline. Missing for 10: explicit CI/pipeline integration guides, documented headless automation examples beyond sandbox testing, independent confirmation of CI usage.

   • [claimed-docs] “[Sandbox Payments](/docs/devtools/sandbox/payments)”
   • [claimed-docs] “Square Sandbox”
   • [claimed-docs] “Idempotency”
   • [claimed-docs] “The Square MCP server (github.com/square/square-mcp-server, Beta) uses a discovery-oriented tool design — `get_service_info` ("Discover meth…”
   • [github] “const client = new SquareClient({ token: "YOUR_TOKEN" });”
   • [github] “The Square TypeScript library provides convenient access to the Square APIs from TypeScript.”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Square
   Square✓fullprobed9/10

   Square documents an official hosted remote MCP server (mcp.squareup.com/mcp) with OAuth-based scoped auth plus an open-source local server, both exposing the full Square API platform, and provides setup guidance for Claude, Cursor, Windsurf, Goose. This is well-documented first-party evidence with a public GitHub repo, though independent hands-on user validation is limited. Missing for 10: independent/community confirmation of real-world agent usage beyond vendor docs.

   • [claimed-docs] “The Square MCP server connects your AI tools directly to the full Square API platform, giving you programmatic access to everything the APIs…”
   • [claimed-docs] “npx square-mcp-server start”
   • [claimed-docs] “"The Square remote MCP server is hosted at: https://mcp.squareup.com/mcp... Square recommends using the remote MCP server, which supports OA…”
   • [claimed-docs] “The Square MCP server (github.com/square/square-mcp-server, Beta) uses a discovery-oriented tool design — `get_service_info` ("Discover meth…”
   • [claimed-docs] “The remote MCP is recommended as it uses OAuth authentication, allowing you to log in with your Square account directly without having to cr…”
   • [probe] “official MCP server documented at https://developer.squareup.com/docs/mcp”

   proof ↗⚑ flag

   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

4. ai-native userUse an official CLI

   weight 2 · round to Autumn
   Square—none0/10

   Square's evidence shows an MCP server, SDKs, GraphQL, and API Explorer, but no dedicated official CLI tool (e.g., a 'square' command-line utility for managing resources, testing APIs, or agentic workflows) is documented anywhere in the pack. The `npx square-mcp-server start` command is for launching an MCP server, not a general-purpose CLI.

   • [claimed-docs] “npx square-mcp-server start”
   • [claimed-docs] “The Square MCP server (github.com/square/square-mcp-server, Beta) uses a discovery-oriented tool design — `get_service_info` ("Discover meth…”
   • [claimed-docs] “API Explorer is an interactive web application you can use to build, view, and send HTTP requests that call Square APIs.”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Square
   Square✓fullprobed9/10

   Square publishes an extensive documented public REST API (payments, refunds, disputes, subscriptions, invoices, webhooks) plus GraphQL, SDKs (e.g. square-nodejs-sdk), API Explorer, sandbox testing, OAuth scopes, and an explicit llms.txt/llms-full.txt agent-consumption index with agent-specific guidance (idempotency keys, pagination) — directly supporting AI-native, agentic driving of the product. Missing for 10: no public OpenAPI/swagger spec discoverable (probe returned 404s), and no independent third-party corroboration beyond vendor docs.

   • [claimed-docs] “The Square MCP server connects your AI tools directly to the full Square API platform, giving you programmatic access to everything the APIs…”
   • [claimed-docs] “Square's developer llms.txt declares the platform "Designed to be consumable by both human developers and AI agents" and ships explicit agen…”
   • [claimed-docs] “Square ships a GraphQL API alongside REST: "GraphQL queries can improve performance and reduce development time by letting you request exact…”
   • [claimed-docs] “"API Explorer is an interactive web application you can use to build, view, and send HTTP requests that call Square APIs. API Explorer lets …”
   • [claimed-docs] “Square access is scope-controlled: "Access tokens are credentials that allow applications to securely interact with Square APIs. An access t…”
   • [github] “The Square TypeScript library provides convenient access to the Square APIs from TypeScript.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.squareup.com/llms.txt # Square Developer Platform > Square APIs and SDKs for accepting paymen…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.squareup.com/openapi.json, https://developer.squareup.com/swagger.json, https://de…”
   • [claimed-docs] “[Sandbox Payments](/docs/devtools/sandbox/payments)”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Square
   Square✓fullclaimed8/10

   Square supports OAuth with per-permission scopes for granular access control, and its remote MCP server explicitly uses OAuth login to 'authorize only the scopes your application needs' for agent connections; the local MCP server also supports a DISALLOW_WRITES read-only mode and SANDBOX flag for least-privilege agent setups. Missing for 10: no independent/hands-on verification of scope granularity in practice, and no explicit documentation of fine-grained scope lists specifically tailored for agent use cases beyond general OAuth scopes.

   • [claimed-docs] “Square access is scope-controlled: "Access tokens are credentials that allow applications to securely interact with Square APIs. An access t…”
   • [claimed-docs] “"The Square remote MCP server is hosted at: https://mcp.squareup.com/mcp... Square recommends using the remote MCP server, which supports OA…”
   • [claimed-docs] “The Square MCP server (github.com/square/square-mcp-server, Beta) uses a discovery-oriented tool design — `get_service_info` ("Discover meth…”
   • [claimed-docs] “Use the OAuth API to connect your application to a seller's account using OAuth.”
   • [claimed-docs] “The remote MCP is recommended as it uses OAuth authentication, allowing you to log in with your Square account directly without having to cr…”

   proof ↗⚑ flag

   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

7. ai-native userBuild against official SDKs

   weight 2 · round to Square
   Square✓fullclaimed8/10

   Square ships official, first-party SDKs (e.g. square-nodejs-sdk/TypeScript library) with documented code examples for payments, versioning, and client setup, plus broader API coverage (REST, GraphQL, OAuth, webhooks, sandbox) that AI-native developers can build against, reinforced by an explicit llms.txt/agent-guidance file and an official MCP server for programmatic AI tool access. Missing for 10: independent/hands-on developer corroboration of SDK quality beyond GitHub README snippets, and broader multi-language SDK evidence beyond Node/TypeScript.

   • [github] “await client.payments.create({ sourceId: "ccof:GaJGNaZa8x4OgDJn4GB",”
   • [github] “await client.payments.create(..., { version: "2024-05-04" // override the version used })”
   • [github] “const client = new SquareClient({ token: "YOUR_TOKEN" });”
   • [github] “The Square TypeScript library provides convenient access to the Square APIs from TypeScript.”
   • [claimed-docs] “Square's developer llms.txt declares the platform "Designed to be consumable by both human developers and AI agents" and ships explicit agen…”
   • [claimed-docs] “The Square MCP server connects your AI tools directly to the full Square API platform, giving you programmatic access to everything the APIs…”
   • [claimed-docs] “"The Square remote MCP server is hosted at: https://mcp.squareup.com/mcp... Square recommends using the remote MCP server, which supports OA…”
   • [claimed-docs] “Square ships a GraphQL API alongside REST: "GraphQL queries can improve performance and reduce development time by letting you request exact…”
   • [claimed-docs] “Use the OAuth API to connect your application to a seller's account using OAuth.”

   proof ↗⚑ flag

   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

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Square
   Square✓fullclaimed8/10

   Square provides a documented Webhooks system with subscribing to event notifications, verifying/validating events, sandbox testing, and event logs — a standard webhook mechanism usable by any AI-native integration (including via its MCP server/API access). missing for 10: no explicit example of an AI agent programmatically subscribing to webhooks, and no independent hands-on corroboration beyond first-party docs.

   • [claimed-docs] “[Subscribe to Event Notifications](/docs/webhooks/step2subscribe)”
   • [claimed-docs] “[Verify and Validate an Event Notification](/docs/webhooks/step3validate)”
   • [claimed-docs] “Square Webhooks”
   • [claimed-docs] “"API Explorer is an interactive web application you can use to build, view, and send HTTP requests that call Square APIs. API Explorer lets …”

   proof ↗⚑ flag

   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

Agentic features

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

   weight 2 · round to Square
   Square~partialclaimed7/10

   Square ships a first-party beta 'Square AI' seller assistant for natural-language queries over sales/inventory data, and a documented MCP server (local + hosted, OAuth-scoped) that lets AI agents like Claude/Cursor issue natural-language-driven API calls (payments, orders, catalog, etc.) via discovery tools. This gives real NL-command operability, but it's split across a beta insights assistant (limited to analysis/reporting) and third-party agent integration (MCP) rather than a single native NL control surface for all product actions. Missing for 10: evidence that Square AI itself can execute broad write/operational commands (not just analysis), and independent/hands-on validation of MCP agent workflows beyond vendor docs.

   • [claimed-docs] “Square AI (Beta) is an in-product assistant for sellers: "Square AI is built into your everyday tools to pull game-changing insights from yo…”
   • [claimed-docs] “"The Square remote MCP server is hosted at: https://mcp.squareup.com/mcp... Square recommends using the remote MCP server, which supports OA…”
   • [claimed-docs] “The Square MCP server (github.com/square/square-mcp-server, Beta) uses a discovery-oriented tool design — `get_service_info` ("Discover meth…”
   • [claimed-docs] “Square's developer llms.txt declares the platform "Designed to be consumable by both human developers and AI agents" and ships explicit agen…”
   • [claimed-docs] “Square AI | Unlock Growth with AI-Powered Insights”

   proof ↗⚑ flag

   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

Api quality

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

   weight 2 · round to Square
   Square✓fullprobed8/10

   Square documents a genuine interactive API Explorer that builds/sends real HTTP requests against Sandbox or production resources (customers, orders, catalog), plus a GraphQL Explorer for runnable queries, giving developers a hands-on interactive reference. Missing for 10: no independent/third-party corroboration of the API Explorer's usability and no discoverable OpenAPI spec (probe confirms 404s), so tooling depth is documented only by the vendor.

   • [claimed-docs] “"API Explorer is an interactive web application you can use to build, view, and send HTTP requests that call Square APIs. API Explorer lets …”
   • [claimed-docs] “API Explorer is an interactive web application you can use to build, view, and send HTTP requests that call Square APIs.”
   • [claimed-docs] “API Explorer lets you test your requests using actual Sandbox or production resources in your account such as customers, orders, and catalog…”
   • [claimed-docs] “Square ships a GraphQL API alongside REST: "GraphQL queries can improve performance and reduce development time by letting you request exact…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.squareup.com/openapi.json, https://developer.squareup.com/swagger.json, https://de…”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Square—none0/10

   No documentation page or probe in the evidence pack shows a downloadable OpenAPI/Swagger spec; explicit probes for common OpenAPI paths (openapi.json, swagger.json, etc.) all returned 404, and no docs page links to a machine-readable spec file (only an interactive API Explorer, GraphQL schema, and SDKs are mentioned).

   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.squareup.com/openapi.json, https://developer.squareup.com/swagger.json, https://de…”
   • [probe] “PROBE docs-md: HTTP 404 at https://developer.squareup.com/docs.md”
   • [claimed-docs] “API Explorer is an interactive web application you can use to build, view, and send HTTP requests that call Square APIs.”
   • [claimed-docs] “"API Explorer is an interactive web application you can use to build, view, and send HTTP requests that call Square APIs. API Explorer lets …”

   proof ↗⚑ flag

   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

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

   weight 1 · round to Square
   Square✓fullclaimed8/10

   Square documents a dedicated Sandbox environment (square-docs-21, square-docs-40) with sandbox testing for disputes/payments, and the API Explorer and MCP server explicitly support running against Sandbox resources instead of production (square-docs-48, square-supp-api-explorer, square-supp-mcp-remote with 'run a local instance configured to access a seller's Sandbox environment', and SANDBOX=true env var in square-supp-mcp-tools). This directly enables AI-native agents to test without touching production data. Missing for 10: independent/hands-on confirmation that sandbox parity with production is complete and that MCP sandbox mode is broadly validated by third-party users rather than only vendor docs.

   • [claimed-docs] “[Sandbox Payments](/docs/devtools/sandbox/payments)”
   • [claimed-docs] “Square Sandbox”
   • [claimed-docs] “API Explorer lets you test your requests using actual Sandbox or production resources in your account such as customers, orders, and catalog…”
   • [claimed-docs] “"API Explorer is an interactive web application you can use to build, view, and send HTTP requests that call Square APIs. API Explorer lets …”
   • [claimed-docs] “"The Square remote MCP server is hosted at: https://mcp.squareup.com/mcp... Square recommends using the remote MCP server, which supports OA…”
   • [claimed-docs] “The Square MCP server (github.com/square/square-mcp-server, Beta) uses a discovery-oriented tool design — `get_service_info` ("Discover meth…”
   • [claimed-docs] “[Test in the Sandbox](/docs/disputes-api/sandbox-testing)”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Square
   Square~partialclaimed5/10

   Square's API clearly supports date-based versioning — SDK calls can override the API version ("version: '2024-05-04'") and the MCP tool documents a SQUARE_VERSION pinning control — showing a live, explicit versioning scheme. However, no evidence in the pack shows a documented deprecation policy (timelines, sunset notices, migration guides) that would let an AI-native user reliably plan around version lifecycle changes. Missing for 10: an explicit deprecation/sunset policy document, version changelog, or migration guidance referenced anywhere in the evidence.

   • [github] “await client.payments.create(..., { version: "2024-05-04" // override the version used })”
   • [claimed-docs] “The Square MCP server (github.com/square/square-mcp-server, Beta) uses a discovery-oriented tool design — `get_service_info` ("Discover meth…”
   • [claimed-docs] “Idempotency”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Square—none0/10

   The evidence pack shows GraphQL reducing multiple API calls into one query (square-docs-41/square-supp-graphql) and a generic MCP `make_api_request` tool, but no documentation or example of true bulk/batch operations (e.g., batch-upserting catalog items, bulk inventory adjustments, or bulk order processing) that would let an AI-native user act across many items in one call.

   • [claimed-docs] “One GraphQL query can retrieve data that requires multiple Square API calls.”
   • [claimed-docs] “Square ships a GraphQL API alongside REST: "GraphQL queries can improve performance and reduce development time by letting you request exact…”
   • [claimed-docs] “The Square MCP server (github.com/square/square-mcp-server, Beta) uses a discovery-oriented tool design — `get_service_info` ("Discover meth…”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Square~partialclaimed4/10

   Square exposes webhooks/event notifications that let a developer wire custom code to react to events (square-docs-19, square-docs-39) and has narrow built-in 'custom rules and alerts' for fraud/risk management (square-docs-28), but there is no general-purpose, user-definable rules/automation engine ('if event X then action Y') across the platform's business events. Missing for 10: a documented no-code/low-code rule builder, broader event-trigger coverage beyond payments/fraud, and evidence of the AI-native user directly authoring such rules (vs. developers writing webhook handlers).

   • [claimed-docs] “[Subscribe to Event Notifications](/docs/webhooks/step2subscribe)”
   • [claimed-docs] “Square Webhooks”
   • [claimed-docs] “Prevent loss online. Get insights into payment fraud patterns, and set custom rules and alerts to manage risk.”
   • [claimed-docs] “[Verify and Validate an Event Notification](/docs/webhooks/step3validate)”

   proof ↗⚑ flag

   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

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 drawn
   Square—none0/10

   Square documents webhooks, a Subscriptions API, and Payments API, but the evidence pack has no mention of failed-payment monitoring, automated retry logic, or dunning outreach features/APIs; the community note even flags subscriptions as a historical gap. An agent could theoretically be built on top of webhooks, but no first-party capability or workflow for this specific story is evidenced.

   • [claimed-docs] “[Subscribe to Event Notifications](/docs/webhooks/step2subscribe)”
   • [claimed-docs] “Subscriptions API”
   • [community] “Does square have a way to handle subscriptions yet? Seems to be the only thing they are missing”

   proof ↗⚑ flag

   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

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 Square
   Square~partialclaimed7/10

   Square's remote/local MCP server (square-mcp-server) exposes a discovery-oriented `make_api_request` tool spanning Catalog, Checkout, and Payments services, and Square's llms.txt explicitly frames the API as agent-consumable with idempotency-key guidance for writes — together these support an agent creating a catalog item (product), its price, and a payment link (via Checkout/Payment Links API) in one session using a single access token/OAuth session. However, no evidence pack item shows an actual end-to-end worked example or transcript of an agent doing product+price+payment-link creation in one session, and Payment Links API itself is not separately documented in the pack (only Checkout/Catalog mentioned generically). missing for 10: an explicit end-to-end tutorial/example chaining catalog item + price + payment link creation, and independent/hands-on confirmation the MCP tool can complete this multi-step flow in a single session.

   • [claimed-docs] “The Square MCP server (github.com/square/square-mcp-server, Beta) uses a discovery-oriented tool design — `get_service_info` ("Discover meth…”
   • [claimed-docs] “"The Square remote MCP server is hosted at: https://mcp.squareup.com/mcp... Square recommends using the remote MCP server, which supports OA…”
   • [claimed-docs] “Square's developer llms.txt declares the platform "Designed to be consumable by both human developers and AI agents" and ships explicit agen…”
   • [claimed-docs] “The Square MCP server connects your AI tools directly to the full Square API platform, giving you programmatic access to everything the APIs…”
   • [claimed-docs] “Learn how to nest modifier lists under modifiers with the Catalog API to build multi-step customization flows”

   proof ↗⚑ flag

   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

Subscriptions

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

   weight 2 · round drawn
   Square—none0/10

   Square documents a Subscriptions API and general payments/invoicing capabilities, but no evidence describes automated retry logic, smart dunning, or recovery emails for failed subscription payments; a community comment even questions whether Square's subscription handling is mature.

   • [claimed-docs] “Subscriptions API”
   • [community] “Does square have a way to handle subscriptions yet? Seems to be the only thing they are missing”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Autumn
   Square~partialcommunity5/10

   Square documents a dedicated Subscriptions API (square-docs-23), confirming recurring billing support, but the evidence pack gives no detail on plan configuration, trial periods, upgrade/downgrade flows, or proration logic. An old community comment (square-comm-1) also shows subscriptions were historically seen as a gap, though this predates the current API's existence. Missing for 10: documented support for trials, plan upgrades/downgrades, and proration calculations; independent/hands-on confirmation these work as expected.

   • [claimed-docs] “Subscriptions API”
   • [community] “Does square have a way to handle subscriptions yet? Seems to be the only thing they are missing”

   proof ↗⚑ flag

   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

Card acceptance

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

   weight 3 · round to Square
   Square✓fullclaimed7/10

   Square documents self-serve signup with a Web Payments SDK, Card Payments API, and prebuilt eCommerce integrations that 'can be completed in just a few clicks,' plus a Sandbox for immediate testing—consistent with a founder going from signup to live online card acceptance quickly without sales calls. Missing for 10: explicit 'time-to-first-payment' documentation or independent/hands-on account of actual signup-to-live timing.

   • [claimed-docs] “Web Payments SDK”
   • [claimed-docs] “[Card Payments](/docs/payments-api/take-payments/card-payments)”
   • [claimed-docs] “Square has prebuilt online payment solutions with top eCommerce providers. Most connections can be completed in just a few clicks.”
   • [claimed-docs] “[Sandbox Payments](/docs/devtools/sandbox/payments)”
   • [claimed-docs] “Take payments in person and online. Securely save recurring payment methods. Easily sync sales, inventory, and customer data with your Squ…”

   proof ↗⚑ flag

   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

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 Square
   Square✓fullclaimed8/10

   Square's Web Payments SDK is explicitly documented for embedding customizable card/ACH/Cash App/Afterpay payment components directly into a developer's own site rather than redirecting to a hosted checkout page, and this is backed by a full Payments API, Node SDK, and sandbox testing tools. missing for 10: no independent/hands-on developer report confirming ease of customization or styling flexibility beyond first-party docs.

   • [claimed-docs] “Web Payments SDK”
   • [claimed-docs] “[Card Payments](/docs/payments-api/take-payments/card-payments)”
   • [claimed-docs] “[ACH Bank Transfer Payment](/docs/payments-api/take-payments/ach-payments)”
   • [claimed-docs] “[Afterpay and Clearpay Payments](/docs/payments-api/take-payments/afterpay-payments)”
   • [claimed-docs] “[Cash App Payments](/docs/payments-api/take-payments/cash-app-payments)”
   • [github] “await client.payments.create({ sourceId: "ccof:GaJGNaZa8x4OgDJn4GB",”
   • [claimed-docs] “[Sandbox Payments](/docs/devtools/sandbox/payments)”
   • [claimed-docs] “Take payments in person and online. Securely save recurring payment methods. Easily sync sales, inventory, and customer data with your Squ…”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Square—none0/10

   The evidence pack covers Square's Payments API, Web Payments SDK (embeddable UI), Invoices, and various backend APIs, but never mentions a vendor-hosted, conversion-optimized checkout page (e.g., a Checkout API or Payment Links) that a developer could redirect customers to without building payment UI. Web Payments SDK (square-docs-31) actually requires building your own UI, the opposite of this story.

   ⚑ flag

   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

No code selling

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

   weight 2 · round drawn
   Square—none0/10

   The evidence pack focuses almost entirely on Square's developer APIs, SDKs, and MCP/AI tooling for building payment integrations, not on the no-code merchant dashboard feature of generating a shareable payment link. No citation mentions 'Payment Links' or a dashboard flow for founders to create a link without coding.

   ⚑ flag

   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

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 Square
   Square~partialclaimed6/10

   Square's Payments API and Web Payments SDK docs confirm ACH bank transfers, Afterpay/Clearpay (BNPL), Cash App, and card payments in one integration, but the evidence never explicitly documents Apple Pay or Google Pay wallet support alongside these, nor generic 'bank redirect' methods beyond ACH. missing for 10: explicit Apple Pay/Google Pay digital wallet docs, broader local bank-redirect methods (iDEAL, etc.), and independent confirmation that all these methods coexist in a single unified checkout flow.

   • [claimed-docs] “[ACH Bank Transfer Payment](/docs/payments-api/take-payments/ach-payments)”
   • [claimed-docs] “[Afterpay and Clearpay Payments](/docs/payments-api/take-payments/afterpay-payments)”
   • [claimed-docs] “[Cash App Payments](/docs/payments-api/take-payments/cash-app-payments)”
   • [claimed-docs] “Web Payments SDK”
   • [claimed-docs] “[Card Payments](/docs/payments-api/take-payments/card-payments)”
   • [claimed-docs] “ACH Bank Transfer Payment”
   • [claimed-docs] “Afterpay and Clearpay Payments”
   • [claimed-docs] “Cash App Payments”

   proof ↗⚑ flag

   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

Integration reliability

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

   weight 2 · round to Square
   Square✓fullclaimed8/10

   Square has a dedicated 'Idempotency' documentation page and its agent-facing llms.txt explicitly states 'every write endpoint accepts an idempotency key' to prevent duplicate charges from retries. This directly matches the story's core requirement. Missing for 10: independent/hands-on developer confirmation of idempotency behavior under real network-failure retries, and more detail on key expiration/scope beyond the doc title.

   • [claimed-docs] “Idempotency”
   • [claimed-docs] “Square's developer llms.txt declares the platform "Designed to be consumable by both human developers and AI agents" and ships explicit agen…”

   proof ↗⚑ flag

   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

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 Square
   Square~partialclaimed5/10

   Square documents webhook subscriptions and signature verification/validation of event notifications, plus mentions of webhook event logs in the dev tools, which covers signed delivery and basic observability. However, the evidence pack contains no explicit documentation of automatic retry behavior or an event replay mechanism, which are core parts of the story. missing for 10: documented automatic retry policy for failed webhook deliveries, explicit event replay/resend capability, independent confirmation of retry/replay behavior.

   • [claimed-docs] “[Subscribe to Event Notifications](/docs/webhooks/step2subscribe)”
   • [claimed-docs] “[Verify and Validate an Event Notification](/docs/webhooks/step3validate)”
   • [claimed-docs] “Square Webhooks”
   • [claimed-docs] “"API Explorer is an interactive web application you can use to build, view, and send HTTP requests that call Square APIs. API Explorer lets …”

   proof ↗⚑ flag

   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

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
   Square~partialclaimed6/10

   Square provides extensive first-party docs for card, ACH, Cash App, Afterpay payments, plus sandbox testing and idempotency guidance, and the Node.js/TypeScript SDK shows concrete copy-paste code (client.payments.create). This supports fast integration, but the evidence pack shows only one language's SDK example, no explicit 'under a day' quickstart guide, and no cross-language parity proof (Python, Java, PHP, etc.) or independent developer testimony confirming a same-day integration timeline. missing for 10: multi-language copy-paste examples, an explicit time-to-integrate quickstart, independent hands-on confirmation of a sub-day integration.

   • [claimed-docs] “[Card Payments](/docs/payments-api/take-payments/card-payments)”
   • [claimed-docs] “[Sandbox Payments](/docs/devtools/sandbox/payments)”
   • [claimed-docs] “Idempotency”
   • [github] “await client.payments.create({ sourceId: "ccof:GaJGNaZa8x4OgDJn4GB",”
   • [github] “const client = new SquareClient({ token: "YOUR_TOKEN" });”
   • [github] “The Square TypeScript library provides convenient access to the Square APIs from TypeScript.”
   • [claimed-docs] “Square Sandbox”

   proof ↗⚑ flag

   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

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 Square
   Square✓fullclaimed7/10

   Square documents a dedicated Sandbox environment (square-docs-21, square-docs-40) with Sandbox Payments docs, sandbox-specific dispute testing (square-docs-16), and an API Explorer that lets developers run requests against actual Sandbox or production resources (square-docs-48, square-supp-api-explorer), covering the core sandbox/test-mode workflow for payments and disputes. missing for 10: explicit enumeration of test card numbers for every decline/dispute scenario and independent developer corroboration that the sandbox fully mirrors production edge cases.

   • [claimed-docs] “[Sandbox Payments](/docs/devtools/sandbox/payments)”
   • [claimed-docs] “Square Sandbox”
   • [claimed-docs] “[Test in the Sandbox](/docs/disputes-api/sandbox-testing)”
   • [claimed-docs] “API Explorer lets you test your requests using actual Sandbox or production resources in your account such as customers, orders, and catalog…”
   • [claimed-docs] “"API Explorer is an interactive web application you can use to build, view, and send HTTP requests that call Square APIs. API Explorer lets …”

   proof ↗⚑ flag

   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

Refunds

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

   weight 3 · round to Square
   Square~partialclaimed7/10

   Square documents a dedicated Refunds API supporting both linked and unlinked refunds (full/partial refunds for existing or off-platform payments), which covers the API side, and the dashboard is implied via the broader Square seller product but not explicitly documented for refund issuance in the evidence pack. missing for 10: explicit dashboard UI documentation/screenshots showing refund issuance from the Seller Dashboard, and confirmation of partial-amount refund support in docs text.

   • [claimed-docs] “[Refund Payments](/docs/payments-api/refund-payments)”
   • [claimed-docs] “[Process an Unlinked Refund](/docs/refunds-api/unlinked-refunds)”
   • [claimed-docs] “Refund Payments”

   proof ↗⚑ flag

   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

Multi currency

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

   weight 2 · round drawn
   Square—none0/10

   The evidence pack contains no mention of multi-currency charging, FX conversion, or cross-currency settlement anywhere in Square's docs, GraphQL/REST APIs, MCP server, or payments pages — all payment method docs (cards, ACH, Afterpay, Cash App) are silent on currency handling. This is a fair axis for a payments platform, so absence of evidence yields none rather than na.

   • [claimed-docs] “[Card Payments](/docs/payments-api/take-payments/card-payments)”
   • [claimed-docs] “[ACH Bank Transfer Payment](/docs/payments-api/take-payments/ach-payments)”
   • [claimed-docs] “[Afterpay and Clearpay Payments](/docs/payments-api/take-payments/afterpay-payments)”
   • [claimed-docs] “[Cash App Payments](/docs/payments-api/take-payments/cash-app-payments)”
   • [claimed-docs] “Payouts API”
   • [claimed-docs] “Take payments in person and online. Securely save recurring payment methods. Easily sync sales, inventory, and customer data with your Squ…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Square
   Square~partialclaimed7/10

   Square's developer platform exposes an extensive set of APIs (payments, refunds, disputes, invoices, subscriptions, payouts, webhooks, OAuth, GraphQL, catalog/customers/orders/inventory/labor) plus an MCP server giving 'programmatic access to everything the APIs offer', suggesting broad UI/API parity for core commerce and back-office functions. However, some UI-only surfaces (e.g., the in-product Square AI seller assistant, POS idle-screen customization, dashboard reporting UI) are not shown to have full API equivalents, and there is no explicit vendor or independent claim of 100% UI-API parity. missing for 10: an explicit parity statement or audit confirming every UI feature (e.g., Square AI insights, POS-specific dashboard views) is fully API-accessible, and independent/hands-on verification of edge-case coverage.

   • [claimed-docs] “Payouts API”
   • [claimed-docs] “Invoices API”
   • [claimed-docs] “Subscriptions API”
   • [claimed-docs] “Disputes API”
   • [claimed-docs] “Square Webhooks”
   • [claimed-docs] “One GraphQL query can retrieve data that requires multiple Square API calls.”
   • [claimed-docs] “Use the OAuth API to connect your application to a seller's account using OAuth.”
   • [claimed-docs] “The Square MCP server connects your AI tools directly to the full Square API platform, giving you programmatic access to everything the APIs…”
   • [claimed-docs] “The Square MCP server (github.com/square/square-mcp-server, Beta) uses a discovery-oriented tool design — `get_service_info` ("Discover meth…”
   • [claimed-docs] “Square AI (Beta) is an in-product assistant for sellers: "Square AI is built into your everyday tools to pull game-changing insights from yo…”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Square—none0/10

   Square's docs describe extensive APIs to create/read individual objects (payments, customers, orders, catalog) and even an MCP/GraphQL layer, but there is no evidence of a bulk data-export feature, standard open-format export (CSV/JSON dump), or documented account-closure/data-portability process letting a user take all their data and leave.

   ⚑ flag

   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

3. ai-native userRead the product's source under an open license

   weight 2 · round to Autumn
   Square—none0/10

   Square is a closed-source SaaS payments platform; the evidence only shows open-source client SDKs (square-nodejs-sdk) and an MCP server wrapper on GitHub, not the core product/platform source under an open license. No documentation states Square's actual service code is open-sourced or licensed for public reading.

   • [github] “The Square TypeScript library provides convenient access to the Square APIs from TypeScript.”
   • [claimed-docs] “npx square-mcp-server start”
   • [claimed-docs] “The Square MCP server (github.com/square/square-mcp-server, Beta) uses a discovery-oriented tool design — `get_service_info` ("Discover meth…”

   proof ↗⚑ flag

   Autumn~partialprobed3/10

   The only evidence is a fragment from Autumn's llms.txt describing it as 'Drop-in, open-source control layer for AI and Sa[aS]', suggesting an open-source posture, but there is no link to an actual repository, license file, or license type (e.g., MIT/Apache) in the evidence pack, and no independent confirmation of a public code repo. Missing for 10: a direct GitHub/source repo link, an explicit license name/file, and corroboration that the full source (not just docs) is publicly readable.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.useautumn.com/llms.txt # Autumn - [Welcome to Autumn](https://docs.useautumn.com/welcome.md): Drop…”

   proof ↗⚑ 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 Square
   Square~partialclaimed6/10

   Square provides the core building blocks for a marketplace: OAuth to onboard sellers to their own Square accounts (square-docs-42, square-docs-51), the OAuth access-token scope model (square-supp-oauth-scopes), Payments API with 'Collect Application Fees' for platform fee splitting (square-docs-37), and a Payouts API for disbursing funds to sellers (square-docs-17). However, the evidence never documents a unified 'split payment across multiple parties in one transaction' primitive or destination-account payout routing akin to Stripe Connect transfers—application fees and payouts appear as separate mechanisms rather than an integrated marketplace split-and-payout flow, and there's no dedicated marketplace/platform guide or case study. missing for 10: explicit multi-party split-payment/transfer API documentation, an end-to-end marketplace onboarding+split+payout guide, and independent/hands-on validation that this pattern works in production.

   • [claimed-docs] “Use the OAuth API to connect your application to a seller's account using OAuth.”
   • [claimed-docs] “multi-tenant applications that serve multiple sellers should use OAuth access tokens”
   • [claimed-docs] “Square access is scope-controlled: "Access tokens are credentials that allow applications to securely interact with Square APIs. An access t…”
   • [claimed-docs] “Collect Application Fees”
   • [claimed-docs] “Payouts API”
   • [claimed-docs] “For custom integrations that only access your own Square account, personal access tokens are suitable for production use.”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Square—none0/10

   No evidence in the pack mentions data residency, regional data storage options, or geographic control over where Square account/API data is stored; the pack covers payments features, MCP/AI tooling, and dev tools but never addresses data residency.

   ⚑ flag

   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