Status

status.hellonear.xyz shows whether HelloNear and the services it runs on answer. It was built on 13 Nov 2026 after two outages from outside HelloNear’s code in one night: NEAR AI embeddings hung, and NEAR Intents 1Click quotes timed out. When a provider is down, a Mind says so plainly in the chat and points to the status page.

What is checked

Every 5 minutes the backend checks 9 services in parallel and keeps 8 days of results:

Service id	Group	Check	Slow over	Down after
`hellonear-api`	HelloNear	Postgres `select 1`	1 s	5 s
`hellonear-engine`	HelloNear	engine `/v1/health`	2 s	10 s
`nearai-chat`	NEAR AI	a chat completion, from the engine	10 s	30 s
`nearai-embeddings`	NEAR AI	an embedding, from the engine	5 s	15 s
`near-intents-quote`	NEAR	1Click dry quote, 10 USDC NEAR to Base	15 s	30 s
`outlayer`	Partners	OutLayer `/health`	3 s	10 s
`near-rpc`	NEAR	FastNear testnet `status`	3 s	10 s
`agent-market`	Partners	`market.near.ai/v1/agents?limit=1`	5 s	15 s
`tee-explorer`	Partners	`HEAD proof.t16z.com`	5 s	15 s

Down also means an error, a non-2xx answer, or an answer without the expected field. If the engine does not answer, nothing is stored for NEAR AI that round; it is not guessed.

GET /v1/status

GET https://api.hellonear.xyz/v1/status: public, any origin, no cookies, access-control-allow-origin: *, cache-control: public, max-age=30.

{ "updatedAt": ISO, "overall": "operational" | "degraded" | "down",
  "services": [{ "id", "name", "group": "HelloNear" | "NEAR AI" | "NEAR" | "Partners",
    "status": "operational" | "degraded" | "down" | "unknown", "latencyMs": number | null, "checkedAt": ISO | null,
    "detail": string | null, "impact": string, "uptime24h": number | null, "uptime7d": number | null,
    "history": [{ "start": ISO, "status": "operational" | "degraded" | "down" | "none", "checks": number, "bad": number, "detail": string | null }] }],
  "incidents": [{ "service", "name", "status": "down" | "degraded", "start": ISO, "end": ISO | null, "minutes": number, "detail": string | null }] }

status is the latest check, or unknown when it is older than 15 minutes.
overall is down when a HelloNear service is down, degraded when anything else is down or degraded. Uptime counts degraded as up.
history is 48 half-hour buckets ending with the current one, oldest first: the worst check in each.
incidents (newest first, at most 100): consecutive non-operational checks of one service; one good check ends it. end is null while ongoing.
Details are short and never carry keys or URLs.

curl -s https://api.hellonear.xyz/v1/status | jq '.overall, [.services[] | {id, status}]'

Get started

Concepts

Track features

API

Smart contracts

More

What is checked

GET /v1/status

​What is checked

​GET /v1/status

What is checked

GET /v1/status