Postman · Agent Readiness

Discoverability

Can agents find your site and its capabilities?

failWebMCP / agent-protocol tools discoveredAgent manifests

The page registers no tools via the WebMCP browser API (navigator.modelContext).

Fix: Expose your actions to AI agents with the WebMCP browser API: register tools via navigator.modelContext.registerTool. Optionally also publish a /.well-known/webmcp.json tool catalog as a discovery signpost.

pass/llms.txt guide for AI agentsAgent manifests

Found https://postman.com/llms.txt.

pass/llms.txt lists key pages as markdown linksAgent manifests

Found at least one "[name](url)" markdown link.

pass/llms.txt has a summary blockquoteAgent manifests

Found a "> summary" blockquote.

pass/llms.txt opens with an H1 titleAgent manifests

First line is a top-level "# Title" heading.

passKey pages discoveredKey pages crawl

Crawled 12 of 12 discovered pages beyond the homepage.

infoWebsite platformplatform

Could not identify a known website platform (custom stack or unrecognised).

Understanding

Can agents understand your content?

warnDOM size is reasonableStructured data & HTML

Homepage contains ~1644 elements — heavy.

Fix: Aim for under 1500 elements on the homepage. Heavier DOMs slow first paint and overflow some AI crawlers' parse buffers.

warnSemantic landmark elementsStructured data & HTML

Missing landmark elements: header.

warnKey pages have <title> and <h1>Key pages crawl

12 of 12 pages are missing <title> and/or <h1>: /category/financial-services, /category/artificial-intelligence, /category/payments, /category/developer-productivity, /category/travel-apis, /category/e-commerce-apis, /category/data-analytics, /category/devops, /category/e-signature-apis, /category/communication, /category/app-security, /category/database-apis.

Fix: Make sure every page sets a unique <title> and exactly one <h1>. The title is how an AI agent confirms it landed on the right page after navigating.

warnKey pages are server-renderedKey pages crawl

12 of 12 pages return <80 words of visible text — agents without JavaScript see an empty page: /category/financial-services (1w), /category/artificial-intelligence (1w), /category/payments (1w), /category/developer-productivity (1w), /category/travel-apis (1w), /category/e-commerce-apis (1w), /category/data-analytics (1w), /category/devops (1w), /category/e-signature-apis (1w), /category/communication (1w), /category/app-security (1w), /category/database-apis (1w).

