Glyph Freshness API
The Freshness API from Glyph — 2 operation(s) for freshness.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/glyphapi-dev:glyphapi-dev-freshness-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Glyph Freshness API
description: 'A language for agents: encode content into the cheapest substrate the reading model can parse, with honest per-reader token math. Fillin is the retrieval product — a time-series index of the dev internet that closes the gap between an LLM''s training cutoff and now.'
version: 0.1.0
tags:
- name: Freshness
paths:
/freshness:
get:
summary: Freshness
description: 'Public corpus freshness — no auth. Powers the landing-page widget and
gives operators a quick liveness signal without exposing /stats. Returns
only counts and timestamps; no document content.
Served from the SHARED corpus cache (`corpus()` — 30-min SWR + disk-
persisted + boot-seeded), not an independent stats() scan. The old path
had its own 60s-TTL cache with no stale-while-revalidate, so it cold-
scanned all ~185k rows (~33s on the 4GB VPS) once a minute and dumped
that latency on whichever visitor hit it first (see 2026-06-03).'
operationId: freshness_freshness_get
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
tags:
- Freshness
/v1/freshness:
get:
summary: Freshness Sla
description: 'Freshness SLA — the one agent-facing gate-point for "is the corpus current?".
Free, no auth, no DB cost (reads the same cached aggregate as /v1/corpus and
/healthz). An agent that watches a topic can poll this and gate on `all_fresh`
(or the per-source `stale` flags) instead of paying to discover staleness. Each
source carries its publish-cadence SLO and the measured lag, so the freshness
claim is verifiable rather than marketing — a source past its SLO is `stale: true`.
This consolidates the freshness signal that was previously only reachable by
parsing /healthz or /v1/corpus; those endpoints keep their existing shapes.
Returns:
as_of — UTC timestamp this judgement was made (timestamp your gate).
rows — total indexed docs.
latest — newest doc published_at across the whole corpus.
ingest_lag_seconds — seconds since that newest doc.
all_fresh — true iff NO source is past its SLO (the single gate field).
stale_sources — names of sources currently past SLO (empty when all_fresh).
sources — per-source {source, latest, lag_hours, slo_hours, stale}.
recovery — present only when stale_sources is non-empty. Same hint
as /v1/health: per stale source, lag, SLO, catch_up_hours,
next_action, and last_attempt when the scheduler recorded one.'
operationId: freshness_sla_v1_freshness_get
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
tags:
- Freshness
components:
securitySchemes:
HTTPBearer:
type: http
scheme: bearer