Anyone else having issues with Claw suggesting deprecated Stripe API versions?

I've been systematically testing various AI coding assistants on data pipeline integrations, specifically focusing on payment processor webhooks where API stability is critical. In our evaluation framework, we've encountered a consistent and concerning pattern with Claw (the new model from a major vendor) when generating Stripe integration code. The assistant repeatedly suggests deprecated API versions, specifically `2020-08-27`, which reached end-of-life in March 2023.

Here's a typical prompt and the problematic output:

**Prompt:**
"Generate a Python function to create a Stripe Checkout Session with line items, using the latest Stripe API."

**Claw's Output (excerpt):**
```python
import stripe
stripe.api_key = "sk_test_..."

def create_checkout_session(product_data):
session = stripe.checkout.Session.create(
api_version="2020-08-27", # Incorrectly specified
payment_method_types=['card'],
line_items=[{
'price_data': {
'currency': 'usd',
'product_data': product_data,
'unit_amount': 5000,
},
'quantity': 1,
}],
mode='payment',
success_url='https://example.com/success',
cancel_url='https://example.com/cancel',
)
return session
```

The issue is twofold:
1. Explicitly hardcoding the `api_version` parameter is unnecessary and dangerous—the Stripe Python library automatically uses the latest version configured in your account unless overridden.
2. The suggested version `2020-08-27` is deprecated. The latest stable version as of this writing is `2024-11-15.acacia`. Using an old version can lead to missing webhook events, deprecated parameters being ignored, and security gaps.

**Correct Approach:**
The function should omit the `api_version` parameter entirely for forward compatibility, and the library should be kept updated. The corrected code block:

```python
import stripe
stripe.api_key = "sk_test_..."

def create_checkout_session(price_id, quantity=1):
"""Create a Stripe Checkout Session using the latest API."""
session = stripe.checkout.Session.create(
payment_method_types=['card'],
line_items=[{
'price': price_id, # Use pre-defined Price IDs, not inline price_data
'quantity': quantity,
}],
mode='payment',
success_url='https://example.com/success',
cancel_url='https://example.com/cancel',
)
return session
```

Key corrections:
- Removed the explicit `api_version` parameter.
- Shifted to using Stripe Price IDs instead of inline `price_data`, which is the current best practice for inventory and price management.
- Added a docstring clarifying intent.

This failure case is particularly insidious because the code will often appear to work initially (the deprecated API version may still be temporarily supported), leading to production issues months later when the version is fully sunset. In a data pipeline context, this can result in silent data loss in webhook processing, reconciliation errors, and broken analytics.

Has anyone else replicated this issue? I'm curious if it extends to other APIs (e.g., Twilio, SendGrid) where versioning is critical. Our team is now adding explicit API version checks to our assistant evaluation rubric.

--DC