API v1.0

API reference

The meeAgent voice API. You pick a voice, write the agent's instructions, and open a call.

Authentication

WhoHow
Your backendAuthorization: Bearer mk_live_… (an API key)
Your users' browsersa client_token, single use, 60 s, in the realtime URL

The API key never goes to a browser. Your backend asks for a client_token and hands that to the page. A key carries scopes (x-scope on each operation below); a key that lacks the scope an operation needs gets 403 naming it.

Identifiers, dates, money

Identifiers are a prefix plus 20 base32 characters (agt_…, ses_…). Dates are ISO-8601 in UTC. Money is an object with amount and currency; amount can be null, which means the call could not be priced, not that it was free.

Errors

Every failure returns {"error": {"code", "message", "param"?}}. Match on code.

Rate limits

Each operation carries its own under x-rate-limit. On top of those, any call made with an API key is limited to 600 per minute per key. Exceeding a limit returns 429 with Retry-After.

Auth

POST/v1/auth/signup

Signup

No auth required10 / 1min per ip
Request bodyjson
{
  "email": "ana@acme.com",
  "password": "correct-horse-battery",
  "company_name": "Acme"
}
Response · 202json
{
  "status": "pending_verification"
}
cURLbash
curl -X POST "https://test.meeagent.ai/v1/auth/signup" \
  -H "Content-Type: application/json" \
  -d '{
  "email": "ana@acme.com",
  "password": "correct-horse-battery",
  "company_name": "Acme"
}'
POST/v1/auth/verify-email

Verify Email

No auth required10 / 1min per ip

200 — Successful Response

cURLbash
curl -X POST "https://test.meeagent.ai/v1/auth/verify-email"
POST/v1/auth/login

Login

No auth required10 / 1min per ip
Request bodyjson
{
  "email": "ana@acme.com",
  "password": "correct-horse-battery"
}
Response · 200json
{
  "access_token": "eyJhbGciOiJIUzI1NiIs…",
  "token_type": "bearer",
  "user": {
    "id": "usr_…",
    "email": "ana@acme.com",
    "name": "Ana",
    "role": "owner"
  }
}
cURLbash
curl -X POST "https://test.meeagent.ai/v1/auth/login" \
  -H "Content-Type: application/json" \
  -d '{
  "email": "ana@acme.com",
  "password": "correct-horse-battery"
}'
POST/v1/auth/otp/request

Otp Request

No auth required10 / 1min per ip

202 — Successful Response

cURLbash
curl -X POST "https://test.meeagent.ai/v1/auth/otp/request"
POST/v1/auth/otp/verify

Otp Verify

No auth required10 / 1min per ip

200 — Successful Response

cURLbash
curl -X POST "https://test.meeagent.ai/v1/auth/otp/verify"
POST/v1/auth/password/forgot

Password Forgot

202 exista o no el correo: quién tiene cuenta aquí no se averigua preguntando.

No auth required10 / 1min per ip

202 — Successful Response

cURLbash
curl -X POST "https://test.meeagent.ai/v1/auth/password/forgot"
POST/v1/auth/password/reset

Password Reset

Sin sesión de vuelta a propósito: quien acaba de poner la contraseña entra con ella.

No auth required10 / 1min per ip

204 — Successful Response

cURLbash
curl -X POST "https://test.meeagent.ai/v1/auth/password/reset"
POST/v1/auth/password/change

Password Change

Cierra las demás sesiones y devuelve un token nuevo para no cerrar también esta.

No auth required10 / 1min per ip

200 — Successful Response

cURLbash
curl -X POST "https://test.meeagent.ai/v1/auth/password/change"
POST/v1/auth/invitations/accept

Accept Invitation

Entra en el tenant que invitó, con el rol que le pusieron y el correo ya verificado.

No auth required10 / 1min per ip

200 — Successful Response

cURLbash
curl -X POST "https://test.meeagent.ai/v1/auth/invitations/accept"
POST/v1/auth/logout

Logout

Revokes this JWT by jti until it expires; later requests with it get 401.

No auth required

204 — Successful Response

cURLbash
curl -X POST "https://test.meeagent.ai/v1/auth/logout"
GET/v1/me

Me

No auth required

200 — Successful Response

cURLbash
curl -X GET "https://test.meeagent.ai/v1/me"

Catalog

GET/v1/voices

List Voices

Authenticated120 / 1min per ip

200 — Successful Response

cURLbash
curl -X GET "https://test.meeagent.ai/v1/voices" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
GET/v1/runtimes

List Runtimes

Authenticated120 / 1min per ip

200 — Successful Response

