/v1/status

Gateway status

Probing…

The cards above are a live read of GET /v1/status. The same JSON is returned by GET /v1 and by GET /api/decide. This page is the gateway for this website. It is not a status board for Hugging Face, for Convai, or for the LayaAir game engine.

What each field means

configured is true when the server has IMPOSSIBL_API_KEY set. live is the same flag. upstream_mode is impossibl in that case and unconfigured otherwise. The model string is IMPOSSIBL_MODEL if the deploy sets one, and convaiinnovations/laya if it does not. service is the name of this API, laya-model-api.

When the gateway is not configured, POST /v1/decide returns 503 with code not_configured. The playground can still run an Offline demo. That demo does not load weights and is not a live model answer. A configured gateway proxies state and questions to the upstream and returns choice, score, and noul answers. The browser never receives the upstream key.

anonymous free runs is ANON_FREE_RUNS. The default is 1. The counter is the laya_anon cookie, which is not tied to a Google account. After the allowance is used, a call without a laya_ key or a signed-in session returns 401. Creating a key requires Google sign-in. The first successful registration also starts the monthly grant of 10,000 input tokens, described on pricing.

The Creem card is on only when CREEM_ENABLED is true and CREEM_API_KEY is set. That is the switch for charging a pack. The buy buttons stay visible when checkout is off, and POST /api/checkout then returns 503 instead of sending you to a payment page. Credits are not added by the browser return URL. They are added when a paid notification arrives at POST /api/payment/notify/creem and the signature matches the signing secret. Stripe is a separate path and is used only when DEFAULT_PAYMENT_PROVIDER is stripe.

Fields the cards leave in the JSON

The probe shows the four facts a caller usually needs. The JSON body also includes whether the Creem webhook secret is set, whether the Creem environment resolves to production or test, how many pack ids are mapped to Creem products, and whether a test charge amount is configured. It includes the same pair of flags for Stripe, and checkout, which is creem, stripe, or null. A null checkout provider means a buy will not start a charge. A test amount is a deploy setting for a deliberate cheap charge. Production leaves it empty so the charge is the pack price.

None of these fields is a latency graph, an incident history, or a per-account error log. A single successful probe means the status route answered. It does not promise that the next decide call will succeed. The upstream can still reject the request, time out, or return an error. Decide calls time out on this server after 120 seconds and then return 504.

GET /v1/status
curl -sS https://laya-model.com/v1/status

Reading a decide error after the probe is green

A configured probe does not change the auth and billing rules. 401 means the laya_ key is missing, unknown, or revoked, or the anonymous allowance is used. 402 means the prepaid balance cannot cover the call. 429 means the account is over its requests-per-minute ceiling, or over the hourly or daily input-token cap. 400 means the body is not the JSON the route expects: state is required on POST /v1/decide, and questions must be a non-empty object. 413 means the body is over 100,000 bytes.

POST /v1/gate does not use this upstream flag. The gate is a local policy check. It returns allow, review, or block, it does not spend tokens, and it does not require a key. If you are debugging a label, call decide first and then send those answers to the gate. The API reference has the request shapes. The decide API guide explains choice, score, and noul. The credits and keys guide explains the meter. If the probe itself fails to load, the gateway process did not answer. Write to the address on the contact page with the time in UTC. Do not include an API key.

Status · Laya AI