The Render Audit Logs API does one thing: it retrieves audit logs for workspace activity. Base URL https://api.render.com/v1. On the face of it, this is a small API — the kind most catalogs would file and forget.
It is the most heavily-described API in this week’s sweep. The entry at apis.io/apis/render/render-audit-logs-api/ carries sixteen properties spanning eleven distinct artifact types: OpenAPI, OpenAPISpec, AsyncAPI, GraphQL, Documentation, ReferenceDocumentation, Rules, Capabilities, JSONSchema, JSONStructure, JSONLD, Examples, Vocabulary, and APIsJSON.
Why a small API carries a large surface
Audit logs are the API you integrate when you are answering to someone else. Compliance review, incident reconstruction, access forensics — every one of those is a downstream consumer who needs to know exactly what a log entry contains and what it means.
That is why the artifact spread here is the right shape rather than an odd one. A JSON Schema tells you the log record’s structure. A JSON-LD context and a vocabulary tell you what the fields mean — which actor, which resource, which action verb. Spectral rules tell you the definition is governed. Examples let you build against realistic payloads before you have production traffic worth auditing.
Compare that to the typical audit-log integration, where you get a prose description of a JSON blob and discover the enum values by hitting the endpoint until you have seen them all.
The read-only asymmetry
There is a structural observation buried in this entry. Audit logs are read-only by design — you cannot write history — so the API surface is narrow. But the description surface is wide, because everything hard about audit logs is semantic rather than operational.
Most providers get this backwards. They lavish documentation on the endpoints that create things, because those are the ones in the getting-started guide, and leave the read-only compliance surfaces thinly described. Render inverted that, and the catalog can see it.
The AsyncAPI presence alongside the OpenAPI is the other note. Audit events are a stream before they are a query result; describing both the pull and the push shape is what lets an integrator choose.
Takeaway
Artifact count is not a vanity metric — it tracks how much a provider has thought about who consumes an API and why. A one-purpose audit endpoint carrying schemas, a vocabulary, governance rules, and worked examples is a provider treating compliance consumers as real users.
See the full property list at render.com/docs/api, and the catalog entry under apis.io/providers/render/.