Postman Collection Request Map from Endpoint Inventory (No Invented Latency Scores)

Prompt

Act as a Postman collection-request cartographer who only uses a pasted inventory. You write a collection request map the inventory already supports. You do not invent latency scores, call totals, success percents, or billing secrets not in Inputs. This is not a Postman brand-kit generator; not an API guarantee.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- Inventory I lock (endpoint stubs, request cues, folder notes): [Inventory]
- Postman / collection version notes I lock: [Version]
- Workspace or collection label I may quote (or UNKNOWN): [Workspace]
- Required request or map names I may quote (or UNKNOWN): [SpecNames]
- Endpoint and path labels already present (or UNKNOWN): [EndpointCues]
- Request and method labels already present (or UNKNOWN): [RequestCues]
- Folder and environment notes already present (or UNKNOWN): [FolderNotes]
- Words I must not use: [Banned]
- What I must never invent (latency scores, call totals, success percents, billing secrets): [Never]
- Output format: [Format]
- Language: [Lang]

Generate:
1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, EndpointCues, RequestCues, FolderNotes, Lang. Forbidden: invented latency scores, call totals, success percents, billing secrets. Banner: not a Postman brand-kit generator; not an API guarantee.
2. Collection request map: one numbered row per Inventory stub or cue. Missing FolderNotes write NOT IN INPUTS. Use Postman collections, requests, folders, environments, and path language when Inventory supports it. Never print latency-count or call VALUES not in Inventory.
3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent success-percent VALUES not in Inventory.
4. Version lock: print Version. Refuse Postman features newer than Version if Version is named.
5. Refuse list: inventing latency scores, inventing call totals, inventing success percents, inventing billing secrets.
6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.

Constraints:
- Map from Inventory only. No invented latency VALUES. Teach Postman collection request maps, not a Insomnia or Hoppscotch swap.
- Honor Version. No emojis.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Generated Output

This image was generated using the prompt above.

Postman Collection Request Map from Endpoint Inventory (No Invented Latency Scores) - Result

Examples

Example Input

Inventory: endpoint Harbor Quay GET /dock/orders as pasted request cue List Dock Orders as pasted folder notes Harbor Staging as pasted; endpoint River Ops POST /river/events as pasted request cue Create River Event as pasted. Latency invent NONE. Call invent NONE.
Version: Postman as pasted (do not invent unreleased AI monitor pack)
Workspace: Harbor Quay API desk as pasted
SpecNames: List Dock Orders request map as pasted; Create River Event request map as pasted. Success percents UNKNOWN.
EndpointCues: GET /dock/orders as pasted; POST /river/events as pasted. DELETE UNKNOWN.
RequestCues: List Dock Orders as pasted; Create River Event as pasted. Auth Probe UNKNOWN.
FolderNotes: Harbor Staging as pasted. Latency VALUES NOT IN INPUTS.
Banned: guaranteed uptime, latency invent, call invent, success invent
Never: invent latency scores, invent call totals, invent success percents, invent billing secrets
Format: ledger + table + specs + version + refuse + compliance
Lang: English

Example Output

1. Ledger. Inventory: endpoint Harbor Quay GET /dock/orders as pasted request cue List Dock Orders as pasted folder notes Harbor Staging as pasted; endpoint River Ops POST /river/events as pasted request cue Create River Event as pasted. Latency invent NONE. Call invent NONE. Version Postman as pasted. Workspace Harbor Quay API desk. SpecNames List Dock Orders request map as pasted; Create River Event request map as pasted. Success percents UNKNOWN. EndpointCues GET /dock/orders as pasted; POST /river/events as pasted. DELETE UNKNOWN. RequestCues List Dock Orders as pasted; Create River Event as pasted. Auth Probe UNKNOWN. FolderNotes Harbor Staging as pasted. Latency VALUES NOT IN INPUTS. Lang English. Banner: not a Postman brand-kit generator; not an API guarantee. Forbidden: invented latency scores, call totals, success percents, billing secrets, guaranteed uptime, latency invent, call invent, success invent.

2. Collection request map.
1. Harbor Quay GET /dock/orders | EndpointCues GET /dock/orders as pasted | RequestCues List Dock Orders as pasted | FolderNotes Harbor Staging as pasted | latency VALUES NONE | call NONE | Postman collection request map only.
2. River Ops POST /river/events | EndpointCues POST /river/events as pasted | RequestCues Create River Event as pasted | FolderNotes beyond Harbor Staging NOT IN INPUTS | latency VALUES NONE | call NONE.
Success percents UNKNOWN so write success-percent VALUES NOT IN INPUTS. DELETE not invented beyond EndpointCues.

3. Spec name set. List Dock Orders request map as pasted; Create River Event request map as pasted as SpecNames. Unnamed rows NOT IN INPUTS. Never invent success-percent VALUES.

4. Version lock. Postman as pasted as pasted. Refuse unreleased AI monitor pack.

5. Refuse list. inventing latency scores; inventing call totals; inventing success percents; inventing billing secrets.

6. Compliance. Quoted Banned: guaranteed uptime, latency invent, call invent, success invent. Cut. Quoted Never: invent latency scores, invent call totals, invent success percents, invent billing secrets. Cut. Format ledger + table + specs + version + refuse + compliance.

Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.