How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
U.S. Department of Transportation

U.S. Department of Transportation Tires API

Tire search and list endpoints

Documentation Provider Profile APIs.io OpenAPI GitHub

U.S. Department of Transportation Tires API is one of 41 APIs that U.S. Department of Transportation publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Tires. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 4 operations across 4 paths, and defines 15 schemas. It is described by OpenAPI 3.2.0, at version 1.6.0.

Requests are made against a single base URL, https://mobile.fmcsa.dot.gov/qc/services.

4 operations 4 paths 15 schemas 4 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.6.0
Base URL
https://catalog.data.faa.gov/api/3
Resource Areas
1

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 4 GET. Each is listed below with its method, path, parameters, and response codes.

Tires 4

Tire search and list endpoints

GET
/tires
Get tires
getTires 9 params → 200400500
GET
/tires/brands
Get tires brands
getTiresBrands 3 params → 200400500
GET
/tires/bySearch
Get tires by search
getTiresBySearch 7 params → 200400500
GET
/tires/{id}
Get tires by id
getTiresById 2 params → 200400500

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are ComplaintAggregate (12 properties), RecallAggregate (11 properties), Pagination (9 properties), Tire (9 properties). Each schema is shown below with its type and property counts.

Message
object
4 properties
Meta
object
3 properties
TireWrapped
object
2 properties
Investigations
object
2 properties
TireBrand
object
1 property
Components
object
1 property
MFRCommunicationAggregate
object
6 properties
Pagination
object
9 properties
Tire
object
9 properties
Recalls
object
2 properties
ComplaintAggregate
object
12 properties
SafetyIssueAggregate
object
4 properties
RecallAggregate
object
11 properties
TireBrandWrapped
object
2 properties
InvestigationAggregate
object
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

us-dot-tires-api-openapi.yml Raw ↑

Other APIs U.S. Department of Transportation publishes across the network.

FAA Data Catalog (CKAN Action API v3)
AE Profile APIs.io
DOT Data Hub Open Data API
AE Profile APIs.io
Bureau of Transportation Statistics Open Data API
AE Profile APIs.io
NHTSA vPIC (Vehicle Product Information Catalog) API
AE Profile APIs.io
NHTSA Safety API (recalls, complaints, safety ratings)
AE Profile APIs.io
FRA Safety Data Web Services
AE Profile APIs.io
FMCSA QCMobile API
AE Profile APIs.io
U.S. Department of Transportation Air Carrier API
AE Profile APIs.io
U.S. Department of Transportation Axhsubmitdiscrepancies API
AE Profile APIs.io
U.S. Department of Transportation Coded Instrument Flight Procedures (CIFP) API
AE Profile APIs.io
U.S. Department of Transportation Daily Digital Obstacle File (DDOF) API
AE Profile APIs.io
U.S. Department of Transportation Digital Enroute Charts US (DDECUS) API
AE Profile APIs.io
#Tires
← Back to U APIs
API Details
ID
us-dot:us-dot-tires-api
Base URL
https://catalog.data.faa.gov/api/3
Docs
https://catalog.data.faa.gov/
Provider
U.S. Department of Transportation
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=us-dot-tires-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/us-dot-tires-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of U.S. Department of Transportation Tires API, 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.