Equipmentwatch
EquipmentWatch (a Fusable brand, operated by Randall-Reilly, LLC) provides construction and equipment data APIs that deliver rental rates, ownership and operating costs, market values, machine specifications, serial-number verification and raw market transaction data for heavy equipment. Their data is used by contractors, equipment dealers, rental houses, lenders and insurance professionals to make informed decisions about equipment valuation, procurement, cost recovery and rental rate setting. The EquipmentWatch API is published as a single OpenAPI 3.0.3 contract at docs.equipmentwatchapi.com covering the Taxonomy, Values, Specifications, Rental, Verification, Cost and Bulk surfaces, served from equipmentwatchapi.com with a documented sandbox host, and authenticated with an x-api-key header issued through a request-an-API-key form.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Equipmentwatch the way a machine reads it — 14 machine-readable artifacts across 1 API, 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 — Equipmentwatch scores 41.0/100 (developing), with a separate agent-readiness read of 25/100 (agent aware). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Equipmentwatch's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/equipmentwatch/"
title="Equipmentwatch on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/equipmentwatch.svg"
alt="Equipmentwatch Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/equipmentwatch/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/equipmentwatch/"
title="Equipmentwatch on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/equipmentwatch/card.svg"
alt="Equipmentwatch Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Equipmentwatch
Each block below is one kind of artifact we hold for Equipmentwatch. 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.
APIs 8
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
EquipmentWatch Taxonomy API
Foundational API providing access to EquipmentWatch's manufacturer and model database, covering the taxonomy used across the broader API suite for construction and heavy equipme...
EquipmentWatch Specs API
Access to the industry's most comprehensive database of rich machine specifications for construction and heavy equipment, covering more than 33,000 models, parsed into spec fami...
EquipmentWatch Verification API
Serial number verification API supporting approximately 30,000 models of construction and heavy equipment, returning year of manufacture from a supplied serial number along with...
EquipmentWatch Costs API
Ownership and operating cost recovery rates derived from the Rental Rate Blue Book, supporting equipment cost benchmarking, internal charge rate calculation and FHWA rate lookup.
EquipmentWatch Values API
Current and trended market values for heavy equipment — Fair Market Value (FMV), Forced Liquidation Value (FLV) and Orderly Liquidation Value (OLV) — supporting valuation, appra...
EquipmentWatch Retail Rental API
National, regional and rental-house specific equipment rental rates for thousands of models across nearly every equipment rental house in North America, supporting rate optimiza...
EquipmentWatch Market Data API
Raw equipment sales activity (auction and resale transactions) and market-derived utilization and popularity benchmarks for the heavy equipment industry. Documented on the Equip...
EquipmentWatch Integration API
Read and write access to user-saved asset and group data inside the EquipmentWatch application, allowing saved models and groups to be moved into and out of third-party platform...
Scroll within the panel for all 8 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Equipmentwatch MCP Server
Candidate MCP tool surface derived from the EquipmentWatch OpenAPI. Every tool below binds 1:1 to a real published GET operation. No endpoint is asserted, because none exists.
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Equipmentwatch Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Equipmentwatch Finops
FINOPSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Equipmentwatch — 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 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/equipmentwatch · machine-readable index on apis.io
This is an independent, third-party profile of Equipmentwatch, 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.