/v1/integrate takes the endpoints you picked plus the job you're doing, and returns a task brief assembled from those endpoints' schemas, shared variables, and auth settings. It's the document you'd otherwise have reconstructed by hand from four doc pages.

1. In the Orbit collection, add a second request named Get task brief, method POST, URL:

2. Open the Body tab, select raw → JSON, and paste the payload below. Note the id: it's {{endpointUrn}}, not a pasted value. Postman substitutes your collection variable when the request is sent, so there's nothing to retype and nothing to get out of sync.

1{
2  "task": "When a Deskly user books a desk, create a calendar event for that time slot",
3  "resources": [
4    {
5      "id": "{{endpointUrn}}",
6      "type": "endpoint"
7    }
8  ]
9}

3. Open the Scripts tab, select After response, and paste the visualizer below. The brief lands in data[0].taskBrief as one long plain-text string — hard to scan in Body. This script splits it into sections and renders them in the Visualization tab.

1// Visualization Script
2​
3const response = pm.response.json();
4const taskBrief = response.data[0].taskBrief;
5​
6// Split into sections by double newline
7const sections = taskBrief.split('\n\n');
8​
9// Helper: render lines within a section body
10function renderLines(lines) {
11    let html = '';
12    let inList = false;
13​
14    for (let i = 0; i < lines.length; i++) {
15        const line = lines[i];
16        const trimmed = line.trim();
17​
18        // Numbered step: starts with digit and dot/period

4. Save, then click Send. Expect a 200 with data[0].taskBrief. Orbit assembles the brief on demand rather than serving a cached page, so it can take a few seconds.
5. In the response pane, open the Visualization tab (next to Body). You should see the brief laid out in sections — FIT (whether these endpoints actually suit the task), AUTH (including which credentials you'd have to obtain), BASE URL, STEPS with parameters and expected responses, dependencies between steps, and important considerations.

Note what just happened: you now know what integrating this endpoint would cost you (which account, which credential, which request order), and you never left Postman or signed up for anything.

Troubleshooting: A 404 means endpointUrn doesn't hold a valid id. Open the collection's Variables tab and check it against your search response, in full and unedited. resources accepts 1 to 10 entries, so you can brief Orbit on several endpoints at once. The brief will cover how they chain together. If Visualization is empty, confirm the script is on Scripts → After response (not Before request), that you saved before sending, and that the response includes data[0].taskBrief.