Cloudflare / Cloudflare

Cloudflare Workers AI returns 7003 Not Found due to invalid object identifier

Cloudflare Workers AI API call fails with 7003 routing error when CLOUDFLARE_ACCOUNT_ID placeholder not properly substituted in curl/base URL Includes evidence for Cloudflare troubleshooting demand.

Source-backed Last updated May 20, 2026 1 source Needs local verification

Category: Cloudflare
Error signature: Not Found: error code 7003 Could not route to /client/v4/accounts/${CLOUDFLARE_ACCOUNT_ID}/ai/v1/chat/completions — object identifier invalid
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 20, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Cloudflare, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

Not Found: error code 7003 Could not route to /client/v4/accounts/${CLOUDFLARE_ACCOUNT_ID}/ai/v1/chat/completions — object identifier invalid is a Cloudflare failure pattern reported for developers trying to cloudflare workers ai api call fails with 7003 routing error when cloudflare_account_id placeholder not properly substituted in curl/base url. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub issue #18552 on anomalyco/opencode — Cloudflare Workers AI returns 7003 error with templated $CLOUDFLARE_ACCOUNT_ID literally present in path. Developer confusion about proper credential substitution for Workers AI endpoint. Covers 7003 error code not in covered-errors (only 522/525 listed). Category: Cloudflare.

Common causes

GitHub issue #18552 on anomalyco/opencode — Cloudflare Workers AI returns 7003 error with templated $CLOUDFLARE_ACCOUNT_ID literally present in path. Developer confusion about proper credential substitution for Workers AI endpoint. Covers 7003 error code not in covered-errors (only 522/525 listed). Category: Cloudflare.

Quick fixes

Confirm the exact error signature matches Not Found: error code 7003 Could not route to /client/v4/accounts/${CLOUDFLARE_ACCOUNT_ID}/ai/v1/chat/completions — object identifier invalid.
Check the Cloudflare account, local tool state, and provider configuration involved in the failing workflow.
Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match Not Found: error code 7003 Could not route to /client/v4/accounts/${CLOUDFLARE_ACCOUNT_ID}/ai/v1/chat/completions — object identifier invalid exactly before applying the quick fix.
Compare the failing environment with Cloudflare versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does Not Found: error code 7003 Could not route to /client/v4/accounts/${CLOUDFLARE_ACCOUNT_ID}/ai/v1/chat/completions — object identifier invalid mean in Cloudflare?

Not Found: error code 7003 Could not route to /client/v4/accounts/${CLOUDFLARE_ACCOUNT_ID}/ai/v1/chat/completions — object identifier invalid indicates the workflow described by "Cloudflare Workers AI returns 7003 Not Found due to invalid object identifier" failed in a Cloudflare context. Start by confirming the exact signature and the component that emitted it.

What should I check first for Not Found: error code 7003 Could not route to /client/v4/accounts/${CLOUDFLARE_ACCOUNT_ID}/ai/v1/chat/completions — object identifier invalid?

Check whether this cause matches your environment: GitHub issue #18552 on anomalyco/opencode — Cloudflare Workers AI returns 7003 error with templated $CLOUDFLARE_ACCOUNT_ID literally present in path. Developer confusion about proper credential substitution for Workers AI endpoint. Covers 7003 error code not in covered-errors (only 522/525 listed). Category: Cloudflare.

Is the Not Found: error code 7003 Could not route to /client/v4/accounts/${CLOUDFLARE_ACCOUNT_ID}/ai/v1/chat/completions — object identifier invalid guidance source-backed?

The "Cloudflare Workers AI returns 7003 Not Found due to invalid object identifier" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for Not Found: error code 7003 Could not route to /client/v4/accounts/${CLOUDFLARE_ACCOUNT_ID}/ai/v1/chat/completions — object identifier invalid?

For "Cloudflare Workers AI returns 7003 Not Found due to invalid object identifier", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging Not Found: error code 7003 Could not route to /client/v4/accounts/${CLOUDFLARE_ACCOUNT_ID}/ai/v1/chat/completions — object identifier invalid?

For "Cloudflare Workers AI returns 7003 Not Found due to invalid object identifier", collect the failing Cloudflare command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.