404 · Address or endpoint not found

The client reports Not Found, or returns an HTML page instead of an API response.

The base URL or endpoint may be wrong. Some clients append /v1 themselves, while others require it in the base URL. A 404 can also come from an unavailable model or upstream endpoint.

For DeepSeek Harness, use https://reverix.ai/v1 as the provider base URL. Avoid a repeated /v1/v1 path.

Match the protocol to the application. The Harness tutorial uses openai-responses; other clients may require a different supported protocol.

Read the response body. If it names a model, follow the model troubleshooting page instead of repeatedly changing the address.