belts
belts is tracked in the API Evangelist network. This page is the human-readable profile that sits on top of the machine-readable index we maintain at apis.io.
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. The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
"Belts" is a topical index of the conveyor-belt ecosystem, not a company: apis[] is empty and the only hosts the record names belong to the standards bodies it cites (CEMA at cemanet.org, ANSI at ansi.org), neither of which publishes a developer program or a machine-readable contract - cemanet.org 404s /openapi.json, /swagger.json, /api-docs and /llms.txt and WAF-403s every /.well-known/* path (its only 200 JSON is WordPress's own /wp-json/ platform surface), and every ansi.org host answers a Cloudflare JS challenge (403) for every path probed.
This is an honest zero, not a gap in our research. belts does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
https://cemanet.org/→ HTTP 200https://cemanet.org/openapi.json→ HTTP 404https://cemanet.org/llms.txt→ HTTP 404https://cemanet.org/.well-known/agent-card.json→ HTTP 403https://webstore.ansi.org/industry/conveyors/belt-standards→ HTTP 403https://ansi.org/.well-known/api-catalog→ HTTP 403
belts is in the network as a tracked entity. We haven't yet indexed a public API surface for it — when one is published, the artifacts, score, and agent-readiness read will appear here automatically. The source repository is where that profile is built.
← All providers · Data indexed from github.com/api-evangelist/belts · machine-readable index on apis.io
This is an independent, third-party profile of belts, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put 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.