# Kiro

Source: https://docs.aicentos.com/en/clients/kiro

Language: en

> Kiro does not currently support a custom Base URL — why, and the workable alternatives

**Kiro does not currently support a custom Base URL and cannot connect to aicentos directly.**

Kiro is an agentic IDE from AWS (built on Code OSS). Its models all go through the bundled service backed by Amazon Bedrock. There is no official entry point for "custom model endpoints" or "bring your own API Key (BYOK)", and the community feature requests for this remain unimplemented.

## Prerequisites

There is no need to create an aicentos API Key for Kiro — the current version has nowhere to enter a custom key.

Reference information:

* Console: [https://aicentos.com](https://aicentos.com)
* Docs site: [https://docs.aicentos.com](https://docs.aicentos.com)

If you have already connected other clients, first confirm whether that client supports custom endpoints.

## Configuration to fill in

| Field    | Value                                              |
| -------- | -------------------------------------------------- |
| Base URL | No such setting exists                             |
| API Key  | No such setting exists                             |
| Model    | Can only be chosen from Kiro's built-in model list |

## Setup steps

Not possible. Kiro's settings only offer model switching (the `/model` command or the model picker) and a `model` field for custom Agents, and `model` only matches the available model IDs returned by Kiro's service — it cannot point at an external endpoint.

## Alternatives

Kiro does not support custom endpoints, so the following options are available:

* **Use a client that natively supports a custom Base URL**: for example Cursor, Windsurf, Cline, Roo Code, Zed Agent and others can all take `https://aicentos.com/v1` directly. See the other documents under "Client Integrations".
* **Stay on Kiro's built-in models**: Kiro's built-in models are provided by AWS and are unrelated to aicentos; billing cannot be combined.
* **Wait for official BYOM / BYOK support**: you can follow the feature requests in Kiro's official repository, but nothing has landed yet.
* **Corporate intranet gateway scenarios**: even with an internal LLM proxy deployed, Kiro cannot be pointed at it — this too requires official support.

Modifying hosts files, installing self-signed certificates, or patching the IDE are unofficial workarounds and are not recommended — they break Kiro's update mechanism and carry security and compliance risks.

## Test

There is no custom endpoint to test. To verify aicentos connectivity, use any client that supports a custom Base URL, or call the API directly:

```bash
curl https://aicentos.com/v1/chat/completions \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $AICENTOS_API_KEY" \
  -d '{"model":"gpt-5","messages":[{"role":"user","content":"hi"}],"stream":false}'
```

## Notes

* To reiterate: **the current version of Kiro does not support a custom Base URL and cannot connect to aicentos**.
* This document will be updated as Kiro's official capabilities change.
* Official documentation: [https://kiro.dev/docs](https://kiro.dev/docs)