generated client calls a bulk-import endpoint from an example response - the endpoint only exists on the enterprise...

Check the pricing tier or plan requirement for every endpoint before generating code that depends on it. Docs examples assume the fullest plan, so an agent picks the clean bulk endpoint and never notices the enterprise badge. If the plan does not cover it, gate the code path behind a plan check or rebuild the flow from standard endpoints the current plan supports.

generated client calls a bulk-import endpoint from an example response  -  the endpoint only exists on the enterprise tier

Steps

1. Find the endpoint in the provider docs and read its tier or plan callout: badges like Enterprise, labels like available on, or a note in the pricing section. Write down exactly which plans include it.

Expected: You can state the endpoint's required plan in one sentence from the docs.

1. Check the actual plan of the account the integration will run on, in the provider dashboard - not the docs' example account, which usually has everything enabled.

Expected: You know the real plan and whether it covers the endpoint.

1. If the plan does not cover it, choose one: upgrade the plan, gate that code path behind a plan check that fails with a clear message, or rebuild the flow as chunked calls to the standard create endpoint the plan does include.

Expected: The import flow no longer depends on an endpoint the plan cannot reach.

1. Test the full flow on the real plan, not a trial or docs sandbox. Confirm no 403 or 404 from tier gating and that the import completes end to end.

Expected: The import runs end to end on the actual plan with no tier-gating errors.

Use this when

• a docs example shows an endpoint that 403s or 404s on your plan
• the generated client assumed features of a higher tier than you pay for
• the agent built an import or bulk flow around a premium-only endpoint

Not for this skill when

• the endpoint does not exist on any tier - that is a phantom endpoint, a different fix
• requests fail with 401 on endpoints the plan does include - that is an auth problem
• the endpoint is throttled but reachable - that is rate limiting, not tiering

Variant phrasings

endpoint only available on enterprise plan

bulk API requires higher tier

403 on docs example endpoint

premium-only endpoint in generated client

Why it happens

Docs examples are written to show the product at its best, which means the fullest plan. Tier badges sit in corners and callouts that an agent skims past while optimizing for the cleanest code path - and the cleanest path is almost always the premium bulk endpoint. The code works in the docs' world and breaks in yours.

Edge cases

• Trials often include enterprise features that vanish at renewal - re-check after the trial converts
• Some providers return 404 instead of 403 for endpoints your plan cannot see, which looks like a phantom endpoint
• Seat-based gating differs from plan-based gating: the endpoint exists but the key's role cannot use it
• When rebuilding on standard endpoints, watch the rate limits - chunked calls multiply request volume

Provenance

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