Canonical site profile

postman.com

https://postman.comLevel 3 — Strong for this profile

saas profile · inferred · scanned 16 Jul 2026 · scanner 0.4.0 · methodology

Category: SaaS & developer tools · Country: US

Refresh this profile Profile JSON

Score78

out of 100

Score: 78

First seen15 Jul 2026

First persisted AgentVisible scan.

Scan history2

Comparable automatic evidence snapshots.

Index statePublished

Rankings remain independent of paid status.

Readable 100

out of 100

Reliable N/A

Not measured for this profile.

Actionable N/A

Not measured for this profile.

Discoverable 76

out of 100

Trust & access 0

out of 100

History

Score evidence over time

Automatic public-baseline scans; only rows with matching profile, scanner and schema versions are directly comparable.
Scanned	Score	Profile	Scanner	Schema
16 Jul 2026	78	saas	0.4.0	2.0
15 Jul 2026	78	saas	0.3.0	2.0

Latest evidence

Persisted signal audit

Agent Skills index

Agent Skills index is not required for a saas site.

Evidence: 404

API Catalog

API Catalog is not required for a saas site.

Evidence: 404

Auth.md

Site publishes auth.md, but it does not clearly describe agent access.

Evidence: https://postman.com/auth.md

Content Signals

Robots.txt does not declare Content-Signal policy.

Link Headers

Homepage does not expose discovery-oriented Link headers.

LLMs.txt

Site publishes /llms.txt for LLM-friendly discovery.

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

Markdown Negotiation

Homepage returns Markdown when requested by an agent.

Evidence: text/markdown

MCP Server Card

MCP Server Card is not required for a saas site.

Evidence: application/json

OpenAPI description

OpenAPI description is not required for a saas site.

Evidence: text/html

Robots.txt

Site publishes a valid-looking robots.txt file.

Evidence: User-agent: * Sitemap: https://www.postman.com/sitemap.xml

Sitemap

Site publishes a reachable sitemap.

Evidence: https://www.postman.com/sitemap.xml

WebMCP

WebMCP is not required for a saas site.