> Keiro Labs API documentation - Beta SLA
> Page: https://docs.keirolabs.ai/beta-sla.html
> Markdown: https://docs.keirolabs.ai/beta-sla.md
> Agent index: https://docs.keirolabs.ai/llms.txt
> API base URL: https://api.keirolabs.ai/v1
> Auth: send "Authorization: Bearer <api-key>" with a key created in the
> Keiro console (https://console.keirolabs.ai/api-keys). Use credentials saved by
> `keiro setup`, or resolve the key from a secret manager or an owner-only
> secret file and pass it to the client explicitly. Never read another
> provider's variable, and never put raw key material in environment
> variables, code, docs, or logs.

# Beta SLA and support posture

Keiro eb1 is in invite-only paid beta. The service is operated for serious
evaluation and early production-style testing, but it is not yet sold with a
formal uptime guarantee.

## Availability posture

During beta, Keiro targets reliable access to the public API at
`https://api.keirolabs.ai/v1`, but beta access is provided on a best-effort
basis unless a signed agreement says otherwise.

Keiro may perform maintenance, change model availability, adjust rate or spend
limits, or temporarily disable a capability to protect reliability, safety,
security, or billing correctness.

## Support path

Use `hello@keirolabs.ai` or the support channel included in your invite for:

- access and API-key issues
- suspected key exposure
- billing or usage questions
- reliability problems
- data-handling questions
- limit or model-access changes

Do not send API keys, external service credentials, private datasets, regulated
data, or full prompt/response logs in the first support message.

## Incident updates

Keiro uses `status.keirolabs.ai` for customer-visible availability updates.
During beta, Keiro may also send direct updates through the invite support
channel.

Public incident updates describe customer-visible symptoms and affected public
surfaces. They avoid sensitive operational detail, customer-specific data, and
non-public account information.

## Maintenance

For planned customer-impacting maintenance, Keiro attempts to provide advance
notice through the status page or support channel. Emergency maintenance may be
performed with shorter notice when needed to protect reliability, billing
correctness, security, or data handling.

## Customer responsibilities

Beta users should:

- store API keys in a local secret manager or equivalent private store,
- delete and replace keys after suspected exposure,
- use idempotency keys for retry-sensitive workflows,
- respect published rate and spend limits,
- avoid sending sensitive data unless the beta agreement permits it, and
- monitor application-level retries and timeouts.

## No unsupported uptime promise

Unless a signed agreement says otherwise, beta access does not include service
credits, a guaranteed monthly uptime percentage, or a guaranteed response time.
Keiro will use commercially reasonable efforts to investigate and mitigate
customer-impacting incidents during the beta.

## Related pages

- [Status and support](status-support.md)
- [Rate and spend limits](rate-and-spend-limits.md)
- [Legal and privacy](legal-privacy.md)