Agents recover from edge cases deterministically with in-band severity classes and server-computed parameter hints
## Highlights
DC Hub deployed **error_version:1** across its entire data layer — 4,197 M&A deals, 316 markets, and 21,959 facilities now return errors with **deterministic recovery hints** instead of dead-ends. A bad parameter now returns a **machine-readable severity class** and **server-computed suggested_params**, so agents recover in-loop without human intervention.
## What it means
When an agent queries a nonexistent market slug or sends mismatched filters, it receives a structured error with **actionable remediation**: the severity (warn, error, fatal), the parameter that failed, and a suggested correction. For example, a query for "cheyene" (typo) returns `suggested_params: {"market": "cheyenne"}` with HTTP 400, not a silent null. The agent retries with the corrected value and completes the task.
The taxonomy is versioned and published at **https://dchub.cloud/docs/error-codes**, so calling systems can maintain forward compatibility as error classes evolve. Fewer dead-ends, fewer escalations, more completed requests.
## Methodology
The error contract uses **in-band signaling**: every response carries an `error_version` field, and error payloads include `code`, `severity`, `message`, and `suggested_params`. The versioning allows DC Hub to add granular classes (e.g., distinguishing a rate-limit from a malformed filter) without breaking existing integrations.
Source: DC Hub Data Center Intelligence (https://dchub.cloud/docs/error-codes). Updated daily.
---
Press inquiries: [email protected] · DC Hub MCP API: https://dchub.cloud/mcp