mocop
Browse · Docs · Guide · Analyze

Cardog API v2

API by Cardog · rest

VIN identity, canonical specs, live market data, and recalls — one key. The ref is the API. Every parameter is an entity ref (make:tesla, model-year:honda/cr-v/2026) or a VIN; every response carries refs plus links to adjacent resources. Free text is accepted in exactly one place — GET /v2/entities/resolve — and returns refs with confidence, never silently fuzzed results. Errors are instructions. Every non-2xx body is the ErrorEnvelope: code, message, hint, docs_url, the offending refs named, and nearest-ref suggestions where computable. Price is machine-readable. GET /v2/pricing is the live rate card; every metered response carries X-Credits-* headers.

Endpoint: https://api.cardog.app/

Verification: observed. Source: crawl.

Capabilities (70)

  • Your credits and usage
  • Who an organization may name on a thread
  • Open a coordination thread
  • A coordination thread's header
  • Reply on a coordination thread
  • Close or reopen a coordination thread
  • An organization's API keys metadata only
  • Open an agent session
  • List agent threads
  • Read an agent thread
  • Find a carrier by name DOT number or VIN
  • The carrier: identity what it declared what the road record shows
  • Every unit observed under a carrier
  • What changed on the API
  • EV charging stations near a point
  • One charging station by id
  • Read a chassis number off a photo of the caution plate or frame stamp
  • A Japanese chassis number: maker models type approvals and build dates
  • Browse/search the entity registry (paged capped)
  • Free text → refs with confidence (the front door)
  • Dereference a ref: node + parents/children + counts + links
  • Report a wrong or missing record
  • Read back a report you filed
  • The organization's feed contracts and where each one stands
  • A feed artifact through the signed link a latest read returns
About · Contact · Privacy