OriginChain docs
examples · errors · 11 / 19

11. 404 - instance / endpoint not found

← Errors examples
what this error means

The hostname resolved but didn't match any provisioned OriginChain instance, or the path is not a registered route. The router replies with a generic not_found rather than disclosing what does exist.

what triggers it

A request to a hostname that doesn't belong to any tenant.

POST to a non-existent instance hostname
curl -X POST "https://nope.ap-south-1.db.originchain.ai/v1/tenants/$OC_TENANT/sql" \
  -H "Authorization: Bearer $OC_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"sql": "SELECT 1"}'
the canonical response body
{
  "error": "not_found",
  "message": "no instance is provisioned at this endpoint",
  "retry": false
}
how to recover
  • Confirm the instance hostname in the dashboard - it's on the instance details page.
  • Check the path is one of the documented routes (/sql, /rows, /vector, /graph, /ask, /schemas).
  • If the instance was destroyed, provision a new one or point at a sibling instance.
  • retry: false - the URL is wrong, not the engine.
common upstream causes
  • Typo in the instance subdomain.
  • Wrong region in the hostname (ap-south-1 vs us-east-1).
  • Instance was destroyed; the env var still points at the old endpoint.
  • Pre-launch hostname queued in DNS but provisioning hasn't completed yet.
  • Calling /api/v1 instead of /v1, or a roadmap endpoint that hasn't shipped.