How an AI agent discovers a 3PL over x402
How an AI agent discovers a 3PL over x402 Agent builders keep asking the same first question: where does my agent look? Nettrux is the first 3PL on x402, so the answer is deliberately boring and HTTP-native. Before any quote, before any payment header, an agent should fetch three public documents: The discovery pointer at https://www.nettrux.ai/.well-known/x402 The human/agent guide at…
An AI agent discovers a third-party logistics provider (3PL) named Nettrux over version x402. To do so, the agent must follow a specific process. First, the agent fetches three public documents: the discovery pointer, the human/agent guide, and the field contract. These documents are located at https://www.nettrux.ai/.well-known/x402, https://www.nettrux.ai/agents, and https://nettrux-edge.fly.dev/openapi.json, respectively.
The agent then parses the JSON data from the discovery pointer document to obtain essential information about the freight API, including the resource host, OpenAPI URL, and deploy gates. The agent guide and OpenAPI document provide the contract for every authenticated call to the API. The discovery pointer does not point to a live public pay-and-book endpoint, populated resources array, or public real-money settlement, as these features are intentionally false.
The agent should expect a 404 error when trying to access the freight API discovery document on the Edge site, as it is not published when EDGE_X402_DISCOVERY_PUBLISHED is false. Only after discoveryPublished flips to true and the gate allows it should the agent consider the Edge discovery URL authoritative.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
