[DennyHo0917]

Summary

Add API Route as an optional OpenAI-compatible gateway preset. I am affiliated with API Route. This follows the one-entry preset approach used in #928/#929.

Changes

• One gatewayPresets entry: canonical endpoint, API_ROUTE_API_KEY, gpt-6.1-sol, strict JSON schema, frontier prompt profile.
• One preset-resolution regression case and one row in the existing gateway table.
• Reuses the generic custom-provider transport and existing user override behavior.

Testing

• go test ./internal/llm ./internal/llm/provider/openaicompat passes.
• go vet ./internal/llm ./internal/llm/provider/openaicompat passes; gofmt and diff whitespace checks pass.
• Real calls through openaicompat.Client using the preset's endpoint/model/key variable: freeform and ShapeExpandTerms strict JSON-schema output both succeed with reasoning_effort: low.
• golangci-lint v2.14.0 run ./internal/llm ./internal/llm/provider/openaicompat: 0 issues.
• Full CGO build and full race suite were not run locally. Verification used a focused sparse checkout on Windows; the Gortex graph tools are not installed in this environment.

Checklist

• Existing preset pattern followed.
• No new transport package or unnecessary abstraction.
• Language extractor and benchmark items are not applicable.

[zzet]

Thanks for the clear PR and for disclosing the affiliation. The entry has the same shape as the cheaperinference preset, and provider list, provider show and the unknown-provider error pick it up with no other changes. On Go 1.27.3, go vet, the internal/llm and cmd/gortex provider tests and golangci-lint v2.14.0 all pass. The endpoint answers with OpenAI-style errors, and gpt-6.1-sol is in API Route's public model list.

Two small corrections before merge, each with a suggestion inline:

1. Docs row order. gortex provider list sorts presets by name, so the api-route row should come first in the gateway presets table, before cheaperinference.
2. Link in the code comment. https://www.api-route.com/en/docs/quickstart redirects to /docs/quickstart, which covers setting up Codex and Claude Code clients. https://www.api-route.com/docs/overview describes the OpenAI-compatible API, which is what the comment is about.

[zzet]

gortex provider list sorts presets by name, so the table can follow the same order:

Suggested change

	| `cheaperinference` | `https://api.cheaperinference.com/v1` | `gpt-5.4-mini` | `CHEAPER_INFERENCE_API_KEY` | `frontier` |
	| `api-route` | `https://global.api-route.com/v1` | `gpt-6.1-sol` | `API_ROUTE_API_KEY` | `frontier` |
	| `api-route` | `https://global.api-route.com/v1` | `gpt-6.1-sol` | `API_ROUTE_API_KEY` | `frontier` |
	| `cheaperinference` | `https://api.cheaperinference.com/v1` | `gpt-5.4-mini` | `CHEAPER_INFERENCE_API_KEY` | `frontier` |

[zzet]

This URL redirects to /docs/quickstart, which is about client setup. The overview page describes the API:

Suggested change

	// API Route (https://www.api-route.com/en/docs/quickstart) uses the
	// API Route (https://www.api-route.com/docs/overview) uses the

[DennyHo0917]

Thank you for the review. Both suggestions are addressed in signed commit b5b714a: the API Route row now precedes cheaperinference, matching the sorted preset list, and the code comment links to https://www.api-route.com/docs/overview. This follow-up changes only documentation and a comment; gofmt and git diff --check pass. Ready for another look.