integrate accepts up to 10 resources in one call, and returns a single brief that covers how they chain together. This is where Orbit earns its keep on multi-step features.

1. Ask your agent:

   Copy prompt

   Using both endpoint ids you picked, call Orbit's integrate tool once with both resources and the task "When a desk is booked, create a calendar event and post a Slack message announcing it." Show me the task brief.

2. Confirm the agent passes both ids in a single resources array (not two separate integrate calls), and that the returned brief describes both endpoints, including which one runs first and any shared setup (like which credentials each needs).

The brief is meant to be handed straight to a coding agent: that's the point of skipping the provider docs. The MCP server already returned it in your conversation, so there's no need to save it to a file first: your agent can work from it directly.

1. Ask your agent:

   Copy prompt

   Using that task brief, write a small function that implements this flow by following its steps exactly: don't invent parameters or endpoints that aren't in the brief.

2. Confirm the generated code's request order, parameters, and auth match what the brief specified rather than something the agent guessed independently.

1. Think of a feature you've been putting off because it touches more than one external API.
2. Ask your agent to run the full loop unassisted: decompose the feature into capability queries, search each one via Orbit, pick endpoints on their evaluateGuide, integrate them together, and generate the integration code.
3. Review the result: did it decompose sensibly, did it catch any Not supported: gaps, does the generated code match the brief?