UPS: 37 of 100 on Ora's agent-readiness scan

The score

UPS is a parcel delivery and logistics company based in Atlanta.

• 37of 100, grade D
  Ora's agent-readiness scan of ups.com, read 9 November 2026.
• 11Discovery, of 13
  Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
• 12Access, of 52
  Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
• 11Usability, of 48
  Whether they can act through it: an MCP server, an API with a specification, sign-in for agents.
• 0Payments, of 0
  No check in this layer applied to the site.

25 percent of the 132,085 domains Ora ranks score under 30, and the average score is 44.

Ora's one-line summary: UPS offers OAuth 2.0 support, but lacks published OpenAPI specification.

What an assistant meets at the door

Before an assistant can read, compare or buy, it has to get in. These rows are the door: whether the bot shield lets the main agents through, what robots.txt tells the search, training and user-triggered agents, and whether the home page has text without running JavaScript.

What it can read, and what it can do

The reading layer is what an assistant takes away from the pages: a text file written for it, markdown on request, structured data about the company, a sitemap. The act layer is whether it can do anything through a published interface rather than by clicking through the site.

The six payment checks did not apply on this read: Ora did not read the site as a shop.

Three fixes to hand to the web team

Ora estimates how many points each open check would return. These are the largest on this read, in Ora's words where it gave them, so a leader can hand the list over without translating it.

1. Public API with reachable endpoints, worth about 6.5 points by Ora's estimate: No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated).
2. Scoped permissions, worth about 4.6 points by Ora's estimate: No declared OAuth scopes, security schemes, or scoped-permission documentation found.
3. WebMCP support, worth about 4.6 points by Ora's estimate: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found.

Our read

UPS opens the door to every agent and then hands it the wrong kind of file at every turn. All four agent user agents reach ups.com, but robots.txt returns HTML instead of rules, the home page could not be fetched, the llms.txt at /.well-known/llms.txt returns an HTML page and there is no sitemap, so the content, policy and structured-data rows are unverified or empty and the Access layer reads 12 of 52. The act layer has one working surface, an OAuth endpoint at ups.com/oauth/authorize, and one broken one, an MCP manifest at /.well-known/mcp/manifest.json that is not valid JSON; there is no reachable public API, no developer portal and no OpenAPI specification, so the Usability layer reads 11 of 48. The Discovery layer is 11 of 13, with Wikipedia matching UPS Airlines rather than the parcel company. A carrier whose tracking numbers are what people most often hand an assistant answers with HTML where text was asked for; three files served as what they claim to be would move this D.

Test your own site

Run the same scan on your own domain at ora.ai. The score, the layers and the fixes on this page come from its public result for ups.com; a scan of a public site takes a few minutes and needs no account.

• Scan your domain on OraThe same checks, the same scoring, on your own site.
• The self-check, 18 questionsWhat to ask for, in business terms, before the scan.
• All the 360 checksThe other companies in this series, newest first.