cURLbash
curl -X GET "https://test.meeagent.ai/v1/runtimes" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"

Agents

GET/v1/agents

List Agents

scope: agents:read600 / 1min per api_key
GET /v1/agents parameters
NameTypeRequiredDescription
limit (query)integerOptional
cursor (query)string | nullOptional

200 — Successful Response

cURLbash
curl -X GET "https://test.meeagent.ai/v1/agents" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
POST/v1/agents

Create Agent

scope: agents:write600 / 1min per api_key
Request bodyjson
{
  "name": "Support Acme",
  "instructions": "You are a customer support agent for Acme. Be brief and warm.",
  "voice": "eva",
  "language": "es-CO",
  "tools": [
    {
      "type": "webhook",
      "name": "get_order",
      "url": "https://acme.com/hooks/order"
    }
  ]
}
Response · 201json
{
  "id": "agt_k3m9x2p7q1r5t8v4w6y2",
  "name": "Support Acme",
  "description": "",
  "instructions": "You are a customer support agent for Acme. Be brief and warm.",
  "voice": "eva",
  "runtime": "mee-voice-standard",
  "language": "es-CO",
  "tools": [
    {
      "type": "webhook",
      "name": "get_order",
      "url": "https://acme.com/hooks/order",
      "description": "",
      "status": "available"
    }
  ],
  "limits": {
    "max_duration_s": 900,
    "max_instructions_chars": 8000
  },
  "status": "active",
  "created_at": "2026-09-18T10:00:00Z",
  "updated_at": "2026-09-18T10:00:00Z"
}
cURLbash
curl -X POST "https://test.meeagent.ai/v1/agents" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "name": "Support Acme",
  "instructions": "You are a customer support agent for Acme. Be brief and warm.",
  "voice": "eva",
  "language": "es-CO",
  "tools": [
    {
      "type": "webhook",
      "name": "get_order",
      "url": "https://acme.com/hooks/order"
    }
  ]
}'
GET/v1/agents/{agent_id}

Get Agent

scope: agents:read600 / 1min per api_key
GET /v1/agents/{agent_id} parameters
NameTypeRequiredDescription
agent_id (path)stringRequired

200 — Successful Response

cURLbash
curl -X GET "https://test.meeagent.ai/v1/agents/{AGENT_ID}" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
PATCH/v1/agents/{agent_id}

Patch Agent

scope: agents:write600 / 1min per api_key
PATCH /v1/agents/{agent_id} parameters
NameTypeRequiredDescription
agent_id (path)stringRequired

200 — Successful Response

cURLbash
curl -X PATCH "https://test.meeagent.ai/v1/agents/{AGENT_ID}" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
DELETE/v1/agents/{agent_id}

Delete Agent

scope: agents:write600 / 1min per api_key
DELETE /v1/agents/{agent_id} parameters
NameTypeRequiredDescription
agent_id (path)stringRequired

204 — Successful Response

cURLbash
curl -X DELETE "https://test.meeagent.ai/v1/agents/{AGENT_ID}" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"

Sessions

POST/v1/sessions

Create Session

scope: sessions:write60 / 1min per tenant

201 — Successful Response

cURLbash
curl -X POST "https://test.meeagent.ai/v1/sessions" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
GET/v1/sessions

List Sessions

scope: sessions:read600 / 1min per api_key
GET /v1/sessions parameters
NameTypeRequiredDescription
limit (query)integerOptional
cursor (query)string | nullOptional

200 — Successful Response

cURLbash
curl -X GET "https://test.meeagent.ai/v1/sessions" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
POST/v1/sessions/token

Session Token

Con Idempotency-Key, un reintento devuelve el token de antes en vez de cobrar otra sesión.

scope: sessions:write60 / 1min per tenant
Request bodyjson
{
  "agent_id": "agt_k3m9x2p7q1r5t8v4w6y2",
  "context": {
    "customer_id": "42"
  }
}
Response · 200json
{
  "client_token": "cZhQgeK9DhIYAmAHVLVZq5aplEUMRn-HxmTLm0-zVFc",
  "session_id": "ses_2ku2tkwhrjkemlzjl6pj",
  "expires_at": "2026-09-18T10:01:00Z",
  "realtime_url": "wss://api.meeagent.ai/v1/realtime",
  "max_duration_s": 900,
  "transport": null
}
cURLbash
curl -X POST "https://test.meeagent.ai/v1/sessions/token" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "agent_id": "agt_k3m9x2p7q1r5t8v4w6y2",
  "context": {
    "customer_id": "42"
  }
}'
GET/v1/demo

Demo Status

Estado de la demo pública, para que la web sepa qué ofrecer antes de pedir un token.

