This is not our API. This repository is an independent, third-party profile of a company's publicly available API surface, maintained by API Evangelist. API Evangelist does not operate, host, resell, or support this company's APIs, and is not affiliated with or endorsed by the company unless stated on the profile.
Where the information came from. Everything here is assembled from material a member of the public can reach with a browser and no credentials — the company's own website, developer portal and documentation, the specifications it publishes for public use (OpenAPI, AsyncAPI, JSON Schema,
apis.json,llms.txtand similar), its public repositories, and its public status, pricing and changelog pages. Nothing here is obtained by breaching a system, defeating an access control, or using credentials of any kind.The rating is an independent assessment. The Kin Score and Agent Readiness rating are independently calculated scores of a company's public API artifacts, produced by API Evangelist against a published rubric. They are not certifications, endorsements, security assessments, or audits, and they score published artifacts — not the quality, safety, or security of the software.
Corrections, re-scores, and removal are free. No partnership, contract, or purchase is required, and you do not need to justify the request.
- Something wrong? Open an issue on this repository, or email info@apievangelist.com.
- Published something new? Ask for a re-score and we will re-run the rating.
- Want the listing taken down? Say so and we will honor it. The profile is reduced to your company name, a factual description, and a link to your own site, and the company is recorded as unrated — never scored zero for having asked.
Response times. Acknowledgement within one business day; removal or restriction within two business days; corrections and re-scores within five business days.
Not from the company, and here with a question? You are welcome here — we would rather be the front line and point you the right way than have a good report go nowhere. What this repository can answer is narrow, though, so it is worth knowing who you are actually looking for:
- A question about how the API works, an account, billing, or a bug in the service — that is the company's own support, not us. We profile this API; we do not operate it and cannot see your account.
- A bug in an open-source project we only catalog — file it on that project's own repository. This has happened with a real and correct bug report that reached us instead of the people who could fix it, which helped nobody.
- Anything about this listing itself — the description, the tags, the rating, a missing or wrong artifact — is ours. Open an issue here.
- Not sure, or something general about API Evangelist or APIs.io — open an issue on the APIs.io Inbox and we will route it.
This repository contains no software, and we will never ask you to download anything. There is no build, release, installer, or binary here — only text and machine-readable API descriptions, so there is nothing here that can be "corrupt" or need "repairing". Any issue, comment, or email claiming otherwise and offering a download link is not from us and is hostile. Do not follow the link; it is a lure. Report it to GitHub and, if you like, tell us at info@apievangelist.com so we can take it down.
On a security or compliance team? Email info@apievangelist.com with security in the subject line and you will get a person, not a form. We will tell you exactly which public URLs this profile was built from so your team can see the same surface we did, and we will take the listing down on request while you work through it.
Full detail: Where this data comes from
linkpeek.com — a Website Screenshot SaaS. You give it a target URL and it captures, stores, serves and refreshes a screenshot of that page through a REST-style image API. API-key authenticated, paid plans.
One API is recorded: the LinkPeek Screenshot API, at https://linkpeek.com/api/v1.
It is thin on purpose, and the reason is worth stating plainly.
Two unrelated projects use the name LinkPeek. The other one submitted itself to the
apis.io Add-API form several times from 147.15.103.217.sslip.io — a raw
IP address behind wildcard DNS, with an anonymous contact address. Because the intake gate matches
on the submitted name, its artifacts were attached to this record.
The result was a record that read as linkpeek.com while its entire evidence base belonged to
somebody else: five harvested OpenAPI definitions all declaring
servers: https://147.15.103.217.sslip.io:5000, plus generated collections, agent skills, an MCP
descriptor, plans, rate limits and security artifacts — 34 files in total — every one of them
derived from that host rather than from linkpeek.com.
All of it has been removed. What remains is what linkpeek.com itself publishes, and every URL in this record was fetched and confirmed to return 200 against a control path that returns a real 404.
linkpeek.com publishes no machine-readable artifacts of its own. Its apis.json,
openapi.json and llms.txt all return 404. So there is no specification to record here, and none
has been invented to fill the gap. A thin, honest record is the correct outcome; the rating reflects
what is published, and nothing else.
If anything here is wrong, or you publish a specification we have not found, write to kin@apievangelist.com and it gets corrected. Removal is honored on request, at no charge.
— Corrected 2026-08-23