Intelligence API error reference · Updated August 2026
city_not_found.
Every Orbyt Intelligence error envelope carries a permanent doc_url that resolves here. This page is generated from the same error registry the API serves from, so it can never drift from runtime behavior.
What it means.
The city slug or ID was not found. Use /api/v1/intelligence/salaries/cities to list available city slugs.
Retry strategy.
The envelope returns retry_strategy: "use_alternative_tool" by default for this code.
Do not retry this endpoint with the same input. Switch to the endpoint or path named in error.retry_hint.alternative_tool.
Example error envelope.
Locked RFC-001 shape. The HTTP status is 404, the x-request-id header mirrors error.request_id, and the doc_url points back to this page.
{
"error": {
"type": "not_found_error",
"code": "city_not_found",
"message": "The city slug or ID was not found.",
"doc_url": "https://www.orbytlabs.ai/intelligence/api/errors/city_not_found",
"request_id": "req_0123456789abcdef",
"retry_strategy": "use_alternative_tool",
"retry_hint": {
"alternative_tool": "/api/v1/intelligence/salaries/search"
}
}
}How to fix it.
- Read error.retry_hint.alternative_tool for the endpoint the API suggests instead.
- Call the suggested endpoint to discover valid inputs (canonical slugs, available cities, replacement paths).
- Retry your original request with the discovered value, or stay on the alternative endpoint if it answers your question directly.
Related codes.
Other codes in the not_found_error family.