# TruckerTech > TruckerTech is one shared load record for shippers, brokers, carriers, drivers and facilities, connected to the systems they already run. Systems connect through TruckerTech™ Nexus, the integration fabric: one adapter, versioned canonical schemas, and every exchange governed and on the record. These files describe the interfaces that exist today. They are generated on every build from the code that enforces them, and checked against it, so they cannot go stale. Published versions never change; a fix is a new version. No host is published yet. ## Docs - [Developer Lab](https://www.truckertech.com/developers): Capability Sockets, System Nodes, and what a partner builds. - [API reference (connectors)](https://www.truckertech.com/developers/reference/connectors): Every operation, event, message and schema, rendered from the specifications below. - [API reference (connectors), Markdown](https://www.truckertech.com/developers/reference/connectors.md): The same reference as one Markdown file. - [Machine index](https://www.truckertech.com/developers/index.json): Every document, version, URL and SHA-256, as JSON. ## Specifications - [OpenAPI 3.1, connectors 1.1.0](https://www.truckertech.com/developers/specs/connectors/1.1.0/openapi.json): Ingress, the remote connector protocol (as a webhook) and the canonical socket schemas. This URL never changes. - [AsyncAPI 3.0, connectors 1.1.0](https://www.truckertech.com/developers/specs/connectors/1.1.0/asyncapi.json): Partner events at ingress, the remote connector request and reply, and the canonical event messages. This URL never changes. - [OpenAPI 3.1, connectors latest](https://www.truckertech.com/developers/specs/connectors/latest/openapi.json): The newest version (also at /developers/specs/connectors/v1/openapi.json, the newest 1.x). - [AsyncAPI 3.0, connectors latest](https://www.truckertech.com/developers/specs/connectors/latest/asyncapi.json): The newest version (also at /developers/specs/connectors/v1/asyncapi.json). - [API-client collection, connectors v1](https://www.truckertech.com/developers/collections/connectors-v1.json): One request per operation, in collection format v2.1. Every variable starts empty. ## Changes and policies - [Changelog](https://www.truckertech.com/developers/changelog): Every published version, what changed, and how to move. - [Changelog feed](https://www.truckertech.com/developers/changelog.xml): The changelog as an Atom feed. - [Versioning](https://www.truckertech.com/developers/policies/versioning): Semver per document; published files never change. - [Deprecation](https://www.truckertech.com/developers/policies/deprecation): Notice periods, and how a deprecated operation says so. ## Authentication - Ingress (`POST /api/nexus/events/{connection}`): every delivery carries the `x-tt-nexus-signature` header, `hmac-sha256;key-id=;t=;value=<64 lowercase hex>`, where `value` is HMAC-SHA-256 over `.` followed by the raw body. The key id names a credential version, never key material. Bodies over 262144 bytes are refused. The send time must fall inside a 300000 ms replay window. - Remote connector protocol (a request TruckerTech Nexus sends to your endpoint): every message is signed with Ed25519 over its canonical form, and the keys are the ones each side publishes. Each request carries `tt-nexus-protocol: tt-nexus-remote/1`. Messages over 262144 bytes are refused. - AI Connect (API and MCP access for AI tools, with the user’s consent): not part of the connectors document. - Sandbox access: request access on the TruckerTech developer site. ## AI Connect - [MCP discovery (AI Catalog)](https://www.truckertech.com/.well-known/ai-catalog.json): The domain’s AI Catalog, listing the AI Connect MCP Server Card. - [MCP Server Card](https://www.truckertech.com/developers/mcp/server-card.json): AI Connect’s identity. It gains its endpoint when AI Connect is live. - The API document and the MCP endpoint: not part of the connectors document. ## Optional - [llms-full.txt](https://www.truckertech.com/llms-full.txt): This index, followed by the whole reference in Markdown.