API 登记簿

Wallpaper search — full-resolution images with dimensions and thumbnails.

Anonymous callers get almost everything: sfw AND sketchy are both open, and only the nsfw bit needs a key — which makes it the wallpaper source that can be a fallback with nothing to apply for. The trap is that the nsfw bit fails in silence. A keyless purity=001 returns 200 with meta.total 0, and in a mixed request it simply contributes nothing: keyless 111 and 110 come back with the identical total. No error, no warning, no hint that a third of what you asked for was dropped. That is the third failure mode in this registry — Openverse 401s, Iconify clamps into range, this one says nothing at all — so the client clears that one bit when keyless, and throws if nsfw was the only thing asked for. Do NOT over-correct by pinning everything to sfw: an earlier version of this entry did, on the strength of a first page that was all sfw, and that page was all sfw only because sfw outnumbers sketchy about 50:1 in sort order. Totals are the evidence; one page is not. A key also widens the sfw and sketchy pools themselves (12728 to 13615, 242 to 745 on the same query) — presumably account filters, not measured further. Page size is a fixed 24 (per_page is accepted and ignored), making pagination the only lever. Two shapes bite: meta.query is a plain string for a normal search but resolves to {id, tag} for an exact-tag search, and ratio is a string ("1.5"), not a number. The key can travel as an X-API-Key header instead of the ?apikey= query the docs lead with, which keeps it out of access logs. And it sends no Access-Control-Allow-Origin at all, so a browser cannot call it directly — every web client needs a server hop, which is where the key should live anyway.

Royalty-free photos and illustrations, permissively licensed.

No keyless mode, so it cannot be the fallback provider. The trap is the 500-result ceiling: it is a cap on what you can *reach*, not on what matched, so naive pagination walks confidently off the end. The original file needs full API access — a free key gets you roughly 1280px, which is fine for reference and not for print.

Creative-Commons and public-domain media aggregated from Flickr, Wikimedia and others.

Keyless, which makes it the provider that always works. Two things to design around: the page_size ceiling for anonymous callers is a hard 401 rather than a clamp, so a client that asks for 50 gets an error and not 20 rows; and because it aggregates upstreams, nearly every field is nullable — dimensions and file type routinely absent, so a schema without optionals fails on real data. It hands back a ready-made attribution string, which is the single most useful field any of these five return.

Curated stock photography, with a browsable default feed.

The key goes in an Authorization header, never a query param, so it cannot leak into a logged URL — the only one of the five that gets this right by design. Its nicest property is that an empty query has an answer: /curated is a real feed, so a search UI has something to show before anyone types. Pagination is a next_page URL that simply disappears on the last page rather than a count.

Search across 150+ open-source icon sets — 200k+ icons, as SVG.

Keyless and the matrix already leans on it twice over — yAssets imports from it, and every icon on every yPulse surface is one of its sets. Two facts worth carrying: results are monochrome SVGs using currentColor, so a thumbnail needs a colour applied or it renders invisible while the imported original stays recolourable; and licence and author are per *set*, returned in the response's collections map rather than on each icon, so an importer that reads only the icon loses the attribution it needs.

DNS records, zones, Workers and Pages deployment.

Carries the matrix's DNS convergence. The trap is not in the API but in what it lets you do: proxying a Vercel record breaks domain-control validation months later, and a Workers custom domain is created and owned by wrangler — writing it through this API means two systems fighting over one name. Scoped tokens are worth the extra minute; Zone:Read + DNS:Edit is all a converger needs.

Repository facts — commits, releases, traffic, contents, Actions dispatch.

The matrix's own nervous system: every snapshot, ledger and changelog yPulse shows is read through it. Two things to know before leaning harder on it — the traffic endpoints only return 14 days, so a collector that skips a fortnight loses that window forever, and the stats endpoints (code frequency) answer 202 with an empty body while GitHub computes, which reads as 'no data' unless you retry.

Daily launch leaderboards with topics, votes and maker data.

Feeds yPulse's radar. GraphQL, so the cost is complexity rather than call count — a wide query on one day beats many narrow ones. The day boundary is US-Pacific and not negotiable, which is why the collector names its files by that day instead of local time.

Text generation and structured extraction.

Two jobs in yPulse and they want opposite things: the weekly digest is long, tolerant and offline (a bad sentence costs nothing), while Discord's /c capture is short, interactive and must not lose data — so its parser re-validates with zod and falls back to filing the raw text as one idea. Any future use should decide which of those two it is before picking a model.

Slash commands over HTTP, plus one-way webhook posting.

The reason yPulse has a terminal without running a gateway process: HTTP interactions verify an Ed25519 signature per request, so a serverless route is enough. The 3-second acknowledgement is the design constraint — anything that calls an LLM has to defer (type 5) and finish in the background. Command choices are baked in at registration, so a change to the project list means re-running the register script.

Postgres over HTTP, with branching and scale-to-zero.

The hub's read-write side. The HTTP driver is what makes it fit a serverless route at all — a pooled TCP client would spend its life reconnecting. Scale-to-zero means the first query after a quiet period pays a cold start, which is fine for an operator tool and would not be for anything a visitor waits on.