Skip to main content
TruckerFetch provides public examples and agent packages that use the same account permissions as the API. Choose the repository that matches your integration and read its README before running a command.

​
Configure credentials

Run REST examples with an appropriately scoped API key stored in a protected environment variable. The quickstart uses TRUCKERFETCH_API_KEY. Follow each repository’s documented environment contract and keep real keys out of committed .env files, logs and issue reports. Use hosted MCP when your client supports the OAuth flow. Choose the local bridge when your environment expects stdio and you intend to authenticate through a REST key. Neither path changes the account’s Pro entitlement, scopes or shared usage limits.

​
Keep examples safe to share

Use synthetic records in issues and tests. Preserve the exact idempotency key and payload for an unfinished mutation; replace them with synthetic values before sharing a reproduction. Report only the request ID and sanitized error details when you need help. The repositories’ code and documentation license does not grant rights to the licensed dataset or TruckerFetch brand assets. Review the applicable terms for your data workflow.