GunSpec

Health

Unauthenticated liveness and readiness probes for uptime monitoring. These return a flat body rather than the standard response envelope.

PublicExplorer+

Health Check

Liveness probe. Answers 200 whenever the API worker is running, and deliberately does not touch the database, so it stays green through a database incident. Use /ready to know whether requests will succeed. No authentication, no rate limit, and a flat body rather than the { success, data } envelope.

GET/health

Explorer+

No authentication. This endpoint answers without a key.

application/json

  • string

    Always ok. Getting an answer at all is the signal; there is no degraded value.

  • string

    When the probe answered, ISO 8601 UTC. A value that does not move between calls means something in between is caching the reply.

  • string

    The API version every endpoint is served under: the v1 in /v1/.... Not a build number.

  • string

    Which deployment answered: production (api.gunspec.io), staging, or development for a worker running locally.

Full rate limits

Minimum tier
Explorer+
Monthly quota
200/mo
Rate limit
10/min
Daily cap
50

Figures shown are for this endpoint's minimum tier. Higher tiers raise every limit.

PublicExplorer+

Readiness Check

Readiness probe. Runs one query against the database: 200 ready when it answers, 503 not_ready when it does not, so a load balancer or status page can tell "the API is up" from "the API can serve data". No authentication, no rate limit, and a flat body rather than the { success, data } envelope.

GET/ready

Explorer+

No authentication. This endpoint answers without a key.

application/json

  • string

    Always ready on a 200.

  • string

    The database answered the probe query.

  • 503The database did not answer the probe query

Full rate limits

Minimum tier
Explorer+
Monthly quota
200/mo
Rate limit
10/min
Daily cap
50

Figures shown are for this endpoint's minimum tier. Higher tiers raise every limit.