EquipmentShare

EquipmentShare is a construction technology and equipment-solutions company (founded 2015, headquartered in Columbia, Missouri) whose proprietary platform, T3, unifies telematics, rental and fleet operations across one of the largest mixed fleets in the US — 349,000+ connected assets across 380+ locations. Its developer surface, T3OS, exposes a GraphQL ERP API (es-erp-api) at api.equipmentshare.com with three first-party auth flows backed by Auth0: user-delegated OAuth 2.0 (Authorization Code + PKCE), workspace-installed API keys (X-API-Key), and sign-in-only OpenID Connect. T3 also offers an Outbound Developer API for structured fleet-data access (XML/JSON) and aggregates AEMP-compliant OEM telematics. Access is granted through the T3OS developer portal (app.t3os.ai) and app registration.

EquipmentShare is listed with 1 API on the APIs.io network. Tagged areas include Company, Construction Technology, Fleet Management, Telematics, and Equipment Rental.

EquipmentShare’s developer surface includes documentation, changelog, engineering blog, support, authentication, and 15 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

27.6/100 thin ▬ flat Agent 16/100 agent aware Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →

AccessSelf serve

1 API 2 Agent Skills

Company Construction Technology Fleet Management Telematics Equipment Rental GraphQL Developer Platform Authentication

Kin Score

Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0

Composite quality — 27.6/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 6.8 / 17

Access Clarity 5.8 / 17

Operational Transparency 2.3 / 11

Contract Governance 0.5 / 10

Discoverability 5.6 / 9

Regulatory Posture 5.1 / 15

Agent readiness — 16/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/equipmentshare/"><img src="https://apis.io/badge/equipmentshare/card.svg" alt="EquipmentShare on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes

9 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Access Clarity scores 34.2 — up to +13.2 composite points
Developer Ergonomics scores 39.9 — up to +12.0 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/equipmentshare/apis.yml: open an issue on github.com/api-evangelist/equipmentshare to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
FMCSA Registered Electronic Logging Devices	regulated	26.2 (thin)	-	1

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

GraphQL

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

T3OS ERP GraphQL API

The T3OS developer platform's GraphQL ERP API (es-erp-api). A single GraphQL endpoint served over authenticated Bearer (user-delegated OAuth2) or X-API-Key (workspace-installed)...

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

Connect to T3OS on behalf of a user (OAuth2 + PKCE)

AGENT SKILL

Install a T3OS app in a workspace (unattended API key)

AGENT SKILL

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Equipmentshare Authentication

oauth2/apiKey/openIdConnect · 3 schemes

SECURITY

Equipmentshare Domain Security

TLSv1.2 · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Equipmentshare Scopes

2 scopes · authorizationCode

2 scopes

SCOPES

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

Login

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

AgentSkill

AgentSkill

LLMsTxt

LLMsTxt

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Conventions

Conventions

Conformance

Conformance

Lifecycle

Lifecycle

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 3

Authentication, authorization, and security posture

Authentication

Authentication

OAuthScopes

OAuthScopes

DomainSecurity

DomainSecurity

Operate 3

Status, limits, changes, and where to get help

ChangeLog

ChangeLog

ChangeLog

ChangeLog

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: equipmentshare
name: EquipmentShare
description: 'EquipmentShare is a construction technology and equipment-solutions company (founded 2015, headquartered in
  Columbia, Missouri) whose proprietary platform, T3, unifies telematics, rental and fleet operations across one of the largest
  mixed fleets in the US — 349,000+ connected assets across 380+ locations. Its developer surface, T3OS, exposes a GraphQL
  ERP API (es-erp-api) at api.equipmentshare.com with three first-party auth flows backed by Auth0: user-delegated OAuth 2.0
  (Authorization Code + PKCE), workspace-installed API keys (X-API-Key), and sign-in-only OpenID Connect. T3 also offers an
  Outbound Developer API for structured fleet-data access (XML/JSON) and aggregates AEMP-compliant OEM telematics. Access
  is granted through the T3OS developer portal (app.t3os.ai) and app registration.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://cdn.prod.website-files.com/60cb2013a506c737cfeddf74/620bbc52f1de86cc1ff1e219_Company%20Page-100.jpg
url: https://raw.githubusercontent.com/api-evangelist/equipmentshare/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- insight-partners
- y-combinator
x-tier: profiled
x-tier-reason: enriched-from-public-developer-surface
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Construction Technology
- Fleet Management
- Telematics
- Equipment Rental
- GraphQL
- Developer Platform
- Authentication
tags_raw:
- Company
- Construction Technology
- Fleet Management
- Telematics
- Equipment Rental
- GraphQL
- Developer Platform
- OAuth
apis:
- name: T3OS ERP GraphQL API
  description: The T3OS developer platform's GraphQL ERP API (es-erp-api). A single GraphQL endpoint served over authenticated
    Bearer (user-delegated OAuth2) or X-API-Key (workspace-installed) access.
  humanURL: https://app.t3os.ai
  baseURL: https://api.equipmentshare.com/es-erp-api/graphql
  properties:
  - type: Authentication
    url: authentication/equipmentshare-authentication.yml
  - type: OAuthScopes
    url: scopes/equipmentshare-scopes.yml
  - type: Conventions
    url: conventions/equipmentshare-conventions.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://equipmentshare.com/
- type: DeveloperPortal
  url: https://app.t3os.ai
- type: Documentation
  url: https://github.com/EquipmentShare/t3os-examples
- type: Integrations
  url: https://www.t3.tech/solutions/integrations
- type: GitHubOrganization
  url: https://github.com/EquipmentShare
- type: ChangeLog
  url: https://updates.equipmentshare.com/
- type: ChangeLog
  url: changelog/equipmentshare-changelog.yml
- type: Blog
  url: https://equipmentshare.com/resources
- type: Support
  url: https://www.equipmentshare.com/contact
- type: Login
  url: https://app.t3os.ai
- type: TermsOfService
  url: https://www.equipmentshare.com/terms
- type: PrivacyPolicy
  url: https://www.equipmentshare.com/privacy-policy
- type: Authentication
  url: authentication/equipmentshare-authentication.yml
- type: OAuthScopes
  url: scopes/equipmentshare-scopes.yml
- type: Conventions
  url: conventions/equipmentshare-conventions.yml
- type: Conformance
  url: conformance/equipmentshare-conformance.yml
- type: Lifecycle
  url: lifecycle/equipmentshare-lifecycle.yml
- type: WellKnown
  url: well-known/equipmentshare-well-known.yml
- type: DomainSecurity
  url: security/equipmentshare-domain-security.yml
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/equipmentshare-llms.txt
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

EquipmentShare API — frequently asked questions

Does EquipmentShare have an API?

Yes. APIs.io lists 1 API from EquipmentShare, including T3OS ERP GraphQL API.

How do I authenticate with the EquipmentShare API?

EquipmentShare documents its authentication (oauth2/apiKey/openIdConnect · 3 schemes). The details are profiled on APIs.io as Equipmentshare Authentication.

Is the EquipmentShare API ready for AI agents?

EquipmentShare has a Kin Score of 27.6 out of 100 (thin) and an Agent Readiness score of 16.0 (agent-aware), scored by API Evangelist on 2026-10-31.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/equipmentshare"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/equipmentshare/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/equipmentshare/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.