Fix: Pre-render or server-render these pages so AI crawlers (which usually don't execute JS) can read them. Frameworks: Next.js Server Components, Nuxt SSR, Astro, or build-time prerendering.

passMarkdown content negotiationOpen agent protocols

Homepage returns text/markdown when requested.

passHomepage content is server-renderedCrawlability (Google)

Homepage server response contains 646 words of visible text — content is reachable without executing JavaScript.

passHeading hierarchy is intactStructured data & HTML

9 headings, no level skips.

pass<html lang> attributeStructured data & HTML

Language declared as "en".

passImages have alt textStructured data & HTML

54 of 54 <img> tags have alt attributes.

passImages have explicit dimensionsStructured data & HTML

54/54 images set width and height — no layout shift.

passInternal links on homepageStructured data & HTML

104 internal links found.

passSingle H1 on homepageStructured data & HTML

Exactly one <h1> on the homepage.

Operability

Can agents actually operate the page?

fail`[aria-hidden="true"]` elements contain focusable descendentsAccessibility

Lighthouse flagged this audit — agents may be unable to perceive or operate the affected elements.

Fix: Don't place focusable/interactive elements inside aria-hidden="true" containers.

failWebMCP tools registered with the browserWebMCP tools

The page registers no tools via the navigator.modelContext browser API, so an AI agent has no structured way to operate it.

Fix: Expose your site’s actions to AI agents with the WebMCP browser API: call navigator.modelContext.registerTool({ name, description, inputSchema, execute }) from your page so an agent can invoke them. Implement it directly, or with a library like the @mcp-b polyfill (https://mcp-b.ai). Spec: https://github.com/webmachinelearning/webmcp.

warnAccessibility tree is agent-navigableAccessibility

1 of 10 agent-critical accessibility audits failed (`[aria-hidden="true"]` elements contain focusable descendents) — an agent may be unable to identify or operate the affected elements.

Fix: Fix the failing agent-accessibility audits listed below (accessible names on controls, valid ARIA roles/relationships, nothing interactive hidden from the tree).

warnOverall accessibility scoreAccessibility

Lighthouse accessibility score: 89/100. Agents read the page through its accessibility tree, so this is a proxy for how navigable your site is to an AI agent.

Fix: Resolve the failing accessibility audits below — each one removes an element or relationship an agent would otherwise be blind to.

warnTime to First BytePerformance

1.67s (field data from CrUX) — needs improvement.

Fix: Every request an AI agent makes pays this server latency, and agents make many requests per task. Reduce TTFB with edge caching, a CDN, and shipping less server-side work per request.

pass`[aria-*]` attributes match their rolesAccessibility

`[aria-*]` attributes match their roles passed.

pass`[aria-hidden="true"]` is not present on the document `<body>`Accessibility

`[aria-hidden="true"]` is not present on the document `<body>` passed.

pass`[role]`s have all required `[aria-*]` attributesAccessibility

`[role]`s have all required `[aria-*]` attributes passed.

pass`[role]` values are validAccessibility

`[role]` values are valid passed.

pass`[aria-*]` attributes are valid and not misspelledAccessibility

`[aria-*]` attributes are valid and not misspelled passed.

pass`[aria-*]` attributes have valid valuesAccessibility

`[aria-*]` attributes have valid values passed.

passButtons have an accessible nameAccessibility

Buttons have an accessible name passed.

passDocument has a `<title>` elementAccessibility

Document has a `<title>` element passed.

passLinks have a discernible nameAccessibility

Links have a discernible name passed.

passCumulative Layout ShiftPerformance

0.100 (field data from CrUX) — good.

infoTool catalog signpost publishedWebMCP tools

No tool catalog was found at /.well-known/webmcp.json (or /.well-known/webmcp). The catalog is a community convention, not part of the WebMCP standard, so this does not affect WebMCP presence.

Fix: Consider also publishing a tool catalog at /.well-known/webmcp.json: a JSON document with a "spec" of "webmcp/0.1" and a "tools" array, where each tool declares a name and a clear description. It is a community convention (optional, not part of the WebMCP standard) that lets crawlers and agents discover your tools without executing JavaScript.

Trust & Security

Can agents safely transact?

warnOAuth authorization server metadataOpen agent protocols

/.well-known/oauth-authorization-server returned 404.

Fix: Publish /.well-known/oauth-authorization-server so AI agents discovering your OAuth setup can negotiate flows automatically. Required if your site offers an authenticated API.

warnOAuth protected-resource metadataOpen agent protocols

/.well-known/oauth-protected-resource returned 404.

Fix: Publish /.well-known/oauth-protected-resource so AI agents discovering your OAuth setup can negotiate flows automatically. Required if your site offers an authenticated API.

warnWeb Bot Auth signature headerOpen agent protocols

No Web Bot Auth signature headers — sites can't verify agent identity.

Fix: Web Bot Auth (IETF HTTP Message Signatures over Signature / Signature-Input) lets you cryptographically verify which agent is hitting you. Several CDNs offer turn-key support; otherwise skip until vendor support matures.

passCDN detectedSecurity & trust

cf-ray: a1eb02bf9eba760b-AMS (Cloudflare); x-amz-cf-id: _QCLHHy84GLR4e6jhHU6eSX-CcxpPcqfCaFyQPbW (AWS CloudFront); Server: cloudflare

passContent-Security-Policy headerSecurity & trust

CSP header present.

passHTTP Strict-Transport-Security headerSecurity & trust

max-age=31536000, includeSubDomains=true, preload=true.

passSite is served over HTTPSSecurity & trust

Homepage scheme is https:.

passhttp:// redirects to https://Security & trust

http://postman.com → https://www.postman.com/ (2 hops).

passHomepage shows no error outputSecurity & trust

No stack-trace markers in the first 5KB.

passNo mixed-content referencesSecurity & trust

Homepage HTML references no http:// resources.

passReferrer-Policy headerSecurity & trust

Referrer-Policy: strict-origin-when-cross-origin.

passTLS certificate is not near expirySecurity & trust

Valid for 84 more days (Oct 14 09:01:44 2026 GMT, issuer: YE1).

passNo tech-stack disclosure in headersSecurity & trust

Server / X-Powered-By headers don't leak product version.

passMIME-sniff protectionSecurity & trust

X-Content-Type-Options: nosniff.

passClick-jacking protectionSecurity & trust

X-Frame-Options: SAMEORIGIN.