GenLogs

GenLogs is a truck intelligence platform that provides ground-truth data on every motor carrier in America from a nationwide network of proprietary roadside sensors, satellites, and millions of data sources - 4.2 billion commercial-vehicle images with 16 million added daily, covering 97% of active motor carriers. The GenLogs API (https://api.genlogs.io) turns that sensor network into freight intelligence: source and score carriers by lane, verify a carrier was recently sighted along an origin/destination, pull carrier and FMCSA profiles, run carrier-vetting rules, discover shippers by lane and shipper facilities with GeoJSON network maps, manage onboarded-carrier contacts, track mismatch observations, and receive HMAC-SHA512-signed alert webhooks. It serves brokers and shippers, insurance underwriting and claims, law enforcement asset recovery, and carriers. Auth uses an x-api-key plus a short-lived Access-Token, with named per-endpoint permissions.

GenLogs publishes 1 API on the APIs.io network: Truck Intelligence API. Tagged areas include Company, Logistics, Freight, Trucking, and Supply Chain.

The GenLogs catalog on APIs.io includes 2 event-driven AsyncAPI specifications.

GenLogs’ developer surface includes documentation, API reference, getting-started guide, support, engineering blog, authentication, and 11 more developer resources.

🌐 Visit website 📡 Source on GitHub
40.7/100 thin Agent 46/100 agent ready Full breakdown ↓
scored 2026-07-20 · rubric v0.4
1 APIs 1 MCP Servers 0 Features
CompanyLogisticsFreightTruckingSupply ChainCarrier IntelligenceFleetTransportationInsuranceFraud DetectionWebhooksGeospatial

API Rating

API Evangelist API Evangelist Rating How this is scored →
scored 2026-07-20 · rubric v0.4
Composite quality — 40.7/100 · thin
Contract Quality 12.3 / 25
Developer Ergonomics 11.7 / 20
Commercial Clarity 4.7 / 20
Operational Transparency 2.7 / 13
Governance 0.0 / 12
Discoverability 9.3 / 10
Agent readiness — 46/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
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
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/genlogs: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs

GenLogs Truck Intelligence API

Carrier sourcing, verification, vetting, and FMCSA profiles plus shipper lanes/facilities, onboarded-carrier contact management, mismatch observations, and alert webhooks - powe...

MCP Servers

genlogs-mcp.yml

MCP SERVER

Event Specifications

GenLogs Alert Webhooks

GenLogs delivers alert.matches_found webhook notifications when detection alerts (license plate, VIN, USDOT, etc.) match roadside sensor observations. Payloads are signed with a...

ASYNCAPI

Genlogs Webhooks

ASYNCAPI

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal
DeveloperPortal
 GettingStarted
GettingStarted
 Login
Login

Documentation 2

Reference material describing how the API behaves

Documentation
Documentation
 APIReference
APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt
LLMsTxt
 AgenticAccess
AgenticAccess
 AgentSkill
AgentSkill

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization
 Packages
Packages

Access & Security 2

Authentication, authorization, and security posture

Authentication
Authentication
 DomainSecurity
DomainSecurity

Operate 2

Status, limits, changes, and where to get help

Support
Support
 StatusPage
StatusPage

Commercial 1

Pricing, plans, and the legal terms of use

PrivacyPolicy
PrivacyPolicy

Company 2

The organization behind the API

Website
Website
 Blog
Blog

Source (apis.yml)

apis.yml Raw ↑ 
aid: genlogs
name: GenLogs
description: 'GenLogs is a truck intelligence platform that provides ground-truth data on every motor carrier in America from
  a nationwide network of proprietary roadside sensors, satellites, and millions of data sources - 4.2 billion commercial-vehicle
  images with 16 million added daily, covering 97% of active motor carriers. The GenLogs API (https://api.genlogs.io) turns
  that sensor network into freight intelligence: source and score carriers by lane, verify a carrier was recently sighted
  along an origin/destination, pull carrier and FMCSA profiles, run carrier-vetting rules, discover shippers by lane and shipper
  facilities with GeoJSON network maps, manage onboarded-carrier contacts, track mismatch observations, and receive HMAC-SHA512-signed
  alert webhooks. It serves brokers and shippers, insurance underwriting and claims, law enforcement asset recovery, and carriers.
  Auth uses an x-api-key plus a short-lived Access-Token, with named per-endpoint permissions.'
url: https://raw.githubusercontent.com/api-evangelist/genlogs/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- battery-ventures
- ivp
x-tier: enriched
x-tier-reason: portfolio-lead
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-07-19'
image: https://static1.squarespace.com/static/6389ebe42811fa07a7c17692/t/67362a2579a24b6b8c42992c/1731602981116/GenLogs+logo+black.png?format=1500w
tags:
- Company
- Logistics
- Freight
- Trucking
- Supply Chain
- Carrier Intelligence
- Fleet
- Transportation
- Insurance
- Fraud Detection
- Webhooks
- Geospatial
apis:
- name: GenLogs Truck Intelligence API
  description: Carrier sourcing, verification, vetting, and FMCSA profiles plus shipper lanes/facilities, onboarded-carrier
    contact management, mismatch observations, and alert webhooks - powered by GenLogs' roadside sensor network. Base URL
    https://api.genlogs.io.
  humanURL: https://docs.genlogs.io
  baseURL: https://api.genlogs.io
  tags:
  - Carrier
  - Shipper
  - Vetting
  - Alerts
  - Webhooks
  properties:
  - type: OpenAPI
    url: openapi/genlogs-openapi.yml
  - type: Overlay
    url: overlays/genlogs-openapi-overlay.yaml
  - type: Authentication
    url: authentication/genlogs-authentication.yml
  - type: Conventions
    url: conventions/genlogs-conventions.yml
  - type: Idempotency
    url: conventions/genlogs-conventions.yml
  - type: ErrorCatalog
    url: errors/genlogs-problem-types.yml
  - type: Lifecycle
    url: lifecycle/genlogs-lifecycle.yml
  - type: DataModel
    url: data-model/genlogs-data-model.yml
  - type: Conformance
    url: conformance/genlogs-conformance.yml
  - type: MCPServer
    url: mcp/genlogs-mcp.yml
  - type: AsyncAPI
    url: asyncapi/genlogs-alerts-asyncapi.yml
  - type: Webhooks
    url: asyncapi/genlogs-webhooks.yml
  - type: JSONSchema
    url: json-schema/genlogs-alert-matches-found.schema.json
  - type: AgentSkill
    url: skills/_index.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.genlogs.io
- type: DeveloperPortal
  url: https://docs.genlogs.io
- type: Documentation
  url: https://docs.genlogs.io
- type: APIReference
  url: https://docs.genlogs.io/genlogs-api-docs
- type: GettingStarted
  url: https://docs.genlogs.io/getting-started
- type: Support
  url: https://help.genlogs.io/en/
- type: Blog
  url: https://genlogs.substack.com
- type: GitHubOrganization
  url: https://github.com/genlogs
- type: StatusPage
  url: https://status.genlogs.io
- type: PrivacyPolicy
  url: https://www.genlogs.io/privacy-policy
- type: Login
  url: https://brokers.genlogs.io
- type: LLMsTxt
  url: llms/genlogs-llms.txt
- type: Packages
  url: packages/genlogs-packages.yml
- type: Authentication
  url: authentication/genlogs-authentication.yml
- type: AgenticAccess
  url: agentic-access/genlogs-agentic-access.yml
- type: DomainSecurity
  url: security/genlogs-domain-security.yml
- type: AgentSkill
  url: skills/_index.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence