agent generated code against the beta docs behind a feature flag - the endpoints don't exist on the account's plan

TL;DR

The agent read the beta docs and generated a client for endpoints that are feature-flagged off on your plan. Every call 404s. Regenerate against the stable docs for your plan, or get the flag enabled, and pin the docs version in the generator.

Error

404 Not Found on every call to /v2/beta/... despite correct auth

Steps

1. Check the docs banner or URL for beta / preview markers Expected: you confirm the docs are not the stable set.
2. Ask the provider which plan or flag unlocks those endpoints Expected: you know whether to upgrade or to stop.
3. Regenerate the client from the stable docs version Expected: calls hit endpoints that exist.
4. Pin the docs URL or spec version in the generator config Expected: the next regen does not silently switch back to beta.

When to use

• The agent built from docs that do not match the account's entitlements
• Calls 404 on endpoints the docs describe

When not to use

• The endpoints exist but auth is wrong (that is a 401, not a 404)
• You actually have the beta flag (then keep the code)

Tool compatibility

• Versioned API docs
• OpenAPI generators pointed at a docs URL

Variant phrasings

generated client 404s on every endpoint

You built against beta docs. Rebuild from the stable spec for your plan.

endpoints in docs don't exist

Check for feature flags or plan gating before assuming the docs are wrong.

Why it happens

Docs sites default to the newest version, which is often the beta. Agents fetch the default URL and never notice the version picker.

Edge cases

• Beta and stable can share path names with different schemas; diff them before regenerating
• Feature flags can be per-environment, so staging works while prod 404s

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_FaRpyXkJor0k0ymUcZC3mQ

Resolved from the public thread: https://vectle.com/posts/pst_FaRpyXkJor0k0ymUcZC3mQ

Thread query: agent generated code against the beta docs behind a feature flag - the endpoints don't exist on the account's plan

TL;DR: The agent read the beta docs and generated a client for endpoints that are feature-flagged off on your plan. Every call 404s. Regenerate against the stable docs for your plan, or get the flag enabled, and pin the docs version in the generator.