Sin autenticación y sin efectos: comparte el cupo del catálogo porque es lo mismo, una página pública preguntando qué hay. Pedir esto nunca gasta el cupo de llamada.

enabled es conservador: dice que creemos que la llamada funcionaría. Si falta la clave del proveedor, o si ninguna llamada reciente llegó a sonar, dice que no y la web ofrece otra cosa —que es mejor que un botón de llamar que contesta 503.

No auth required120 / 1min per ip

200 — Successful Response

cURLbash
curl -X GET "https://test.meeagent.ai/v1/demo"
POST/v1/demo/token

Demo Token

Public website demo (ADR 0002): no API key, one call per IP per window, small concurrency cap.

No auth required1 / 5min per ip
Request bodyjson
{
  "voice": "eva"
}

200 — Successful Response

cURLbash
curl -X POST "https://test.meeagent.ai/v1/demo/token" \
  -H "Content-Type: application/json" \
  -d '{
  "voice": "eva"
}'
GET/v1/sessions/{session_id}

Get Session

scope: sessions:read600 / 1min per api_key
GET /v1/sessions/{session_id} parameters
NameTypeRequiredDescription
session_id (path)stringRequired

200 — Successful Response

cURLbash
curl -X GET "https://test.meeagent.ai/v1/sessions/{SESSION_ID}" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
POST/v1/sessions/{session_id}/update

Update Session

scope: sessions:write600 / 1min per api_key
POST /v1/sessions/{session_id}/update parameters
NameTypeRequiredDescription
session_id (path)stringRequired

200 — Successful Response

cURLbash
curl -X POST "https://test.meeagent.ai/v1/sessions/{SESSION_ID}/update" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
POST/v1/sessions/{session_id}/cancel

Cancel

scope: sessions:write600 / 1min per api_key
POST /v1/sessions/{session_id}/cancel parameters
NameTypeRequiredDescription
session_id (path)stringRequired

204 — Successful Response

cURLbash
curl -X POST "https://test.meeagent.ai/v1/sessions/{SESSION_ID}/cancel" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
POST/v1/sessions/{session_id}/end

End

scope: sessions:write600 / 1min per api_key
POST /v1/sessions/{session_id}/end parameters
NameTypeRequiredDescription
session_id (path)stringRequired

204 — Successful Response

cURLbash
curl -X POST "https://test.meeagent.ai/v1/sessions/{SESSION_ID}/end" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
GET/v1/sessions/{session_id}/transcript

Transcript

scope: sessions:read600 / 1min per api_key
GET /v1/sessions/{session_id}/transcript parameters
NameTypeRequiredDescription
session_id (path)stringRequired

200 — Successful Response

cURLbash
curl -X GET "https://test.meeagent.ai/v1/sessions/{SESSION_ID}/transcript" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
GET/v1/sessions/{session_id}/events

Events

scope: sessions:read600 / 1min per api_key
GET /v1/sessions/{session_id}/events parameters
NameTypeRequiredDescription
session_id (path)stringRequired

200 — Successful Response

cURLbash
curl -X GET "https://test.meeagent.ai/v1/sessions/{SESSION_ID}/events" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"

Account

GET/v1/usage

Usage

scope: usage:read600 / 1min per api_key
GET /v1/usage parameters
NameTypeRequiredDescription
from (query)string | nullOptional
to (query)string | nullOptional
group_by (query)stringOptional
Response · 200json
{
  "minutes": 12.5,
  "sessions": 7,
  "api_requests": 143,
  "spend": {
    "amount": 0.625,
    "currency": "USD"
  },
  "unpriced_sessions": 0,
  "series": [
    {
      "key": "2026-09-18",
      "minutes": 12.5,
      "sessions": 7,
      "spend": 0.625,
      "api_requests": 143
    }
  ]
}
cURLbash
curl -X GET "https://test.meeagent.ai/v1/usage" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
GET/v1/usage/export

Usage Export

El detalle, una fila por sesión, para llevárselo a una hoja de cálculo o a un cierre de mes.

Se manda a trozos según se lee: un trimestre de una cuenta con tráfico son decenas de miles de filas, y armarlas enteras en memoria sería dejar que un cliente grande tumbe el proceso pidiendo su propio consumo.

scope: usage:read10 / 1min per ip
GET /v1/usage/export parameters
NameTypeRequiredDescription
from (query)string | nullOptional
to (query)string | nullOptional
format (query)stringOptional

200 — Successful Response

cURLbash
curl -X GET "https://test.meeagent.ai/v1/usage/export" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
PATCH/v1/tenant

Update Tenant

