Scoring reads your public surface. If an artifact is not fetchable at a public URL, it does not exist as far as the score is concerned — which is the whole point, since that is also true for anyone trying to adopt you.
The fastest improvements are almost always the same ones. Publish an accurate OpenAPI at a stable URL and link to it. Publish the JSON Schema behind it. Put your plans and rate limits on a public page, ideally machine-readable. Declare your security schemes in the contract. Ship a change log with dates. Run a status page. Name a support channel a human answers. Publish terms. If you have an MCP server or agent-facing artifacts, publish them yourself rather than leaving them to be inferred.
Notice that none of these require you to change your API. They require you to publish what you already have, which is why scores usually move faster than teams expect.
If you want the specific list for your provider — which checks you are failing, what each is worth, and what to do about it — that is what the personalized checklist is for. And if you think a score is wrong, say so with the URLs; every claim gets checked against a real fetch, and corrections happen when the evidence supports them.
