ACKNOWLEDGMENTS.md
ACKNOWLEDGMENTS.md is a standardized file convention used in open source repositories to credit third-party software, libraries, inspirations, and other works that a project builds upon or is indebted to. It is a common practice for documenting attribution and provenance, complementing LICENSE, README, CONTRIBUTING, and CODE_OF_CONDUCT files as part of a healthy open source project structure. The file typically lists dependencies, their copyright holders, and the licenses under which they are distributed.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles ACKNOWLEDGMENTS.md the way a machine reads it — 8 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — ACKNOWLEDGMENTS.md scores 10.7/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile ACKNOWLEDGMENTS.md
Each block below is one kind of artifact we hold for ACKNOWLEDGMENTS.md. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Features 4
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Attribution Documentation
Provides a standardized location to document all third-party libraries, frameworks, and tools used in a project, along with their copyright holders and licenses.
License Compliance
Helps projects maintain compliance with open source licenses that require attribution, such as MIT, BSD, Apache 2.0, and Creative Commons.
Contributor Recognition
Acknowledges individuals and organizations that contributed to the project, beyond the primary maintainers listed in other files.
Provenance Tracking
Documents the origins of code, designs, or concepts that influenced the project, providing clear provenance for legal and audit purposes.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Open Source Projects
Used in open source repositories to document all third-party dependencies, their licenses, and copyright notices for compliance.
Corporate Software Releases
Required by many corporate open source release policies to document all third-party components before releasing software publicly.
Academic and Research Projects
Used in academic repositories to cite datasets, tools, and prior work that the research builds upon.
Documentation Projects
Applied to documentation repositories to credit sources, frameworks, and tools used to generate or host the documentation.
Resources
Every other property we hold for ACKNOWLEDGMENTS.md — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
← All providers · Data indexed from github.com/api-evangelist/acknowledgments-md · machine-readable index on apis.io