Cuánto se guarda el historial de las llamadas. Lo decide el cliente, no nosotros.

Authenticated

200 — Successful Response

cURLbash
curl -X PATCH "https://test.meeagent.ai/v1/tenant" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
POST/v1/tenant/delete/request

Request Tenant Deletion

202 siempre. Borrar una cuenta no puede depender de un clic ni de una sesión robada.

Authenticated10 / 1min per ip

202 — Successful Response

cURLbash
curl -X POST "https://test.meeagent.ai/v1/tenant/delete/request" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
POST/v1/tenant/delete/confirm

Confirm Tenant Deletion

Apaga la cuenta en el acto y programa la purga.

Authenticated10 / 1min per ip

200 — Successful Response

cURLbash
curl -X POST "https://test.meeagent.ai/v1/tenant/delete/confirm" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
GET/v1/billing

Billing

Authenticated

200 — Successful Response

cURLbash
curl -X GET "https://test.meeagent.ai/v1/billing" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
GET/v1/api-keys

List Keys

Authenticated

200 — Successful Response

cURLbash
curl -X GET "https://test.meeagent.ai/v1/api-keys" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
POST/v1/api-keys

Create Key

Authenticated
Request bodyjson
{
  "name": "production backend",
  "permissions": [
    "sessions:write",
    "agents:read"
  ]
}
Response · 200json
{
  "id": "key_7h2k9m4p1q6r3t8v5w1y",
  "name": "production backend",
  "prefix": "mk_live_a1b2",
  "permissions": [
    "sessions:write",
    "agents:read"
  ],
  "status": "active",
  "created_at": "2026-09-18T10:00:00Z",
  "last_used_at": null,
  "key": "mk_live_a1b2… shown once, never again"
}
cURLbash
curl -X POST "https://test.meeagent.ai/v1/api-keys" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "name": "production backend",
  "permissions": [
    "sessions:write",
    "agents:read"
  ]
}'
DELETE/v1/api-keys/{key_id}

Revoke Key

Authenticated
DELETE /v1/api-keys/{key_id} parameters
NameTypeRequiredDescription
key_id (path)stringRequired

204 — Successful Response

cURLbash
curl -X DELETE "https://test.meeagent.ai/v1/api-keys/{KEY_ID}" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"

Members

GET/v1/members

List Members

Quién está dentro, y quién está invitado y todavía no ha entrado.

En {data: [...]} como el resto de listados: una lista a secas no deja sitio para añadir un cursor el día que un tenant tenga cien personas, y obligaría a la web a tratar esta ruta distinto de todas las demás.

Authenticated

200 — Successful Response

cURLbash
curl -X GET "https://test.meeagent.ai/v1/members" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
POST/v1/members/invitations

Invite

202 se pueda o no: quién tiene cuenta aquí no se averigua invitando.

Authenticated10 / 1min per ip

202 — Successful Response

cURLbash
curl -X POST "https://test.meeagent.ai/v1/members/invitations" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
DELETE/v1/members/invitations/{invitation_id}

Revoke Invitation

Authenticated
DELETE /v1/members/invitations/{invitation_id} parameters
NameTypeRequiredDescription
invitation_id (path)stringRequired

204 — Successful Response

cURLbash
curl -X DELETE "https://test.meeagent.ai/v1/members/invitations/{INVITATION_ID}" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
PATCH/v1/members/{member_id}

Set Role

Authenticated
PATCH /v1/members/{member_id} parameters
NameTypeRequiredDescription
member_id (path)stringRequired

200 — Successful Response

cURLbash
curl -X PATCH "https://test.meeagent.ai/v1/members/{MEMBER_ID}" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
DELETE/v1/members/{member_id}

Remove

Authenticated
DELETE /v1/members/{member_id} parameters
NameTypeRequiredDescription
member_id (path)stringRequired

204 — Successful Response

cURLbash
curl -X DELETE "https://test.meeagent.ai/v1/members/{MEMBER_ID}" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"

Webhooks

GET/v1/webhooks

List Webhooks

scope: webhooks:read30 / 1min per ip

200 — Successful Response

cURLbash
curl -X GET "https://test.meeagent.ai/v1/webhooks" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
POST/v1/webhooks

Create Webhook

El secreto se enseña aquí y no vuelve a salir nunca, igual que una API key.

scope: webhooks:write30 / 1min per ip

201 — Successful Response

cURLbash
curl -X POST "https://test.meeagent.ai/v1/webhooks" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
DELETE/v1/webhooks/{webhook_id}

Delete Webhook

scope: webhooks:write30 / 1min per ip
DELETE /v1/webhooks/{webhook_id} parameters
NameTypeRequiredDescription
webhook_id (path)stringRequired

