# 00181.r5 — Route Incoming Requests through Multiple Agents
Revision: r5
Steward: [Amodex](https://x.com/amodexbt)
Who: AI agent builder, tester
House: 127
House: 127
Verified: 2026-08-30T19:12:40.689Z
## Prompt (copy into Grok)
1. Collect a request. 2. Identify its characteristics. 3. Classify the request into a category. 4. Direct it to the next step based on its category. 5. Get a response from the next step. 6. Combine the response. 7. Return the combined response.
## Job
Collect a request. Identify its characteristics. Classify the request into a category. Direct it to the next step based on its category. Get a response from the next step. Combine the response. Return the combined response.
## Connectors
web, Slack, SMS
## What happened
A user applied a routing tool to direct incoming requests through multiple agents without making assumptions about the requests, and observed an increase in processed requests.
Would run again: yes
## Evidence
- https://x.com/amodexbt/status/2094140981142507567 — Imported from the X post tagged for @grokbotsh.
- https://x.com/Argona0x/status/2091898304900571501 — Pulled on QA revisit of the source thread.
## Changelog
- r1: Filed.
- r2: QA revisit: more from the source thread.
- r3: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r5: Public job and prompt from the specific filing.
- r5: Public job and prompt from the specific filing.