# Support and production access

## Contact

Email [contact@genomicintelligence.ai](mailto:contact@genomicintelligence.ai) for API keys, integration questions, bug reports, and access changes. Include your `client_id` so we can trace your traffic.

When filing a bug, attach the correlators from the failing call so we can find it in the logs:

- `error.request_id` from the response body — also on the `X-Request-Id` response header. See [Errors](../reference/errors.md) for where it appears.
- `X-Job-Id`, set on every successful POST, when the issue is with a specific prediction or async job.

## Running at scale

The default API tier (see [Limits](../reference/limits.md)) covers development and steady production traffic. For high-volume or latency-sensitive integrations, contact us at [contact@genomicintelligence.ai](mailto:contact@genomicintelligence.ai). We provision production-shaped deployments with higher concurrency and dedicated throughput, sized to your workload.

## Server-side task chaining

The **find-genes-and-predict-expression** workflow chains the annotation and expression tasks server-side, so a single call finds genes in a region and predicts their expression without round-tripping intermediate results back to your client. It is a published endpoint — `POST /v1/workflows/find-genes-and-predict-expression`, on the same key as every other route, nothing to enable. Contract and options: [Tasks](../tasks.md#find-genes-and-predict-expression); the 50,000 bp synchronous cap is in [Limits](../reference/limits.md#hard-sync-cap).

Other kinds of chaining (a task pipeline we don't ship, or a variant of this one) are worth an [email](mailto:contact@genomicintelligence.ai) — tell us the shape of the call you'd like to make.