204 — Successful Response

cURLbash
curl -X DELETE "https://test.meeagent.ai/v1/webhooks/{WEBHOOK_ID}" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
GET/v1/webhooks/{webhook_id}/deliveries

Deliveries

Qué se intentó, cuándo y cómo acabó: la respuesta a «no me llegó».

scope: webhooks:read30 / 1min per ip
GET /v1/webhooks/{webhook_id}/deliveries parameters
NameTypeRequiredDescription
webhook_id (path)stringRequired
limit (query)integerOptional
cursor (query)string | nullOptional

200 — Successful Response

cURLbash
curl -X GET "https://test.meeagent.ai/v1/webhooks/{WEBHOOK_ID}/deliveries" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"
POST/v1/webhooks/{webhook_id}/deliveries/{delivery_id}/retry

Retry Delivery

Vuelve a intentar una entrega que se rindió, con un ciclo nuevo de intentos.

Solo sobre failed: reintentar algo que ya se entregó sería mandarlo dos veces a propósito, y una que sigue pendiente ya tiene su hora puesta. El event_id no cambia, porque sigue siendo el mismo hecho y el cliente tiene que poder reconocerlo como repetido.

scope: webhooks:write30 / 1min per ip
POST /v1/webhooks/{webhook_id}/deliveries/{delivery_id}/retry parameters
NameTypeRequiredDescription
webhook_id (path)stringRequired
delivery_id (path)stringRequired

202 — Successful Response

cURLbash
curl -X POST "https://test.meeagent.ai/v1/webhooks/{WEBHOOK_ID}/deliveries/{DELIVERY_ID}/retry" \
  -H "Authorization: Bearer $MEEAGENT_API_KEY"

Realtime

The call itself runs over a WebSocket, which OpenAPI cannot describe, so it is documented here.

Open wss://…/v1/realtime?token=<client_token> with the token from POST /v1/sessions/token. The token is single use and lasts 60 seconds: if the socket drops and you reconnect, ask for a new one. Reusing a spent token is refused before the handshake.

What you send

MessagePayload
session.update{instructions?, context?, business_state?, tools?}; answered with the new version
response.cancelnone — stops the agent talking
client.metrics{eot_to_audio_ms, connect_ms?, first_audio_ms?} — one per agent turn
pingnone — answered with pong

What you receive

MessagePayload
session.state{status, version}; the first one also carries session_id
error{code, message}; the REST codes, plus max_duration, which only exists here

turn.user, turn.agent and latency are reserved and not emitted yet: while the audio does not pass through meeAgent there are no turns to report, which is also why GET /v1/sessions/{id}/transcript comes back empty.

Latency, measured by you

Send client.metrics after each agent turn. eot_to_audio_ms is the one that matters: from the moment the person stops speaking to the first audio of the reply. connect_ms and first_audio_ms are worth sending once, on the first turn. Anything out of range or any extra field is answered with error {code: "invalid_request"} without closing the socket: telemetry must never cost a call. The aggregate appears in latency on the session, with source: "client".

Close codes

CodeMeaning
4401the token is invalid, expired or already used — refused before the handshake
4403the tenant, agent or runtime was stopped; an error {code: "forbidden"} is sent first
1008you broke one of the channel rules below while connected

Anything else is an ordinary WebSocket close. Reaching max_duration_s sends error {code: "max_duration"} first.

Channel rules

Four limits, and none of them is a surprise if you send what the protocol says.

- Origin. If the connection carries an Origin header — that is, it comes from a browser — the origin has to be one we know, or the connection is refused *before the handshake* (HTTP 403, the same as a bad token). With no Origin header, which is the case for an SDK or curl, the token is the only thing that matters. A WebSocket is not covered by the policy a browser applies to fetch, so this check lives here. - 40 messages every 2 seconds, per session. Going over ends the call with ended_reason: "flooded". - 10 invalid messages in a row end it with ended_reason: "protocol_error". One on its own does not: you get an error and the call goes on, and any valid message resets the count. - 32 KiB per message. The server cuts an oversized frame at its own layer, before reading it whole into memory.

Binary audio, server to server

WS /v1/realtime with Authorization: Bearer mk_… and binary PCM16 audio is planned and not available in v1.0. Today the socket takes ?token= and text messages only. That is why the control channel above is all there is for now, and why transport exists at all.

transport

POST /v1/sessions/token may return a transport block describing a direct audio channel. For a paying account it is always `null`, and you should treat it as such: it exists only for the public demo on meeagent.ai, and it will disappear once the audio runs through meeAgent. Build against the realtime socket above, never against transport.