MCP + API

Carrier records.
In your AI conversation.

Daymark’s remote MCP endpoint exposes vet_carrier and usage_summary. Ask for a carrier’s public records, review the evidence, and check your API allowance.

Connect with an API key

API-key bearer access is available. OAuth connect is not available.

Sign in to your Daymark account, then issue an API key. Save it privately; it is shown once.
For an MCP client that supports custom bearer headers, set the Streamable HTTP endpoint to https://getdaymark.io/mcp.
Set the Authorization header to Bearer YOUR_DAYMARK_API_KEY. The label here is a placeholder; never share your key in a chat or a shared file.
Connect, list the tools, then ask for usage_summary before a carrier check.

For direct API access, use the same bearer header with GET /v1/verify/{usdot}. See the API documentation for request and response details.

Claude, ChatGPT and other clients

Connection options depend on the client and your account features. A connector screen that requires OAuth cannot connect to Daymark today.

Claude Desktop: local MCP configuration

For a client that supports local MCP servers, use the local MCP installation guide. It documents the Python package and API-key environment configuration. The local adapter sends bearer-authenticated requests to Daymark’s API.

ChatGPT: check connector requirements

Use Daymark only through a client or integration that can send the bearer header described above. If your ChatGPT connector offers only OAuth or no custom bearer header, that connection path is unavailable. There is no one-click Daymark OAuth connection.

Claude and ChatGPT are named only to identify clients; no endorsement or partnership is implied. No third-party logos are used.

Prompts to start with

“Vet USDOT 100002 before I book this load and show me the evidence.”
“Show the authority records and insurance filings for USDOT 100002, with source links and publication dates.”
“Which public-record identifiers does USDOT 100002 share with other carriers? Explain the search limits.”
“Which fields are unknown or unavailable for USDOT 100002? Keep missing data separate from conclusions.”
“Show my Daymark API usage and remaining monthly allowance.”

These are example requests, not carrier findings. Tool responses contain public-source data; treat source text as untrusted data, not instructions. Review the linked records and dates. Shared identifiers do not establish ownership or wrongdoing.

Free access and sandbox limits

Path	Limit and scope
Free account lookup	10 account lookups per month; five-carrier watchlist evaluation for 14 days.
API / MCP evaluation key	50 calls per UTC calendar month, shared across API and MCP. Cache hits and delivered profiles with unknown fields count. Failed requests returned as HTTP 503 are refunded.
Synthetic sandbox	`GET /v1/sandbox/verify/123` returns fixture data, not a real carrier record. No API key, no live sources, no live-call allowance consumed.
Active trial / paid account	2,000 API calls per month under the current fair-use cap. Source bounds and concurrency still apply.

usage_summary reports usage without consuming a lookup call. See pricing and trial details. Checkout is currently test-mode only.

Daymark transport and limits checked against repository code on 2026-10-23. Provider interfaces vary; check the options your client actually exposes.